# CVE-2022-27419: Memory corruption in n/a

> Attackers can cause a denial of service in rtl_433 via a crafted file triggering a stack overflow in the Acurite decoder.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-27419, GHSA-85w3-6f4c-mf9j, UBUNTU-CVE-2022-27419, openSUSE-SU-2024:11994-1

## What is CVE-2022-27419?

CVE-2022-27419 is a medium-severity memory corruption vulnerability in n/a, published on 12 Apr 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

rtl_433 21.12 was discovered to contain a stack overflow in the function acurite_00275rm_decode at /devices/acurite.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted file.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-27419?

It affects 1 product.


Products: Rtl 433 Project Rtl 433.

## How do I fix CVE-2022-27419?

Upgrade to a fixed version.

## Is CVE-2022-27419 being exploited?

There is no known exploitation of CVE-2022-27419 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-34450](https://insights.sbomify.com/CVE-2025-34450/): merbanan/rtl_433 <= 25.02 Stack-based Buffer Overflow (medium 6.9)
- [CVE-2022-25051](https://insights.sbomify.com/CVE-2022-25051/): Integer overflow in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-27419 and fix it if it is affected.

What it is: CVE-2022-27419 is a medium-severity memory corruption vulnerability in n/a, published on 12 Apr 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-27419 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-27419/ (Markdown: https://insights.sbomify.com/CVE-2022-27419/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-27419
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-27419
- OSV: https://osv.dev/vulnerability/CVE-2022-27419

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-27419/
Summaries are generated and may contain mistakes; the official description above is the record.