dbcve.org
Omada Er605 FirmwareOperating system · Tp Link

CVE-2024-1180

HIGH · 8.0 CVSS v3.1 Published 2024-04-03
Fix available
A fix is available. Upgrade to 2.2.3 or later.
See remediation →
82/100
Remediation priority · High
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 Access Control Command Injection Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of TP-Link Omada ER605. Authentication is required to exploit this vulnerability. The specific issue exists within the handling of the name field in the access control user interface. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-22227.

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

The TP-Link Omada ER605 router contains a command injection vulnerability in its access control feature. The 'name' field in the access control UI does not properly validate user-supplied input before passing it to a system call, allowing an authenticated attacker to execute arbitrary commands with root privileges.

MitigationApply the vendor-supplied firmware patch when available; until then, restrict network access to the management interface to trusted users only and monitor for unauthorized access control rule modifications.

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.3

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

CVSS:3.1/AV:A/AC:L/PR:L/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 device model
    Access the router management interface or check the device label to confirm the model is TP-Link Omada ER605
    Affected if The device is not an ER605 model
  2. Check the installed firmware version
    Log into the router web interface, go to System Settings > Firmware Upgrade, or use the CLI command 'show version' to display the current firmware version
    Affected if The firmware version is lower than 2.2.3 (e.g., 2.2.2, 2.2.1, 2.1.x, etc.)
  3. Verify access control feature status
    Navigate to the access control settings in the router management interface (typically under Firewall or Network Security settings) and check if any access control rules are defined
    Affected if Access control rules exist and the firmware is below 2.2.3
  4. Inspect access control rule names for anomalies
    Review each access control rule's name field for unexpected characters such as semicolons, pipes, backticks, quotes, or dollar signs that may indicate injection payloads
    Affected if Any access control rule name contains shell metacharacters or appears to encode a command

A defender is affected if they are running TP-Link Omada ER605 firmware below version 2.2.3 and have access control rules configured, making command injection possible through the rule name field.

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.3 or later
Fixed in 2.2.3
Interim mitigation

Apply the vendor-supplied firmware patch when available; until then, restrict network access to the management interface to trusted users only and monitor for unauthorized access control rule modifications.

Recommended fix High confidence

Firmware version 2.2.3

  1. Download the firmware version 2.2.3 for TP-Link Omada ER605 from the official TP-Link support website
  2. Log into the Omada ER605 router administration interface
  3. Navigate to the System settings or Firmware Upgrade section
  4. Upload the downloaded firmware version 2.2.3
  5. Wait for the upgrade process to complete and the device to reboot
  6. Verify the firmware version has been updated to 2.2.3 or later

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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