Memory corruption via event-listener removal command
Published Mar 4, 2024 · Updated Aug 29, 2024
Memory corruption in Qualcomm Core Services allows local users to corrupt memory through a command that removes one event listener. The event-listener removal path mishandles that command, but Qualcomm has not published the invalid field, buffer operation, or memory boundary involved. Local access is required; Qualcomm reports no required privileges or user interaction, while the resulting execution primitive remains undisclosed.
Summary
What happened
Memory corruption in Qualcomm Core Services allows local users to corrupt memory through a command that removes one event listener. The event-listener removal path mishandles that command, but Qualcomm has not published the invalid field, buffer operation, or memory boundary involved. Local access is required; Qualcomm reports no required privileges or user interaction, while the resulting execution primitive remains undisclosed.
The record
- CVE
- CVE-2023-28578
- Published
- Mar 4, 2024
- Updated
- Aug 29, 2024
- Vendor
- Qualcomm
- Product
- Robotics RB3 Platform Firmware
- Classifications
- CWE-20, CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 4, 2024CVE publishedPublication date reported by the CVE source.
- Aug 29, 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.
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