# CVE-2024-30143: A path traversal vulnerability in HCL AppScan Traffic Recorder

> Attackers can exploit path traversal in HCL AppScan Traffic Recorder to execute code or escalate privileges on the host system.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 13 Mar 2025
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-qj9x-hh6x-5x2m

## What is CVE-2024-30143?

CVE-2024-30143 is a medium-severity path traversal vulnerability in HCL AppScan Traffic Recorder, published on 13 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HCL AppScan Traffic Recorder fails to adequately neutralize special characters within the filename, potentially allowing it to resolve to a location beyond the restricted directory. Potential exploits can completely disrupt or takeover the application or the computer where the application is running.

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

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


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

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

## Is CVE-2024-30143 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-30143 is a medium-severity path traversal vulnerability in HCL AppScan Traffic Recorder, published on 13 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-30143 in the wild and no public exploit code.

Affected product: HCL AppScan Traffic Recorder. 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-30143/ (Markdown: https://insights.sbomify.com/CVE-2024-30143/index.md)
```

## Sources

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

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