# CVE-2020-9376: Information disclosure in n/a

> Attackers can retrieve sensitive account information from unsupported D-Link DIR-610 routers via a crafted request to getcfg.php.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** No
- **Published:** 9 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2qxc-rcjp-37j2

## What is CVE-2020-9376?

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

### Official description

D-Link DIR-610 devices allow Information Disclosure via SERVICES=DEVICE.ACCOUNT%0AAUTHORIZED_GROUP=1 to getcfg.php. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Dlink Dir-610 Firmware.

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

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

## Is CVE-2020-9376 being exploited?

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

Public exploit code:

- Exploits for CVE-2020-9376 and CVE-2020-9377 (github_poc): https://github.com/renatoalencar/dlink-dir610-exploits
- D-Link DIR-610 Devices - Information Disclosure (nuclei): http/cves/2020/CVE-2020-9376.yaml

## Other vulnerabilities in n/a

- [CVE-2020-9377](https://insights.sbomify.com/CVE-2020-9377/): D-Link DIR-610 Devices Remote Command Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

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

## Sources

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

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