# CVE-2024-0717: D-Link Good Line Router v2 HTTP GET Request devinfo information disclosure

> Remote attackers can access sensitive device information via the /devinfo endpoint on multiple D-Link router models.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 19 Jan 2024
- **Updated:** 30 May 2025
- **Also known as:** GHSA-27wg-r456-jc87

## What is CVE-2024-0717?

CVE-2024-0717 is a medium-severity vulnerability in Dlink Dir-816 Firmware, published on 19 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability classified as critical was found in D-Link DAP-1360, DIR-300, DIR-615, DIR-615GF, DIR-615S, DIR-615T, DIR-620, DIR-620S, DIR-806A, DIR-815, DIR-815AC, DIR-815S, DIR-816, DIR-820, DIR-822, DIR-825, DIR-825AC, DIR-825ACF, DIR-825ACG1, DIR-841, DIR-842, DIR-842S, DIR-843, DIR-853, DIR-878, DIR-882, DIR-1210, DIR-1260, DIR-2150, DIR-X1530, DIR-X1860, DSL-224, DSL-245GR, DSL-2640U, DSL-2750U, DSL-G2452GR, DVG-5402G, DVG-5402G, DVG-5402GFRU, DVG-N5402G, DVG-N5402G-IL, DWM-312W, DWM-321, DWR-921, DWR-953 and Good Line Router v2 up to 20240112. This vulnerability affects unknown code of the file /devinfo of the component HTTP GET Request Handler. The manipulation of the argument area with the input notice|net|version leads to information disclosure. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-251542 is the identifier assigned to this vulnerability.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 44 products.


Products: Dlink Dap-1360 Firmware, Dlink Dir-1210 Firmware, Dlink Dir-1260 Firmware, Dlink Dir-2150 Firmware, Dlink Dir-300 Firmware, Dlink Dir-615 Firmware, Dlink Dir-615gf Firmware, Dlink Dir-615s Firmware, Dlink Dir-615t Firmware, Dlink Dir-620 Firmware, Dlink Dir-620s Firmware, Dlink Dir-806a Firmware, Dlink Dir-815\/Ac Firmware, Dlink Dir-815 Firmware, Dlink Dir-815s Firmware, Dlink Dir-816 Firmware, Dlink Dir-820 Firmware, Dlink Dir-822 Firmware, Dlink Dir-825 Firmware, Dlink Dir-825ac Firmware and 24 more.

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

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

## Is CVE-2024-0717 being exploited?

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

## Other vulnerabilities in Dlink Dir-816 Firmware

- [CVE-2023-32136](https://insights.sbomify.com/CVE-2023-32136/): D-Link DAP-1360 webproc var:menu Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-32139](https://insights.sbomify.com/CVE-2023-32139/): D-Link DAP-1360 webproc Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-32141](https://insights.sbomify.com/CVE-2023-32141/): D-Link DAP-1360 webproc WEB_DisplayPage Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-32142](https://insights.sbomify.com/CVE-2023-32142/): D-Link DAP-1360 webproc var:page Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-32143](https://insights.sbomify.com/CVE-2023-32143/): D-Link DAP-1360 webupg UPGCGI_CheckAuth Numeric Truncation Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0717 is a medium-severity vulnerability in Dlink Dir-816 Firmware, published on 19 Jan 2024. 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-2024-0717 exists.

Affected product: Dlink Dir-816 Firmware. 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-0717/ (Markdown: https://insights.sbomify.com/CVE-2024-0717/index.md)
```

## Sources

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

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