# CVE-2018-12237: Command injection in Symantec Reporter

> An authenticated administrator can execute arbitrary OS commands with elevated privileges via the Symantec Reporter CLI.

- **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:** 24 Jan 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9696-8p87-q8wc

## What is CVE-2018-12237?

CVE-2018-12237 is a high-severity command injection vulnerability in Symantec Reporter, published on 24 Jan 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Symantec Reporter CLI 10.1 prior to 10.1.5.6 and 10.2 prior to 10.2.1.8 is susceptible to an OS command injection vulnerability. An authenticated malicious administrator with Enable mode access can execute arbitrary OS commands with elevated system privileges.

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

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

It affects 1 product.


Products: Symantec Reporter.

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

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

## Is CVE-2018-12237 being exploited?

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

## Other vulnerabilities in Symantec Reporter

- [CVE-2017-15531](https://insights.sbomify.com/CVE-2017-15531/): Auth bypass in Reporter (critical 9.8)
- [CVE-2019-12753](https://insights.sbomify.com/CVE-2019-12753/): Information disclosure in Symantec Reporter (medium 4.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12237 is a high-severity command injection vulnerability in Symantec Reporter, published on 24 Jan 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-12237 in the wild and no public exploit code.

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

## Sources

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

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