Application crash via incomplete reply-name lookup
Published Nov 12, 2024 · Updated Nov 19, 2024
Null pointer dereference in goToMain LibOSDP before 2.4.0 allows physically proximate attackers to crash a consuming application. The osdp_reply_name function accepts every reply identifier from REPLY_ACK through REPLY_XRD, although its names table omits entries, then dereferences a null lookup result. A peer on the OSDP communication channel can send an undefined in-range reply without establishing a secure channel, terminating the process that embeds the library.
Summary
What happened
Null pointer dereference in goToMain LibOSDP before 2.4.0 allows physically proximate attackers to crash a consuming application. The osdp_reply_name function accepts every reply identifier from REPLY_ACK through REPLY_XRD, although its names table omits entries, then dereferences a null lookup result. A peer on the OSDP communication channel can send an undefined in-range reply without establishing a secure channel, terminating the process that embeds the library.
The record
- CVE
- CVE-2024-52296
- Published
- Nov 12, 2024
- Updated
- Nov 19, 2024
- Vendor
- goToMain
- Product
- LibOSDP
- Classifications
- CWE-476, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2024CVE publishedPublication date reported by the CVE source.
- Nov 19, 2024Record 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=< 2.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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