# CVE-2024-1138: TIBCO FTL Privilege Escalation

> A low-privileged attacker with network access can escalate privileges on the TIBCO FTL Server component.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 12 Mar 2024
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-j6ph-cmqv-q28r

## What is CVE-2024-1138?

CVE-2024-1138 is a high-severity vulnerability in TIBCO FTL - Enterprise Edition, published on 12 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The FTL Server component of TIBCO Software Inc.'s TIBCO FTL - Enterprise Edition contains a vulnerability that allows a low privileged attacker with network access to execute a privilege escalation on the affected ftlserver. Affected releases are TIBCO Software Inc.'s TIBCO FTL - Enterprise Edition: versions 6.10.1 and below.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2024-1138 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1138 is a high-severity vulnerability in TIBCO FTL - Enterprise Edition, published on 12 Mar 2024. 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-1138 in the wild and no public exploit code.

Affected product: TIBCO FTL - Enterprise Edition. 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-1138/ (Markdown: https://insights.sbomify.com/CVE-2024-1138/index.md)
```

## Sources

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

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