Ac6 FirmwareOperating system · Tenda

CVE-2024-52274

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-04
Fix available
A fix is available. Upgrade to after 15.03.06.50 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Stack-based Buffer Overflow vulnerability in Shenzhen Tenda Technology Co Tenda AC6V2 (setDoubleL2tpConfig->guest_ip_check(overflow arg: mask) modules) allows Overflow Buffers.This issue affects Tenda AC6V2: through 15.03.06.50

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 confidence

Stack-based buffer overflow in Tenda AC6V2 routers (through v15.03.06.50) in the guest_ip_check function called by setDoubleL2tpConfig allows overflow via the mask parameter, potentially enabling remote code execution.

MitigationApply vendor firmware patch when released; until then, restrict access to the router's management interface from untrusted networks and disable L2TP features if not needed.

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
Ac6 FirmwareOperating system
Affected:<= 15.03.06.50

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Access the router's web administration interface or check the device label to confirm the model is Tenda AC6 or AC6V2
    Affected if The device is a Tenda AC6/AC6V2 router
  2. Check the installed firmware version
    Log into the router's web interface and navigate to System Settings or Administration > Firmware Upgrade to view the current firmware version, or use the router's serial console or telnet/ssh to run 'cat /proc/version' or check /etc/version if accessible
    Affected if The firmware version is 15.03.06.50 or any version lower than 15.03.06.50
  3. Verify L2TP functionality is accessible
    Check if the router's web interface exposes L2TP configuration options, typically found under Advanced Settings or Network Settings > L2TP/PPTP, or attempt to access the setDoubleL2tpConfig endpoint via the web interface if endpoints are known
    Affected if L2TP configuration features are available and accessible on the router
  4. Confirm guest network or IP configuration is in use
    Examine if the guest network feature is enabled in the router's wireless settings, as the vulnerable function is guest_ip_check which processes the mask parameter
    Affected if Guest network features are enabled and the mask parameter can be supplied through the L2TP configuration interface

You are affected if you have a Tenda AC6/AC6V2 router running firmware version 15.03.06.50 or lower with L2TP features enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 15.03.06.50
Interim mitigation

Apply vendor firmware patch when released; until then, restrict access to the router's management interface from untrusted networks and disable L2TP features if not needed.

Fix this in Ac6 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52274 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-52274 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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