{"answers":{"affected":"2 open source packages ship an affected version, including routinator. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-3029 in the wild and no public exploit code.","fix":"Upgrade routinator to 0.11.3 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2022-3029 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2022-3029 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- routinator (crates.io): affected from 0.9.0; fixed in 0.11.3\n- routinator (crates.io): affected from 0.9.0; fixed in 0.11.3\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-3029/ (Markdown: https://insights.sbomify.com/CVE-2022-3029/index.md)","id":"CVE-2022-3029","markdown":"https://insights.sbomify.com/CVE-2022-3029/index.md","name":"CVE-2022-3029","record":{"aliases":["GHSA-m4vx-ccrf-w399"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"RPKI validator","requires_auth":"none","summary":"Attackers can cause Routinator to crash by sending malformed base64 data, disrupting RPKI route validation for network operators.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NLnet Labs","cpe":[{"product":"routinator","vendor":"nlnetlabs"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-241","name":"Improper Handling of Unexpected Data Type"}],"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.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Fatal error on incorrect base64 data in RRDP","id":"CVE-2022-3029","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":2,"n_references":1,"next":{"headline":"Information disclosure in GitLab","id":"CVE-2022-3030"},"packages":[{"ecosystem":"crates.io","fixed":["0.11.3"],"introduced":["0.9.0"],"last_affected":[],"package":"routinator","purl":null,"source":"GHSA-m4vx-ccrf-w399"},{"ecosystem":"crates.io","fixed":["0.11.3"],"introduced":["0.9.0"],"last_affected":[],"package":"routinator","purl":"pkg:cargo/routinator","source":"GHSA-m4vx-ccrf-w399"}],"prev":{"headline":"Race condition in Linux kernel","id":"CVE-2022-3028"},"products":["Routinator"],"published":"2022-09-13","related":[{"cvss_score":9.3,"headline":"Possible path traversal when storing RRDP responses","id":"CVE-2023-39916","kev_date_added":null,"published":"2023-09-13"},{"cvss_score":8.7,"headline":"Routinator crashes on specifically crafted RRDP XML files","id":"CVE-2026-49235","kev_date_added":null,"published":"2026-06-08"},{"cvss_score":8.3,"headline":"Routinator cache path traversal using rogue rsync URIs","id":"CVE-2026-49233","kev_date_added":null,"published":"2026-06-08"},{"cvss_score":8.2,"headline":"Routinator crashes on specifically crafted ASN strings in the API","id":"CVE-2026-49234","kev_date_added":null,"published":"2026-06-08"},{"cvss_score":7.5,"headline":"Crashes on parsing certain invalid RPKI objects","id":"CVE-2023-39915","kev_date_added":null,"published":"2023-09-13"},{"cvss_score":7.5,"headline":"Infinite length chain of RRDP repositories","id":"CVE-2021-43172","kev_date_added":null,"published":"2021-11-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["NLnet Labs"]},"summary":"Attackers can cause Routinator to crash by sending malformed base64 data, disrupting RPKI route validation for network operators.","url":"https://insights.sbomify.com/CVE-2022-3029/"}