# CVE-2011-1688: Path traversal in n/a

> Remote attackers can read arbitrary files from the server via crafted HTTP requests in the RT ticketing system.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Apr 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-23qv-956x-w2hr

## What is CVE-2011-1688?

CVE-2011-1688 is a medium-severity path traversal vulnerability in n/a, published on 22 Apr 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in Best Practical Solutions RT 3.2.0 through 3.6.10, 3.8.0 through 3.8.9, and 4.0.0rc through 4.0.0rc7 allows remote attackers to read arbitrary files via a crafted HTTP request.

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

## Which versions are affected by CVE-2011-1688?

It affects 1 product.


Products: Bestpractical Rt.

## How do I fix CVE-2011-1688?

Upgrade to a fixed version.

## Is CVE-2011-1688 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-5092](https://insights.sbomify.com/CVE-2011-5092/): Privilege escalation in n/a (high 7.5)
- [CVE-2013-3370](https://insights.sbomify.com/CVE-2013-3370/): Missing authorization in n/a (medium 6.8)
- [CVE-2012-4732](https://insights.sbomify.com/CVE-2012-4732/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2011-2085](https://insights.sbomify.com/CVE-2011-2085/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2011-4458](https://insights.sbomify.com/CVE-2011-4458/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1688 and fix it if it is affected.

What it is: CVE-2011-1688 is a medium-severity path traversal vulnerability in n/a, published on 22 Apr 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-1688 in the wild and no public exploit code.

Affected product: n/a. 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-2011-1688/ (Markdown: https://insights.sbomify.com/CVE-2011-1688/index.md)
```

## Sources

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

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