# CVE-2018-5757: Command injection in n/a

> Attackers can execute arbitrary OS commands on AudioCodes IP phones via shell metacharacters in the web UI monitoring page.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p8fp-8747-qj72

## What is CVE-2018-5757?

CVE-2018-5757 is a high-severity command injection vulnerability in n/a, published on 1 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on AudioCodes 450HD IP Phone devices with firmware 3.0.0.535.106. The traceroute and ping functionality, which uses a parameter in a request to command.cgi from the Monitoring page in the web UI, unsafely puts user-alterable data directly into an OS command, leading to Remote Code Execution via shell metacharacters in the query string.

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

## Which versions are affected by CVE-2018-5757?

It affects 1 product.


Products: Audiocodes 420hd Ip Phone Firmware.

## How do I fix CVE-2018-5757?

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

## Is CVE-2018-5757 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-10093](https://insights.sbomify.com/CVE-2018-10093/): Missing authorization in n/a (high 8.8)
- [CVE-2018-10091](https://insights.sbomify.com/CVE-2018-10091/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5757 and fix it if it is affected.

What it is: CVE-2018-5757 is a high-severity command injection vulnerability in n/a, published on 1 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-5757 in the wild and no public exploit code.

Affected product: n/a. 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-2018-5757/ (Markdown: https://insights.sbomify.com/CVE-2018-5757/index.md)
```

## Sources

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

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