# CVE-2022-3029: Fatal error on incorrect base64 data in RRDP

> Attackers can cause Routinator to crash by sending malformed base64 data, disrupting RPKI route validation for network operators.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Sep 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m4vx-ccrf-w399

## What is CVE-2022-3029?

CVE-2022-3029 is a high-severity denial of service vulnerability in NLnet Labs Routinator, published on 13 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In NLnet Labs Routinator 0.9.0 up to and including 0.11.2, due to a mistake in error handling, data in RRDP snapshot and delta files that isn’t correctly base 64 encoded is treated as a fatal error and causes Routinator to exit. Worst case impact of this vulnerability is denial of service for the RPKI data that Routinator provides to routers. This may stop your network from validating route origins based on RPKI data. This vulnerability does not allow an attacker to manipulate RPKI data.

Weakness: CWE-241 (Improper Handling of Unexpected Data Type)

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

2 open source packages ship an affected version, including routinator. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `routinator` | crates.io | From 0.9.0 | 0.11.3 |
| `routinator` | crates.io | From 0.9.0 | 0.11.3 |

Products: Nlnetlabs Routinator.

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

Upgrade routinator to 0.11.3 or later.

## Is CVE-2022-3029 being exploited?

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

## Other vulnerabilities in NLnet Labs Routinator

- [CVE-2023-39916](https://insights.sbomify.com/CVE-2023-39916/): Possible path traversal when storing RRDP responses (critical 9.3)
- [CVE-2026-49235](https://insights.sbomify.com/CVE-2026-49235/): Routinator crashes on specifically crafted RRDP XML files (high 8.7)
- [CVE-2026-49233](https://insights.sbomify.com/CVE-2026-49233/): Routinator cache path traversal using rogue rsync URIs (high 8.3)
- [CVE-2026-49234](https://insights.sbomify.com/CVE-2026-49234/): Routinator crashes on specifically crafted ASN strings in the API (high 8.2)
- [CVE-2023-39915](https://insights.sbomify.com/CVE-2023-39915/): Crashes on parsing certain invalid RPKI objects (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3029 is a high-severity denial of service vulnerability in NLnet Labs Routinator, published on 13 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3029 in the wild and no public exploit code.

Affected packages and fixed versions:
- routinator (crates.io): affected from 0.9.0; fixed in 0.11.3
- routinator (crates.io): affected from 0.9.0; fixed in 0.11.3

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-3029/ (Markdown: https://insights.sbomify.com/CVE-2022-3029/index.md)
```

## Sources

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

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