# CVE-2024-42501: Authenticated Path Traversal Vulnerability Leads to a Remote Command Execution (RCE)

> Authenticated attackers can exploit path traversal in ArubaOS to install unsigned packages, leading to remote code execution and privilege escalation.

- **Severity:** High 7.2 (`CVSS:3.1/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:** 17 Sep 2024
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-97r7-fmq6-w47h

## What is CVE-2024-42501?

CVE-2024-42501 is a high-severity path traversal vulnerability in Hewlett Packard Enterprise (HPE) Aruba OS, published on 17 Sep 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An authenticated Path Traversal vulnerabilities exists in the ArubaOS. Successful exploitation of this vulnerability allows an attacker to install unsigned packages on the underlying operating system, enabling the threat actor to execute arbitrary code or install implants.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2024-42501 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42501 is a high-severity path traversal vulnerability in Hewlett Packard Enterprise (HPE) Aruba OS, published on 17 Sep 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-42501 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise (HPE) Aruba OS. 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-42501/ (Markdown: https://insights.sbomify.com/CVE-2024-42501/index.md)
```

## Sources

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

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