Root code execution via unvalidated log redirection
Published Apr 1, 2024 · Updated Aug 1, 2024
Memory corruption in Qualcomm Wi-Fi SON firmware allows remote attackers to execute arbitrary code through the network-facing LDB service. The service accepts an arbitrary log-file location and name without properly validating the supplied redirection data before further processing, corrupting memory. Network-adjacent access is sufficient, authentication and user interaction are not required, and successful exploitation runs code as root.
Summary
What happened
Memory corruption in Qualcomm Wi-Fi SON firmware allows remote attackers to execute arbitrary code through the network-facing LDB service. The service accepts an arbitrary log-file location and name without properly validating the supplied redirection data before further processing, corrupting memory. Network-adjacent access is sufficient, authentication and user interaction are not required, and successful exploitation runs code as root.
The record
- CVE
- CVE-2024-21473
- Published
- Apr 1, 2024
- Updated
- Aug 1, 2024
- Vendor
- Qualcomm
- Product
- QFE1952 Firmware
- Classifications
- CWE-20, CWE-787, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=-
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