Request Tracker (RT) 4.x before 4.0.25, 4.2.x before 4.2.14, and 4.4.x before 4.4.2 does not use a constant-time comparison algorithm for se
Request Tracker (RT) 4.x before 4.0.25, 4.2.x before 4.2.14, and 4.4.x before 4.4.2 does not use a constant-time comparison algorithm for secrets, which makes it easier for remote attackers to obtain sensitive user password information via a timing side-channel attack.
- Published
- Jul 3, 2017
- Updated
- Jun 16, 2026
- EPSS
- 1.4% · 71th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| bestpractical | request tracker | cpe:2.3:a:bestpractical:request_tracker |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- bestpractical request tracker4.0.0
- bestpractical request tracker4.0.1
- bestpractical request tracker4.0.10
- bestpractical request tracker4.0.11
- bestpractical request tracker4.0.12
- bestpractical request tracker4.0.13
- bestpractical request tracker4.0.14
- bestpractical request tracker4.0.15
- bestpractical request tracker4.0.16
- bestpractical request tracker4.0.17
- bestpractical request tracker4.0.18
- bestpractical request tracker4.0.19
- bestpractical request tracker4.0.2
- bestpractical request tracker4.0.20
- bestpractical request tracker4.0.21
- bestpractical request tracker4.0.22
- bestpractical request tracker4.0.23
- bestpractical request tracker4.0.24
- bestpractical request tracker4.0.3
- bestpractical request tracker4.0.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | request-tracker4 | before 4.4.1-4 | 4.4.1-4 |
| Debian:7 | request-tracker4 | before 4.0.7-5+deb7u5 | 4.0.7-5+deb7u5 |
| Debian:7 | rt-authen-externalauth | before 0.10-4+deb7u1 | 0.10-4+deb7u1 |
| Debian:8 | request-tracker4 | before 4.2.8-3+deb8u2 | 4.2.8-3+deb8u2 |
| Debian:8 | rt-authen-externalauth | before 0.25-1+deb8u1 | 0.25-1+deb8u1 |
| Debian:9 | request-tracker4 | before 4.4.1-3+deb9u1 | 4.4.1-3+deb9u1 |
Same product
bestpractical: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-44231RT: Privilege escalation and information disclosure via REST 2.0 user collection endpoint36Monitor
- CVE-2017-5944The dashboard subscription interface in Request Tracker (RT) 4.x before 4.0.25, 4.2.x before 4.2.14, and 4.4.x before 4.4.2 might allow remo36Monitor
- CVE-2017-5943Request Tracker (RT) 4.x before 4.0.25, 4.2.x before 4.2.14, and 4.4.x before 4.4.2 allows remote attackers to obtain sensitive information 35Monitor
- CVE-2021-38562Best Practical Request Tracker (RT) 4.2 before 4.2.17, 4.4 before 4.4.5, and 5.0 before 5.0.2 allows sensitive information disclosure via a 31Monitor
- CVE-2018-18898The email-ingestion feature in Best Practical Request Tracker 4.1.13 through 4.4 allows denial of service by remote attackers via an algorit31Monitor
- CVE-2013-3525SQL injection vulnerability in Approvals/ in Request Tracker (RT) 4.0.10 and earlier allows remote attackers to execute arbitrary SQL comman31Monitor
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-tracker4 | 4.4.1-4 · Debian:12 | Package registry (OSV) |
| debian:rt-authen-externalauth | 0.10-4+deb7u1 · Debian:7 | 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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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
- www.debian.org/security/2017/dsa-3882
- www.debian.org/security/2017/dsa-3883
- forum.bestpractical.com/t/security-vulnerabilities-in-rt-2017-06-15/32016
Vendor advisories and official records. Exploit/PoC links are deliberately left out.