Hackers Can Now Exploit IP Streams

EddieC 0 Tallied Votes 267 Views Share

Isn't anything safe from hackers? Now they've apparently found a way to hack into systems through a media stream, threatening users with denial of service attacks that can bring down servers and desktops alike. The vulnerability was reported yesterday by VoIPshield Laboratories, a security tools maker in Canada.

The flaws were found in Microsoft Office Communications Server 2007, Office Communicator and Windows Live Messenger, which Microsoft said could impact as many as 250 million people. The flaws also affect and systems that use the Real-time Transport Protocol (RTP), including those from Avaya, Cisco and Nortel, according to .

"Securing the media stream is particularly challenging because once the messaging session is established, the flow of packets is not always monitored and managed by the call server," according to a statement from VoIPshield Labs, the research division of VoIPshield Systems. Microsoft is investigating the flaws, it said, but so far has not issued any security advisories or updates.

But denial of service are not the only threats to worry about. Andriy Markov, director of VoIPshield Labs, told TMCnet.com that "many other media stream attacks exist that have more severe implications than service availability. We’re presently validating new research that shows an attacker can gain unauthorized access to an unsuspecting user’s laptop by manipulating the packets of a VoIP phone call. We believe that these attacks can even be made to traverse a PSTN gateway.”

Is this the real world or a Wachowski brothers movie?

Dani AI

Generated

As pointed out, the November 2008 research exposed real parsing/RTCP‑handling flaws in RTP/RTCP implementations — recorded as CVE‑2008‑5179 and observed in Microsoft Office Communications Server, Office Communicator and Windows Live Messenger — that could be triggered by crafted RTCP receiver‑report packets and cause denial‑of‑service. (app.opencve.io)

Why this mattered then (and still matters): RTP carries the media stream and RTCP carries control/quality reports; many implementations historically assumed well‑formed RTCP and did minimal validation, so a malformed RTCP packet can crash or exhaust a stack that processes it. Because media flows are often peer‑to‑peer and bypass the call server, the media path can be an under‑monitored attack surface. (datatracker.ietf.org)

Practical, applied mitigations that address the root causes:

  • Keep endpoint and server software patched and track CVEs for VoIP components.
  • Encrypt and authenticate media with SRTP (RFC 3711) so an attacker cannot easily inject or tamper with RTCP/RTP.
  • Place a Session Border Controller (SBC) or RTP‑aware firewall at your network edge to validate, rate‑limit and interwork media streams (reject unexpected RTCP/RTP or limit RTCP rates).
  • Use secure signalling (SIP over TLS), IDS/IPS signatures for VoIP anomalies, and logging/alerts for abnormal RTCP patterns. (rfc-editor.org)

Operational notes and context: vendors and CERT/NVD entries document these issues and the usual response is vendor fixes plus network controls when endpoints are EOL or unpatchable; defense‑in‑depth is essential because media‑path bugs bypass simple signalling checks. Also note ’s ASP.NET request is a separate topic — web app security and secure coding deserve their own thread. (cvefeed.io)

Summary tip: treat media (RTP/RTCP) as part of the attack surface — validate, authenticate, monitor and isolate it the same way as signalling and other network services.

baandow 0 Newbie Poster

i am an IT student, i want to learn more about ASP.NET so guide me please the beast webside that got with examples..
thank you

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.