# CVE-2020-16163: Security feature bypass in n/a

> Remote attackers can bypass TLS validation in RIPE NCC RPKI Validator, potentially bypassing access restrictions or causing denial of service to routing systems.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8558-8prw-98p6

## What is CVE-2020-16163?

CVE-2020-16163 is a critical vulnerability in n/a, published on 30 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in RIPE NCC RPKI Validator 3.x before 3.1-2020.07.06.14.28. RRDP fetches proceed even with a lack of validation of a TLS HTTPS endpoint. This allows remote attackers to bypass intended access restrictions, or to trigger denial of service to traffic directed to co-dependent routing systems. NOTE: third parties assert that the behavior is intentionally permitted by RFC 8182

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2020-16163?

It affects 1 product.


Products: Ripe Rpki Validator 3.

## How do I fix CVE-2020-16163?

No fix has been published for CVE-2020-16163 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-16163 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-16162](https://insights.sbomify.com/CVE-2020-16162/): Security feature bypass in n/a (high 7.5)
- [CVE-2020-16164](https://insights.sbomify.com/CVE-2020-16164/): Security feature bypass in n/a (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-16163 and fix it if it is affected.

What it is: CVE-2020-16163 is a critical vulnerability in n/a, published on 30 Jul 2020. 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-2020-16163 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-2020-16163/ (Markdown: https://insights.sbomify.com/CVE-2020-16163/index.md)
```

## Sources

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

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