# CVE-2024-8781: Container Escape Vulnerability in TR7's Application Security Platform (ASP)

> Attackers can escape containers and escalate privileges in TR7's Application Security Platform due to improper protection of alternate paths.

- **Severity:** High 8.7 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2024
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-x9xr-4q3h-r33w

## What is CVE-2024-8781?

CVE-2024-8781 is a high-severity vulnerability in TR7 Application Security Platform (ASP), published on 18 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Execution with Unnecessary Privileges, : Improper Protection of Alternate Path vulnerability in TR7 Application Security Platform (ASP) allows Privilege Escalation, -Privilege Abuse.

This issue affects Application Security Platform (ASP): v1.4.25.188.

Weakness: CWE-424 (Improper Protection of Alternate Path), CWE-250 (Execution with Unnecessary Privileges)

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


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

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

## Is CVE-2024-8781 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8781 is a high-severity vulnerability in TR7 Application Security Platform (ASP), published on 18 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8781 in the wild and no public exploit code.

Affected product: TR7 Application Security Platform (ASP). 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-8781/ (Markdown: https://insights.sbomify.com/CVE-2024-8781/index.md)
```

## Sources

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

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