# CVE-2023-45579: Memory corruption in n/a

> Remote attackers can execute arbitrary code on D-Link routers via a buffer overflow in the jingx.asp function.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 16 Oct 2023
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-95pq-x7mh-2f6c

## What is CVE-2023-45579?

CVE-2023-45579 is a critical memory corruption vulnerability in n/a, published on 16 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer Overflow vulnerability in D-Link device DI-7003GV2.D1 v.23.08.25D1 and before, DI-7100G+V2.D1 v.23.08.23D1 and before, DI-7100GV2.D1 v.23.08.23D1, DI-7200G+V2.D1 v.23.08.23D1 and before, DI-7200GV2.E1 v.23.08.23E1 and before, DI-7300G+V2.D1 v.23.08.23D1, and DI-7400G+V2.D1 v.23.08.23D1 and before allows a remote attacker to execute arbitrary code via the ip/type parameter of the jingx.asp function.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-45579?

It affects 7 products.


Products: Dlink Di-7003g Firmware, Dlink Di-7100g\+ Firmware, Dlink Di-7100g Firmware, Dlink Di-7200g\+ Firmware, Dlink Di-7200g Firmware, Dlink Di-7300g\+ Firmware, Dlink Di-7400g\+ Firmware.

## How do I fix CVE-2023-45579?

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

## Is CVE-2023-45579 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-45572](https://insights.sbomify.com/CVE-2023-45572/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-45573](https://insights.sbomify.com/CVE-2023-45573/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-45574](https://insights.sbomify.com/CVE-2023-45574/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-45575](https://insights.sbomify.com/CVE-2023-45575/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-45576](https://insights.sbomify.com/CVE-2023-45576/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-45579 and fix it if it is affected.

What it is: CVE-2023-45579 is a critical memory corruption vulnerability in n/a, published on 16 Oct 2023. 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-2023-45579 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-2023-45579/ (Markdown: https://insights.sbomify.com/CVE-2023-45579/index.md)
```

## Sources

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

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