# CVE-2020-9278: Missing authorization in n/a

> An unauthenticated attacker can reset the D-Link DSL-2640B router to its default configuration by accessing a specific URL.

- **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:** 20 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wj3j-vfvc-g245

## What is CVE-2020-9278?

CVE-2020-9278 is a critical missing authorization vulnerability in n/a, published on 20 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on D-Link DSL-2640B B2 EU_4.01B devices. The device can be reset to its default configuration by accessing an unauthenticated URL.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Dlink Dsl-2640b Firmware.

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

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

## Is CVE-2020-9278 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-9275](https://insights.sbomify.com/CVE-2020-9275/): Information disclosure in n/a (critical 9.8)
- [CVE-2020-9277](https://insights.sbomify.com/CVE-2020-9277/): Auth bypass in n/a (critical 9.8)
- [CVE-2020-9279](https://insights.sbomify.com/CVE-2020-9279/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-9276](https://insights.sbomify.com/CVE-2020-9276/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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