# CVE-2024-3262: Information exposure vulnerability in Request Tracker (RT)

> Local attackers can retrieve sensitive application data from the browser cache after session termination, exposing vulnerability tickets.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Apr 2024
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-3262, GHSA-6426-p644-ffcf, UBUNTU-CVE-2024-3262

## What is CVE-2024-3262?

CVE-2024-3262 is a medium-severity vulnerability in Best Practical Solutions Request Tracker, published on 4 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Information exposure vulnerability in RT software affecting version 4.4.1. This vulnerability allows an attacker with local access to the device to retrieve sensitive information about the application, such as vulnerability tickets, because the application stores the information in the browser cache, leading to information exposure despite session termination.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

Upgrade to a fixed version.

## Is CVE-2024-3262 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3262 is a medium-severity vulnerability in Best Practical Solutions Request Tracker, published on 4 Apr 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-3262 in the wild and no public exploit code.

Affected product: Best Practical Solutions Request Tracker. 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-3262/ (Markdown: https://insights.sbomify.com/CVE-2024-3262/index.md)
```

## Sources

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

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