Process crash via unallocated bitbuffer row
Published Apr 12, 2022 · Updated Aug 3, 2024
Out-of-bounds write in rtl_433 21.12 allows local users to crash the process by opening a crafted signal-capture file. In acurite_00275rm_decode, the three-repeat path writes an 88-bit majority-decoded row at bitbuffer->num_rows before allocating that row. The target must process the crafted file; the demonstrated consequence is an AddressSanitizer-detected abort, with no sourced confidentiality or integrity impact.
Summary
What happened
Out-of-bounds write in rtl_433 21.12 allows local users to crash the process by opening a crafted signal-capture file. In acurite_00275rm_decode, the three-repeat path writes an 88-bit majority-decoded row at bitbuffer->num_rows before allocating that row. The target must process the crafted file; the demonstrated consequence is an AddressSanitizer-detected abort, with no sourced confidentiality or integrity impact.
The record
- CVE
- CVE-2022-27419
- Published
- Apr 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 12, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
Public exploit references
- POC1 crafted signal-capture fileproof 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