# CVE-2020-24581: Command injection in n/a

> An authenticated user can execute arbitrary OS commands via a hidden CGI endpoint on D-Link DSL-2888A devices.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3hhh-hv27-4gjh

## What is CVE-2020-24581?

CVE-2020-24581 is a high-severity command injection vulnerability in n/a, published on 22 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on D-Link DSL-2888A devices with firmware prior to AU_2.31_V1.1.47ae55. It contains an execute_cmd.cgi feature (that is not reachable via the web user interface) that lets an authenticated user execute Operating System commands.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Dlink Dsl2888a Firmware.

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

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

## Is CVE-2020-24581 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-24579](https://insights.sbomify.com/CVE-2020-24579/): Auth bypass in n/a (high 8.8)
- [CVE-2020-24580](https://insights.sbomify.com/CVE-2020-24580/): Auth bypass in n/a (high 7.5)
- [CVE-2020-24578](https://insights.sbomify.com/CVE-2020-24578/): Misconfiguration in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-24581 is a high-severity command injection vulnerability in n/a, published on 22 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-24581 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-24581/ (Markdown: https://insights.sbomify.com/CVE-2020-24581/index.md)
```

## Sources

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

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