CVE-2025-34450: Rtl 433 Project Rtl 433 buffer overflow (CVSS 7.8)

Description

merbanan/rtl_433 versions up to and including 25.02 and prior to commit 25e47f8 contain a stack-based buffer overflow vulnerability in the function parse_rfraw() located in src/rfraw.c. When processing crafted or excessively large raw RF input data, the application may write beyond the bounds of a stack buffer, resulting in memory corruption or a crash. This vulnerability can be exploited to cause a denial of service and, under certain conditions, may be leveraged for further exploitation depending on the execution environment and available mitigations.

CVSS 3.1 breakdown

Attack vectorLocal

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Rtl 433 Project Rtl 433≤ 25.02

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

Patch & vendor advisories

References

https://github.com/dd32/rtl_433/commit/25e47f8Patch
https://github.com/marlinkcyber/advisories/blob/main/advisories/MCSAID-2025-004-rtl_433-rfraw-parse-overflow.mdExploitThird Party Advisory
https://github.com/merbanan/rtl_433/issues/3375ExploitIssue TrackingPatch
https://www.vulncheck.com/advisories/merbanan-rtl-433-stack-based-buffer-overflowThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-34450 being actively exploited?

CVE-2025-34450 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.23%.

How severe is CVE-2025-34450?

CVE-2025-34450 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 0.23% probability of exploitation.

Which products are affected by CVE-2025-34450?

Affected products include Rtl 433 Project Rtl 433.

How do I fix CVE-2025-34450?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-34450 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo