VYPR
← All advisories
Unrated severityNVD Advisory· Published Mar 14, 2018· Updated Aug 5, 2024

CVE-2018-1000122

CVE-2018-1000122

Description

Buffer over-read in curl's RTSP+RTP handling (7.20.0-7.58.0) allows remote DoS or info leak.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Buffer over-read in curl's RTSP+RTP handling (7.20.0-7.58.0) allows remote DoS or info leak.

Vulnerability

A buffer over-read vulnerability exists in curl versions 7.20.0 to 7.58.0 inclusive in the RTSP (Real Time Streaming Protocol) and RTP (Real-time Transport Protocol) handling code [2]. The bug occurs when parsing certain RTSP responses, leading to reading beyond the allocated buffer boundary.

Exploitation

An attacker can trigger the vulnerability by sending a crafted RTSP response to a client that uses libcurl with RTSP support. No authentication is required, and the attacker only needs network access to deliver the malicious response. The attacker must control the RTSP server or intercept the communication.

Impact

Successful exploitation can result in denial of service due to a crash or information leakage of sensitive data from the client's memory. The impact is limited to information disclosure or disruption of the client application.

Mitigation

The vulnerability is fixed in curl version 7.59.0 [2]. Red Hat has released updated packages for curl 7.61.1 in Red Hat Enterprise Linux 7 (via RHSA-2018:3157) [2] and for httpd24-curl in Red Hat Software Collections (via RHSA-2018:3558) [1]. Users should upgrade to the fixed version or apply the relevant security updates.

References
  1. https://access.redhat.com/errata/RHSA-2018:3558
  2. https://access.redhat.com/errata/RHSA-2018:3157

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

20

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

17

News mentions

0

No linked articles in our index yet.