# CVE-2024-28005: Code injection in CR2500P

> Privileged attackers can execute arbitrary scripts on various NEC Aterm routers, potentially compromising device integrity and control.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2024
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-fqmj-j6qq-43c5

## What is CVE-2024-28005?

CVE-2024-28005 is a medium-severity code injection vulnerability in NEC Corporation CR2500P, published on 28 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Aterm WG1800HP4, WG1200HS3, WG1900HP2, WG1200HP3, WG1800HP3, WG1200HS2, WG1900HP, WG1200HP2, W1200EX(-MS), WG1200HS, WG1200HP, WF300HP2, W300P, WF800HP, WR8165N, WG2200HP, WF1200HP2, WG1800HP2, WF1200HP, WG600HP, WG300HP, WF300HP, WG1800HP, WG1400HP, WR8175N, WR9300N, WR8750N, WR8160N, WR9500N, WR8600N, WR8370N, WR8170N, WR8700N, WR8300N, WR8150N, WR4100N, WR4500N, WR8100N, WR8500N, CR2500P, WR8400N, WR8200N, WR1200H, WR7870S, WR6670S, WR7850S, WR6650S, WR6600H, WR7800H, WM3400RN, WM3450RN, WM3500R, WM3600R, WM3800R, WR8166N, MR01LN MR02LN, WG1810HP(JE) and WG1810HP(MF) all versions allows a attacker who has obtained high privileges can execute arbitrary scripts.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-250 (Execution with Unnecessary Privileges)

## Which versions are affected by CVE-2024-28005?

It affects 59 products.


Products: Nec Aterm Cr2500p Firmware, Nec Aterm Mr01ln Firmware, Nec Aterm Mr02ln Firmware, Nec Aterm W1200ex-Ms Firmware, Nec Aterm W300p Firmware, Nec Aterm Wf1200hp2 Firmware, Nec Aterm Wf1200hp Firmware, Nec Aterm Wf300hp2 Firmware, Nec Aterm Wf300hp Firmware, Nec Aterm Wf800hp Firmware, Nec Aterm Wg1200hp2 Firmware, Nec Aterm Wg1200hp3 Firmware, Nec Aterm Wg1200hp Firmware, Nec Aterm Wg1200hs2 Firmware, Nec Aterm Wg1200hs3 Firmware, Nec Aterm Wg1200hs Firmware, Nec Aterm Wg1400hp Firmware, Nec Aterm Wg1800hp2 Firmware, Nec Aterm Wg1800hp3 Firmware, Nec Aterm Wg1800hp4 Firmware and 39 more.

## How do I fix CVE-2024-28005?

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

## Is CVE-2024-28005 being exploited?

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

## Other vulnerabilities in NEC Corporation CR2500P

- [CVE-2024-28007](https://insights.sbomify.com/CVE-2024-28007/): Auth bypass in CR2500P (critical 9.8)
- [CVE-2024-28008](https://insights.sbomify.com/CVE-2024-28008/): Command injection in CR2500P (critical 9.8)
- [CVE-2024-28009](https://insights.sbomify.com/CVE-2024-28009/): Auth bypass in CR2500P (critical 9.8)
- [CVE-2024-28010](https://insights.sbomify.com/CVE-2024-28010/): Hardcoded credentials in CR2500P (critical 9.8)
- [CVE-2024-28011](https://insights.sbomify.com/CVE-2024-28011/): Command injection in CR2500P (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28005 and fix it if it is affected.

What it is: CVE-2024-28005 is a medium-severity code injection vulnerability in NEC Corporation CR2500P, published on 28 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-28005 in the wild and no public exploit code.

Affected product: NEC Corporation CR2500P. 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-2024-28005/ (Markdown: https://insights.sbomify.com/CVE-2024-28005/index.md)
```

## Sources

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

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