CVE-2024-13030
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was found in D-Link DIR-823G 1.0.2B05_20181207. It has been rated as critical. This issue affects the function SetAutoRebootSettings/SetClientInfo/SetDMZSettings/SetFirewallSettings/SetParentsControlInfo/SetQoSSettings/SetVirtualServerSettings of the file /HNAP1/ of the component Web Management Interface. The manipulation leads to improper access controls. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCritical authentication bypass in D-Link DIR-823G router's HNAP1 web interface allows remote attackers to execute multiple configuration functions (SetAutoRebootSettings, SetClientInfo, SetDMZSettings, SetFirewallSettings, SetParentsControlInfo, SetQoSSettings, SetVirtualServerSettings) without any authentication. The CVSS 9.8 indicates trivial remote exploitation leading to complete device compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.2b05_20181207CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelCheck the device label on the router or log into the admin interface to confirm the model is D-Link DIR-823GAffected if Device model is DIR-823G
-
Check the firmware versionLog into the router admin interface (typically at 192.168.0.1) and navigate to Status or Management section to view the firmware version. Compare against 1.0.2b05_20181207Affected if Firmware version is exactly 1.0.2b05_20181207
-
Verify HNAP1 interface accessibilityAttempt to access the HNAP1 SOAP endpoint via HTTP request to the router's LAN IP (example: http://192.168.0.1/HNAP1 or check if the interface responds to HNAP1 requests)Affected if HNAP1 endpoint responds without requiring authentication credentials
-
Check if remote web management is enabledIn router admin interface, go to Management > Remote Management or similar section. Verify if remote access from WAN is permittedAffected if Remote management is enabled and the router is accessible from external networks
The device is affected if it is a D-Link DIR-823G running firmware version 1.0.2b05_20181207 with the HNAP1 web interface accessible, particularly from remote networks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedThis is an end-of-life device (2018 firmware) receiving no further updates. Replace the router with a currently supported model. If immediate replacement is impossible, disable remote web management, place device behind a firewall, and ensure it is not internet-facing.
DIR-823G latest firmware version available from D-Link (check www.dlink.com for version after 1.0.2b05_20181207)
- 1. Visit D-Link's official support page for the DIR-823G device at www.dlink.com
- 2. Navigate to the firmware downloads section for model DIR-823G
- 3. Download the latest available firmware version (check release notes for security fixes)
- 4. Access the device's web management interface at the default IP address
- 5. Navigate to the Administration or System section
- 6. Locate the firmware upgrade option and upload the downloaded firmware file
- 7. Wait for the upgrade process to complete and the device to reboot
- 8. Verify the new firmware version is installed and the device functions normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13030 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-13030 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data