CVE-2024-12009
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 post-authentication command injection vulnerability in the "ZyEE" function of the Zyxel EX5601-T1 firmware version V5.70(ACDZ.3.6)C0 and earlier could allow an authenticated attacker with administrator privileges to execute operating system (OS) commands on a vulnerable device.
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 confidencePost-authentication command injection in the ZyEE function of Zyxel EX5601-T1 firmware versions V5.70(ACDZ.3.6)C0 and earlier allows authenticated administrators to execute arbitrary OS commands, likely through improper input sanitization in the function's parameter handling.
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<= 5.50\(abvy.5.4\)c0<= 5.50\(abvy.5.4\)c0<= 5.50\(abvy.5.4\)c0<= 5.17\(abyl.8\)c0<= 5.17\(abyl.8\)c0<= 5.17\(abyo.6.4\)c0<= 5.17\(abyo.6.4\)c0<= 5.19\(acjq.1\)c1CVSS 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 device model and firmware versionAccess the device admin web interface or check the device label to determine the exact model (e.g., EX5601-T1, Dx3300, Dx4510, Dx5401, Ee6510) and navigate to the firmware/version information page to retrieve the installed firmware version stringAffected if The firmware version matches or is earlier than the affected version ranges (e.g., EX5601-T1 <= V5.70(ACDZ.3.6)C0, Dx3300 <= 5.50(abvy.5.4)c0, etc.)
-
Locate the ZyEE function in the admin interfaceLog into the device administrative interface and navigate through the menu options to find the ZyEE function or feature. This may appear under advanced settings, network functions, or a specific ZyEE configuration sectionAffected if The ZyEE function is present and accessible in the admin interface, indicating the vulnerable component exists on this device
-
Verify administrative access exposureDetermine if the device administrative interface (HTTP/HTTPS) is exposed to untrusted networks such as the public internet, or if it is accessible from non-trusted VLANs or guest networksAffected if The admin interface is reachable from untrusted networks, increasing the likelihood of exploitation since this is a post-authentication vulnerability
A user is affected if their device model and firmware version fall within the listed affected ranges AND the ZyEE function is enabled/present in their installation.
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 · scopedApply available firmware update from Zyxel; if no patch exists, restrict administrative access to trusted networks and consider disabling the ZyEE function until patched.
Latest firmware version available from Zyxel for your specific device model (newer than 5.50 for Dx3300/Dx3301, newer than 5.17 for Dx4510/Dx5401, newer than 5.19 for Ee6510)
- 1. Identify the specific model number of your Zyxel device from the affected list (Dx3300 T0, Dx3300 T1, Dx3301 T0, Dx4510 B0, Dx4510 B1, Dx5401 B0, Dx5401 B1, or Ee6510 10)
- 2. Visit the official Zyxel support website at www.zyxel.com and navigate to the firmware download section for your specific device model
- 3. Check for firmware versions newer than the affected versions listed (5.50 for Dx3300/Dx3301, 5.17 for Dx4510/Dx5401, 5.19 for Ee6510)
- 4. Download the latest available firmware version for your device model
- 5. Back up your current device configuration before applying the firmware update
- 6. Upload and apply the new firmware through the device's web administration interface
- 7. After the firmware update completes, verify the device is functioning normally and the new firmware version is installed
- 8. Confirm the vulnerability is patched by checking the release notes or security advisory for the new firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12009 — 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-12009 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