CVE-2024-4021
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 Keenetic KN-1010, KN-1410, KN-1711, KN-1810 and KN-1910 up to 4.1.2.15. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /ndmComponents.js of the component Configuration Setting Handler. The manipulation leads to information disclosure. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-261673 was assigned to this vulnerability. NOTE: The vendor is aware of this issue and plans to fix it by the end of 2024.
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 confidenceAn information disclosure vulnerability exists in the web interface of Keenetic KN-series routers (KN-1010, KN-1410, KN-1711, KN-1810, KN-1910) up to firmware 4.1.2.15. The vulnerability is in the Configuration Setting Handler component within the /ndmComponents.js file, allowing remote attackers to potentially access sensitive configuration data. A public exploit exists, increasing urgency.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 Keenetic router modelAccess the router web interface or check the device label to confirm the model is one of: KN-1010, KN-1410, KN-1711, KN-1810, or KN-1910Affected if The device is a Keenetic KN-series model listed in this CVE
-
Check the installed firmware versionLog into the router web interface and navigate to System > Firmware or check the home page for the firmware version numberAffected if The firmware version is 4.1.2.15 or lower (any version up to and including 4.1.2.15)
-
Confirm the web interface is accessibleAttempt to reach the router web interface over HTTP/HTTPS from a network-connected deviceAffected if The web interface responds to requests (the vulnerability requires the web interface to be reachable)
The environment is affected if you have a KN-1010, KN-1410, KN-1711, KN-1810, or KN-1910 router running firmware 4.1.2.15 or lower with the web interface accessible to network attackers.
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 · scopedRestrict web interface access to trusted networks or VPNs until the vendor-supplied firmware patch is available. Monitor vendor advisories for the scheduled fix by end of 2024 and apply updates promptly.
- No fix is currently available. Monitor vendor release notes for firmware updates addressing CVE-2024-4021.
- If available, consider network segmentation to limit exposure of the affected device's management interface.
- Follow vendor guidance for secure configuration of the Keenetic device.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4021 — 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-4021 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