Memory corruption via Alternative Frequency offset overflow
Published Sep 2, 2024 · Updated Sep 5, 2024
Buffer overflow in Qualcomm FM Host firmware allows local users to corrupt memory by setting an Alternative Frequency offset to 255. Qualcomm maps the flaw to CWE-120 but does not disclose the affected function, destination buffer, or exact unchecked copy operation. Local low-privileged access and affected embedded FM hardware are required; the documented result is FM Host memory corruption, while further behavior remains undisclosed.
Summary
What happened
Buffer overflow in Qualcomm FM Host firmware allows local users to corrupt memory by setting an Alternative Frequency offset to 255. Qualcomm maps the flaw to CWE-120 but does not disclose the affected function, destination buffer, or exact unchecked copy operation. Local low-privileged access and affected embedded FM hardware are required; the documented result is FM Host memory corruption, while further behavior remains undisclosed.
The record
- CVE
- CVE-2024-33042
- Published
- Sep 2, 2024
- Updated
- Sep 5, 2024
- Vendor
- Qualcomm
- Product
- Robotics RB3 Platform Firmware
- Classifications
- CWE-787, CWE-120
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 2, 2024CVE publishedPublication date reported by the CVE source.
- Sep 5, 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=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