Memory corruption via unbounded RTSP reply formatting
Published Jan 18, 2026 · Updated Jan 18, 2026
Buffer overflow in rtsp_rely_dumps in cijliu librtsp at commit 2ec1a81ad65280568a0c7c16420d7c10fde13b04 allows local users to corrupt memory. The function accepts any buffer of at least 1,024 bytes, then uses unbounded sprintf calls to append request-derived reply data without checking the supplied len. Exploitation requires local low-privilege access to a host application that invokes the library; the public reproduction reports a Valgrind overflow but withholds the payload, so code execution is unproven.
Summary
What happened
Buffer overflow in rtsp_rely_dumps in cijliu librtsp at commit 2ec1a81ad65280568a0c7c16420d7c10fde13b04 allows local users to corrupt memory. The function accepts any buffer of at least 1,024 bytes, then uses unbounded sprintf calls to append request-derived reply data without checking the supplied len. Exploitation requires local low-privilege access to a host application that invokes the library; the public reproduction reports a Valgrind overflow but withholds the payload, so code execution is unproven.
The record
- CVE
- CVE-2026-1108
- Published
- Jan 18, 2026
- Updated
- Jan 18, 2026
- Vendor
- cijliu
- Product
- librtsp
- Classifications
- CWE-120, CWE-119
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 18, 2026CVE publishedPublication date reported by the CVE source.
- Jan 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2ec1a81ad65280568a0c7c16420d7c10fde13b04
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo