Local service crash via malformed location parsing
Published Jan 30, 2020 · Updated Aug 4, 2024
NULL pointer dereference in OSSEC-HIDS 2.7 through 3.5.0 allows local users to crash ossec-analysisd via a crafted UNIX-socket message. In OS_CleanMSG, a missing -> delimiter makes strstr return NULL, and strchr dereferences that result while parsing the message location. The attacker needs local write access to the analysisd socket; successful exploitation terminates the analysis process and interrupts log analysis.
Summary
What happened
NULL pointer dereference in OSSEC-HIDS 2.7 through 3.5.0 allows local users to crash ossec-analysisd via a crafted UNIX-socket message. In OS_CleanMSG, a missing -> delimiter makes strstr return NULL, and strchr dereferences that result while parsing the message location. The attacker needs local write access to the analysisd socket; successful exploitation terminates the analysis process and interrupts log analysis.
The record
- CVE
- CVE-2020-8448
- Published
- Jan 30, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 30, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Malformed analysisd queue-message proof of conceptproof of concept · demonstrated
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