Local application integrity compromise via license-file stack overflow
Published Dec 13, 2024 · Updated Feb 7, 2025
Stack buffer overflow in the Core Libraries of RTI Connext Professional allows local users to corrupt application memory via a license file. The license-file parser writes attacker-controlled license data beyond a stack buffer because it fails to validate the input length. Low-privileged filesystem access is required to replace the file; successful exploitation can alter application integrity and interrupt execution.
Summary
What happened
Stack buffer overflow in the Core Libraries of RTI Connext Professional allows local users to corrupt application memory via a license file. The license-file parser writes attacker-controlled license data beyond a stack buffer because it fails to validate the input length. Low-privileged filesystem access is required to replace the file; successful exploitation can alter application integrity and interrupt execution.
The record
- CVE
- CVE-2024-52064
- Published
- Dec 13, 2024
- Updated
- Feb 7, 2025
- Vendor
- Real-Time Innovations
- Product
- Connext Professional
- Classifications
- CWE-121, CWE-193, CWE-120, CAPEC-46
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 13, 2024CVE publishedPublication date reported by the CVE source.
- Feb 7, 2025Record 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=4.4 <5.3.1.45
- Affected versionversion=6.0.0 <6.0.1.40
- Affected versionversion=6.1.0 <6.1.2.21
- Affected versionversion=7.0.0 <7.3.0.2
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