Vulnerability Note VU#329561

RealNetworks Helix Universal Server vulnerable to buffer overflow when supplied an overly long string within the "Transport" field of a SETUP RTSP request

Original Release date: 17 Apr 2003 | Last revised: 17 Apr 2003

Overview

The RealNetworks' Helix Universal Server supports delivery of several different media types via RTSP (Real Time Streaming Protocol). Vulnerabilities have been discovered in the way it handles some RTSP requests. These vulnerabilities could allow a remote attacker to execute arbitrary code on vulnerable systems.

Description

Researchers at NGSSoftware have discovered a vulnerability in the way that the Helix Universal Server overly long strings in the Transport field of an RTSP SETUP request. According to the NGSSoftware advisory:

    "By supplying an overly long character string within the Transport field of a SETUP RTSP request to a Helix server, which by default listens on TCP port 554, an overflow will occur overwriting the saved return address on the stack. On a windows box, the Helix server is installed by default as a system service and so exploitation of this vulnerability would result in a complete server compromise, with supplied code executing in the security context of SYSTEM. The impact of these vulnerabilities on UNIX based platforms was not tested, though they are vulnerable."


This vulnerability is similar to VU#485057 and VU#974689, which were also discovered by NGSSoftware and published in the same advisory.

Impact

A remote attacker may be able to execute arbitrary code on the vulnerable system. This attacker-supplied code would be run with the privileges of the user running the Helix Server.

Solution

Apply a patch from the vendor

RealNetworks has provided information about patches for the Helix Universal Server at the following location:


Users are encouraged to review this information and apply the patch.


Workarounds

Disable access to the Helix Server via RTSP

If patches cannot be applied, limit access to the RTSP service (554/tcp) on the vulnerable systems to trusted systems on the network. Note that this will not prevent internal attackers from exploiting this vulnerability, but can limit exposure. As a general rule, the CERT/CC recommends blocking access to all services that are not explicitly required.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
RealNetworksAffected-02 Apr 2003
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A

References

Credit

Thanks to Mark Litchfield of NGSSoftware Insight Security Research for reporting this vulnerability.

This document was written by Chad R Dougherty.

Other Information

  • CVE IDs: Unknown
  • Date Public: 20 Dec 2002
  • Date First Published: 17 Apr 2003
  • Date Last Updated: 17 Apr 2003
  • Severity Metric: 6.41
  • Document Revision: 16

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.