rtl_433 through 25.12 Stack-Based Buffer Overflow via Proflame 2 Decoder
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
rtl_433, a tool that decodes signals from radio-connected devices, is affected through its Proflame 2 decoder. A nearby attacker transmitting a specially crafted radio signal, or someone supplying a malicious signal file, could crash the program and corrupt its memory, potentially allowing an attacker to take control of it on builds lacking stack protections.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
rtl_433 through 25.12 contains a stack-based buffer overflow vulnerability in proflame2_mc() that allows nearby attackers to write past a 7-byte stack buffer by sending more than seven valid Manchester-coded words. Attackers can transmit a crafted OOK radio signal or supply a crafted signal file to crash rtl_433 and corrupt stack memory, enabling control-flow hijacking on builds without stack canaries.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- merbanan rtl_433
From 21.12 · through 25.12