# CVE-2020-16248: Server-side request forgery in n/a

> Attackers can exploit Server-Side Request Forgery in Prometheus Blackbox Exporter to access internal resources via the probe target parameter.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** CLEANSTART-2026-QQ16629, DEBIAN-CVE-2020-16248, GHSA-8jrj-57gq-475g

## What is CVE-2020-16248?

CVE-2020-16248 is a medium-severity server-side request forgery vulnerability in n/a, published on 9 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Prometheus Blackbox Exporter through 0.17.0 allows /probe?target= SSRF. NOTE: follow-on discussion suggests that this might plausibly be interpreted as both intended functionality and also a vulnerability

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Prometheus Blackbox Exporter.

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

Upgrade to a fixed version.

## Is CVE-2020-16248 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-16248 exists.

Public exploit code:

- Prometheus Blackbox Exporter - Server-Side Request Forgery (SSRF) (nuclei): http/cves/2020/CVE-2020-16248.yaml

## Other vulnerabilities in n/a

- [CVE-2023-26735](https://insights.sbomify.com/CVE-2023-26735/): Server-side request forgery in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-16248 is a medium-severity server-side request forgery vulnerability in n/a, published on 9 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-16248 exists.

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

## Sources

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

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