CVE-2024-0717: D-Link Good Line Router v2 HTTP GET Request devinfo information disclosure
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 18.1% (FIRST EPSS); higher than 97.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 18.1% · 97th percentile
- CWE
- CWE-200
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 5 / 30 · 18.1%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.3
- CNA · VulDB
- 5.3
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| dlink | dir-825acg1 firmware | cpe:2.3:o:dlink:dir-825acg1_firmware |
| dlink | dir-825acg1 | cpe:2.3:h:dlink:dir-825acg1 |
| dlink | dir-841 firmware | cpe:2.3:o:dlink:dir-841_firmware |
| dlink | dir-841 | cpe:2.3:h:dlink:dir-841 |
| dlink | dir-1260 firmware | cpe:2.3:o:dlink:dir-1260_firmware |
| dlink | dir-1260 | cpe:2.3:h:dlink:dir-1260 |
| dlink | dir-822 firmware | cpe:2.3:o:dlink:dir-822_firmware |
| dlink | dir-822 | cpe:2.3:h:dlink:dir-822 |
| dlink | dir-x1530 firmware | cpe:2.3:o:dlink:dir-x1530_firmware |
| dlink | dir-x1530 | cpe:2.3:h:dlink:dir-x1530 |
| dlink | dir-825 firmware | cpe:2.3:o:dlink:dir-825_firmware |
| dlink | dir-825 | cpe:2.3:h:dlink:dir-825 |
and 76 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dlink dap-1360 firmwareup to 2024-01-12 inclusive
- dlink dir-1210 firmwareup to 2024-01-12 inclusive
- dlink dir-1260 firmwareup to 2024-01-12 inclusive
- dlink dir-2150 firmwareup to 2024-01-12 inclusive
- dlink dir-300 firmwareup to 2024-01-12 inclusive
- dlink dir-615 firmwareup to 2024-01-12 inclusive
- dlink dir-615gf firmwareup to 2024-01-12 inclusive
- dlink dir-615s firmwareup to 2024-01-12 inclusive
- dlink dir-615t firmwareup to 2024-01-12 inclusive
- dlink dir-620 firmwareup to 2024-01-12 inclusive
- dlink dir-620s firmwareup to 2024-01-12 inclusive
- dlink dir-806a firmwareup to 2024-01-12 inclusive
- dlink dir-815 firmwareup to 2024-01-12 inclusive
- dlink dir-815/ac firmwareup to 2024-01-12 inclusive
- dlink dir-815s firmwareup to 2024-01-12 inclusive
- dlink dir-816 firmwareup to 2024-01-12 inclusive
- dlink dir-820 firmwareup to 2024-01-12 inclusive
- dlink dir-822 firmwareup to 2024-01-12 inclusive
- dlink dir-825 firmwareup to 2024-01-12 inclusive
- dlink dir-825ac firmwareup to 2024-01-12 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulDB). Independent of NVD's CPE analysis and usually ahead of it.
D-Link DAP-1360
- 20240112affected
D-Link DIR-1210
- 20240112affected
D-Link DIR-1260
- 20240112affected
D-Link DIR-2150
- 20240112affected
D-Link DIR-300
- 20240112affected
D-Link DIR-615
- 20240112affected
D-Link DIR-615GF
- 20240112affected
D-Link DIR-615S
- 20240112affected
D-Link DIR-615T
- 20240112affected
D-Link DIR-620
- 20240112affected
D-Link DIR-620S
- 20240112affected
D-Link DIR-806A
- 20240112affected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- 99iz (VulDB User)reporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-200 · Exposure of Sensitive Information to an Unauthorized ActorCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Root cause
The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.
The bug in code
The whole CWE-200 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
{
"permissions": ["tabs", "<all_urls>"],
"background": { "service_worker": "analytics.js" }
}Fixed
{
"permissions": ["activeTab"],
"host_permissions": ["https://yildiz.example/*"]
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- ExcavationCAPEC-116likelihood: High · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- FootprintingCAPEC-169likelihood: High · Very Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- FingerprintingCAPEC-224likelihood: High · Very Low
- ICMP Echo Request PingCAPEC-285likelihood: Medium · Low
- TCP SYN ScanCAPEC-287Low
- Enumerate Mail Exchange (MX) RecordsCAPEC-290Low
ATT&CK techniques
- System Service DiscoveryT1007
- System Network Configuration DiscoveryT1016
- Remote System DiscoveryT1018
- System Owner/User DiscoveryT1033
- Masquerading: Match Legitimate Name or LocationT1036.005
- Network Service ScanningT1046
- System Network Connections DiscoveryT1049
- Process DiscoveryT1057
- Permission Groups DiscoveryT1069
- System Information DiscoveryT1082
- File and Directory DiscoveryT1083
- Account DiscoveryT1087
- Multi-Factor Authentication InterceptionT1111
- Peripheral Device DiscoveryT1120
- System Time DiscoveryT1124
- Access Token Manipulation:Token Impersonation/TheftT1134.001
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.