CVE-2024-3659
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 · uneditedFirmware in KAON AR2140 routers, prior to versions 3.2.50 and 4.2.16, is vulnerable to a shell command injection via sending a crafted request to one of the endpoints. In order to exploit this vulnerability, one has to have access to the administrative portal of the router.
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 · moderate confidenceKAON AR2140 router firmware contains a shell command injection vulnerability in one of its administrative endpoints. Attackers with administrative portal access can send crafted requests containing malicious shell commands that the underlying operating system will execute with elevated privileges.
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>= 3.2.46, < 4.2.16CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 device modelAccess the router administrative interface or check the device label to confirm the model is KAON AR2140Affected if The device is not a KAON AR2140 router, then this CVE does not apply
-
Determine the installed firmware versionLog into the router administrative portal and navigate to the status or system information page to view the current firmware versionAffected if The firmware version cannot be determined or the device does not have an accessible administrative interface
-
Compare the firmware version against the vulnerable rangeReview the firmware version number identified in the previous step and determine if it falls within >= 3.2.46 and < 4.2.16Affected if The installed version is 3.2.46 or higher but lower than 4.2.16, indicating the device is running a vulnerable firmware version
-
Assess administrative portal accessibilityDetermine if the router administrative web interface is accessible from untrusted networks or the internetAffected if The administrative portal is exposed to untrusted networks, which would allow an attacker to attempt the command injection
The device is affected if it is a KAON AR2140 router running firmware version 3.2.46 or higher but lower than 4.2.16, and the administrative portal is accessible to an attacker.
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 · scoped4.2.16
Update KAON AR2140 router firmware to versions 3.2.50 or 4.2.16 or later to remediate this vulnerability. Restrict administrative portal access to trusted networks or IP addresses as an interim control.
4.2.16 (or 3.2.50+ for the 3.x branch)
- Download firmware version 4.2.16 or later from the vendor's support site
- Alternatively, if staying on the 3.x branch, download firmware version 3.2.50 or later
- Access the router's administrative web interface
- Navigate to the firmware upgrade or system settings section
- Upload and apply the new firmware version
- Verify the upgrade was successful and the router is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3659 — 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-3659 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