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

> An attacker can exploit DNS rebinding in Freebox v5 to bypass security controls and access internal network resources.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3fxq-98r3-r3g2

## What is CVE-2020-24374?

CVE-2020-24374 is a critical server-side request forgery vulnerability in n/a, published on 16 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A DNS rebinding vulnerability in Freebox v5 before 1.5.29.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Free Freebox Hd Firmware.

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

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

## Is CVE-2020-24374 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-24374 is a critical server-side request forgery vulnerability in n/a, published on 16 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-24374 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-24374/ (Markdown: https://insights.sbomify.com/CVE-2020-24374/index.md)
```

## Sources

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

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