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 all
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.
- Published
- Apr 22, 2011
- Updated
- Jun 16, 2026
- EPSS
- 3.8% · 90th percentile
- CWE
- CWE-22
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.8%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| bestpractical | rt | cpe:2.3:a:bestpractical:rt |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- bestpractical rt3.2.0
- bestpractical rt3.2.1
- bestpractical rt3.2.2
- bestpractical rt3.2.3
- bestpractical rt3.4.0
- bestpractical rt3.4.1
- bestpractical rt3.4.2
- bestpractical rt3.4.3
- bestpractical rt3.4.4
- bestpractical rt3.4.5
- bestpractical rt3.4.6
- bestpractical rt3.6.0
- bestpractical rt3.6.1
- bestpractical rt3.6.10
- bestpractical rt3.6.2
- bestpractical rt3.6.3
- bestpractical rt3.6.4
- bestpractical rt3.6.5
- bestpractical rt3.6.6
- bestpractical rt3.6.7
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:5.0 | request-tracker3.6 | before 3.6.7-5+lenny6 | 3.6.7-5+lenny6 |
| Debian:6.0 | request-tracker3.8 | before 3.8.8-7+squeeze1 | 3.8.8-7+squeeze1 |
Same product
bestpractical: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-41075RT: SQL injection via entry_aggregator parameter in JSON search35Monitor
- CVE-2026-41076RT: LDAP authentication bypass via empty password32Monitor
- CVE-2011-5092Best Practical Solutions RT 3.8.x before 3.8.12 and 4.x before 4.0.6 allows remote attackers to execute arbitrary code and gain privileges v31Monitor
- CVE-2026-41074RT has broken CSRF protection for authenticated users28Monitor
- CVE-2013-3370Request Tracker (RT) 3.8.x before 3.8.17 and 4.0.x before 4.0.13 does not properly restrict access to private callback components, which all28Monitor
- CVE-2011-4458Best Practical Solutions RT 3.6.x, 3.7.x, and 3.8.x before 3.8.12 and 4.x before 4.0.6, when the VERPPrefix and VERPDomain options are enabl28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:request-tracker3.6 | 3.6.7-5+lenny6 · Debian:5.0 | Package registry (OSV) |
| debian:request-tracker3.8 | 3.8.8-7+squeeze1 · Debian:6.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- none
- Availability
- none
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
AV:N/AC:M/Au:N/C:P/I:N/A:N
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) { return res.sendStatus(400);}res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- blog.bestpractical.com/2011/04/security-vulnerabilities-in-rt.html
- lists.bestpractical.com/pipermail/rt-announce/2011-April/000187.html
- lists.bestpractical.com/pipermail/rt-announce/2011-April/000188.html
- lists.bestpractical.com/pipermail/rt-announce/2011-April/000189.html
- secunia.com/advisories/44189
- www.debian.org/security/2011/dsa-2220
- www.securityfocus.com/bid/47383
- www.vupen.com/english/advisories/2011/1071
- bugzilla.redhat.com/show_bug.cgi?id=696795
- exchange.xforce.ibmcloud.com/vulnerabilities/66795
Vendor advisories and official records. Exploit/PoC links are deliberately left out.