# CVE-2020-17505: Command injection in n/a

> Authenticated attackers can inject commands via the service-cmds parameter in Artica Web Proxy, leading to root-level code execution.

- **Severity:** High 8.8 (`CVSS:3.1/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:** 12 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m3f9-9cw6-5ccj

## What is CVE-2020-17505?

CVE-2020-17505 is a high-severity command injection vulnerability in n/a, published on 12 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Artica Web Proxy 4.30.000000 allows an authenticated remote attacker to inject commands via the service-cmds parameter in cyrus.php. These commands are executed with root privileges via service_cmds_peform.

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

## Which versions are affected by CVE-2020-17505?

It affects 1 product.


Products: Articatech Web Proxy.

## How do I fix CVE-2020-17505?

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

## Is CVE-2020-17505 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-17505 exists.

Public exploit code:

- Artica proxy 4.30.000000 Auth Bypass service-cmds-peform Command Injection (metasploit)
- Artica Web Proxy 4.30 - OS Command Injection (nuclei): http/cves/2020/CVE-2020-17505.yaml

## Other vulnerabilities in n/a

- [CVE-2020-17506](https://insights.sbomify.com/CVE-2020-17506/): SQL injection in n/a (critical 9.8)
- [CVE-2021-40680](https://insights.sbomify.com/CVE-2021-40680/): Path traversal in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-17505 and fix it if it is affected.

What it is: CVE-2020-17505 is a high-severity command injection vulnerability in n/a, published on 12 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-17505 exists.

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-2020-17505/ (Markdown: https://insights.sbomify.com/CVE-2020-17505/index.md)
```

## Sources

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

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