CVE-2024-51314
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 · uneditedThe Tenda TX9 V22.03.02.20 firmware has a stack overflow vulnerability in the sub_424CE0 function of the file /goform/setMacFilterCfg.
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 confidenceA stack overflow vulnerability exists in the sub_424CE0 function within the /goform/setMacFilterCfg endpoint of Tenda TX9 firmware v22.03.02.20. This allows remote attackers to overflow a stack-based buffer, potentially enabling arbitrary code execution or device compromise.
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
- 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.
-
Confirm Tenda TX9 router modelLog into the router web interface or check the device label to verify the model is Tenda TX9Affected if Device is not a Tenda TX9 router (different models may have different vulnerabilities)
-
Check firmware versionNavigate to the router web interface System Settings or Firmware Upgrade page to view the current firmware version, or use the telnet/SSH interface and run 'cat /proc/version' or 'ver' commandAffected if Firmware version is V22.03.02.20 (this is the specific version containing the vulnerability)
-
Verify web management interface accessibilityAttempt to access the router login page from both LAN and WAN interfaces by navigating to the router IP address in a web browserAffected if The /goform/setMacFilterCfg endpoint is reachable over the network (this is the vulnerable interface)
-
Check if Mac Filter feature is enabledLog into the router web interface and navigate to the MAC Filtering or Access Control settings page to see if any filter rules are configuredAffected if Mac Filter functionality is present and accessible (the vulnerability lies in the setMacFilterCfg function)
The environment is affected if it is a Tenda TX9 router running firmware V22.03.02.20 with the web management interface and Mac Filter feature 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.
From vendor dataUpdate to a patched firmware version if available; otherwise, restrict network access to the device's web interface and disable the MAC filter functionality until a fix is released.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51314 — 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-51314 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