dbcve.org
Omada Er605 FirmwareOperating system · Tp Link

CVE-2024-1179

HIGH · 8.8 CVSS v3.1 Published 2024-04-01
Fix available
A fix is available. Upgrade to 2.2.4 or later.
See remediation →
93/100
Remediation priority · Urgent
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
TP-Link Omada ER605 DHCPv6 Client Options Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of TP-Link Omada ER605 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of DHCP options. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-22420.

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 confidence

A stack-based buffer overflow vulnerability exists in the TP-Link Omada ER605 router's DHCPv6 client options handling. The issue stems from insufficient validation of user-supplied data length before copying into a fixed-size stack buffer, allowing remote network-adjacent attackers to achieve arbitrary code execution with root privileges without authentication.

MitigationApply the vendor-supplied firmware patch when available. Until then, restrict network access to the router's management interface and disable DHCPv6 client functionality if not required.

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
Omada Er605 FirmwareOperating system
Affected:< 2.2.4

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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. Confirm device model is TP-Link Omada ER605
    Access the router's web management interface or check the physical device label to verify the exact model number
    Affected if Device is not an Omada ER605 router
  2. Check installed firmware version
    Log into the router's web interface and navigate to System > Firmware Upgrade, or use the CLI command 'show version' to retrieve the current firmware version
    Affected if Firmware version is lower than 2.2.4
  3. Verify DHCPv6 client status
    In the router's web interface, go to Network > DHCP > DHCPv6 Client, or check the running configuration for 'ip dhcpv6 client' settings
    Affected if DHCPv6 client is enabled and configured
  4. Assess network exposure
    Determine if the router's management interface or WAN interface is accessible from untrusted networks by reviewing firewall rules and interface bindings
    Affected if Router management or WAN is exposed to untrusted network segments

You are affected if you have an Omada ER605 router running firmware below version 2.2.4 with DHCPv6 client enabled and the router accessible from a network where attackers could send malicious DHCPv6 responses.

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.

dbcve · scoped
Upgrade available Upgrade to 2.2.4 or later
Fixed in 2.2.4
Interim mitigation

Apply the vendor-supplied firmware patch when available. Until then, restrict network access to the router's management interface and disable DHCPv6 client functionality if not required.

Recommended fix High confidence

Firmware version 2.2.4

  1. Download the fixed firmware version 2.2.4 for the Omada ER605 from the official TP-Link support website (https://www.tp-link.com/support/download/er605/)
  2. Access the Omada ER605 router's web-based management interface by entering the router's IP address in a web browser
  3. Log in to the router with administrator credentials
  4. Navigate to the firmware upgrade section (typically found under System > Firmware Upgrade, System Tools > Firmware Upgrade, or a similar menu path)
  5. Click the option to upgrade firmware and select the downloaded firmware file (2.2.4)
  6. Initiate the firmware upgrade and wait for the process to complete - do not power off or restart the router during this process
  7. After the router automatically reboots, log back into the management interface
  8. Verify the firmware version displays as 2.2.4 or later in the device status or system information page
Caveat Review release notes for any configuration changes or feature modifications between your current version and 2.2.4; backup router configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Omada Er605 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1179 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-1179 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