# CVE-2024-5227: TP-Link Omada ER605 PPTP VPN username Command Injection Remote Code Execution Vulnerability

> Network-adjacent attackers can execute arbitrary code as root on TP-Link Omada ER605 routers via command injection in PPTP VPN username handling.

- **Severity:** High 7.5 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2024
- **Updated:** 3 Sep 2024

## What is CVE-2024-5227?

CVE-2024-5227 is a high-severity command injection vulnerability in TP-Link Omada ER605, published on 23 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TP-Link Omada ER605 PPTP VPN username Command Injection 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. However, devices are only vulnerable if configured to use a PPTP VPN with LDAP authentication.

The specific flaw exists within the handling of the username parameter provided to the /usr/bin/pppd endpoint. 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-22446.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2024-5227?

It affects 1 product.


Products: Tp-Link Omada Er605 Firmware.

## How do I fix CVE-2024-5227?

No fix has been published for CVE-2024-5227 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-5227 being exploited?

There is no known exploitation of CVE-2024-5227 in the wild and no public exploit code.

## Other vulnerabilities in TP-Link Omada ER605

- [CVE-2024-25139](https://insights.sbomify.com/CVE-2024-25139/): Integer overflow in n/a (critical 10.0)
- [CVE-2024-5228](https://insights.sbomify.com/CVE-2024-5228/): TP-Link Omada ER605 Comexe DDNS Response Handling Heap-based Buffer Overflow Remote Code Execution Vulnerability (high 7.5)
- [CVE-2024-5242](https://insights.sbomify.com/CVE-2024-5242/): TP-Link Omada ER605 Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 7.5)
- [CVE-2024-5243](https://insights.sbomify.com/CVE-2024-5243/): TP-Link Omada ER605 Buffer Overflow Remote Code Execution Vulnerability (high 7.5)
- [CVE-2024-1179](https://insights.sbomify.com/CVE-2024-1179/): TP-Link Omada ER605 DHCPv6 Client Options Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5227 and fix it if it is affected.

What it is: CVE-2024-5227 is a high-severity command injection vulnerability in TP-Link Omada ER605, published on 23 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5227 in the wild and no public exploit code.

Affected product: TP-Link Omada ER605. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-5227/ (Markdown: https://insights.sbomify.com/CVE-2024-5227/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-5227
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-5227
- OSV: https://osv.dev/vulnerability/CVE-2024-5227

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-5227/
Summaries are generated and may contain mistakes; the official description above is the record.