Project

General

Profile

Actions

Bug #2625

closed

osmo-mgw leaks host data when forwarding RTP packets

Added by pespin over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
11/08/2017
Due date:
% Done:

100%

Spec Reference:

Description

I was testing the new osmo-mgw+osmo-bsc from today's master (54dd4b3f72d90dfbed19ffa7b1e98112add067a6). I can place the call (from msA->msB, the other way it didn't work due to some sccp paging bug according to dexter), but no audio is heard.

Looking at the pcap traces with dexter, everything is fine, all the endpoints and connections are created and handled correctly, and RTP from msA reaches msB and the opposite too. However, no audio can be heard during the call.

It seems the RTP packets going osmo-bts=>osmo-mgw are 87 bytes long, which seems fine, but once they leave the osmo-mgw => osmo-mgcp, then size explodes to 4138 bytes, and the packet contains the initial data + random memory, which in my case contains filesystem paths from my workstation.

So, conclusion, there seems to be some reading out of buffer bounds in the code path in osmo-mgw which receives RTP packets and forwards it. I attach a sample pcap file showing the issue.


Files

wrong_size_rtp3.pcapng wrong_size_rtp3.pcapng 106 KB pespin, 11/08/2017 03:25 PM

Related issues

Related to OsmoGSMTester - Bug #2626: osmo-gsm-tester: Add osmo-mgw supportClosedpespin11/08/2017

Actions
Related to OsmoBTS - Bug #2624: osmo-bts aborts: Not enough tailroom msgb_putClosedpespin11/08/2017

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)