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

> Authenticated administrators can execute arbitrary commands as root on Veritas NetBackup Appliances due to insufficient input filtering.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-78wx-v5xq-93gg

## What is CVE-2018-18652?

CVE-2018-18652 is a high-severity command injection vulnerability in n/a, published on 25 Oct 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A remote command execution vulnerability in Veritas NetBackup Appliance before 3.1.2 allows authenticated administrators to execute arbitrary commands as root. This issue was caused by insufficient filtering of user provided input.

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

It affects 1 product.


Products: Veritas Netbackup Appliance.

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

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

## Is CVE-2018-18652 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-8859](https://insights.sbomify.com/CVE-2017-8859/): Command injection in n/a (critical 9.8)
- [CVE-2019-9867](https://insights.sbomify.com/CVE-2019-9867/): Information disclosure in n/a (high 7.2)
- [CVE-2019-9868](https://insights.sbomify.com/CVE-2019-9868/): Information disclosure in n/a (high 7.2)
- [CVE-2023-37237](https://insights.sbomify.com/CVE-2023-37237/): Privilege escalation in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18652 is a high-severity command injection vulnerability in n/a, published on 25 Oct 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-18652 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-18652/ (Markdown: https://insights.sbomify.com/CVE-2018-18652/index.md)
```

## Sources

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

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