# CVE-2024-1137: TIBCO ActiveSpaces Information Leak Vulnerability

> An attacker can passively observe data traffic intended for other clients in TIBCO ActiveSpaces Enterprise Edition, leading to information disclosure.

- **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:** 12 Mar 2024
- **Updated:** 31 Oct 2024
- **Also known as:** GHSA-crf3-v2gr-xr72

## What is CVE-2024-1137?

CVE-2024-1137 is a medium-severity vulnerability in TIBCO ActiveSpaces - 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 Proxy and Client components of TIBCO Software Inc.'s TIBCO ActiveSpaces - Enterprise Edition contain a vulnerability that theoretically allows an Active Spaces client to passively observe data traffic to other clients. Affected releases are TIBCO Software Inc.'s TIBCO ActiveSpaces - Enterprise Edition: versions 4.4.0 through 4.9.0.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-1137 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1137 is a medium-severity vulnerability in TIBCO ActiveSpaces - 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-1137 in the wild and no public exploit code.

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

## Sources

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

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