# CVE-2024-38494: Symantec Privileged Access Manager Remote Command Execution vulnerability

> A high-privileged authenticated user can execute arbitrary commands on the Symantec Privileged Access Manager system via a crafted HTTP request.

- **Severity:** High 8.6 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-m9f2-w9fv-j46g

## What is CVE-2024-38494?

CVE-2024-38494 is a high-severity command injection vulnerability in Broadcom Symantec Privileged Access Management, published on 15 Jul 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

This vulnerability allows a high-privileged authenticated PAM user to achieve remote command execution on the affected PAM system by sending a specially crafted HTTP request.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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


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

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

## Is CVE-2024-38494 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38494 is a high-severity command injection vulnerability in Broadcom Symantec Privileged Access Management, published on 15 Jul 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-38494 in the wild and no public exploit code.

Affected product: Broadcom Symantec Privileged Access Management. 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-38494/ (Markdown: https://insights.sbomify.com/CVE-2024-38494/index.md)
```

## Sources

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

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