CVE-2017-5361

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: 2017-07-03 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-5361 is rated Low Risk (37.7/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.19%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-5361

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-14 0.36% 0.19% -0.17%
2 2025-03-30 0.70% 0.36% -0.34%
3 2025-03-29 — 0.70% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-5361

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.9 3.0 MEDIUM
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2017-5361

OS Trackers for CVE-2017-5361

vendor priority summary link
debian not yet assigned CVE-2017-5361 not yet assigned priority: Debian including 1 source packages (request-tracker4), 2 status rows across 2 suites (bookworm, bullseye): resolved 2. https://security-tracker.debian.org/tracker/CVE-2017-5361
ubuntu low CVE-2017-5361 low priority: Ubuntu including 2 source packages (request-tracker4, rt-authen-externalauth), 44 status rows across 22 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial, yakkety, zesty): DNE 20, not-affected 17, released 5, ignored 1, needed 1. https://ubuntu.com/security/CVE-2017-5361

Affected software / configurations for CVE-2017-5361

Vendor Product Version Raw CPE
bestpractical request_tracker 4.0.0 cpe:2.3:a:bestpractical:request_tracker:4.0.0:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.1 cpe:2.3:a:bestpractical:request_tracker:4.0.1:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.2 cpe:2.3:a:bestpractical:request_tracker:4.0.2:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.3 cpe:2.3:a:bestpractical:request_tracker:4.0.3:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.4 cpe:2.3:a:bestpractical:request_tracker:4.0.4:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.5 cpe:2.3:a:bestpractical:request_tracker:4.0.5:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.6 cpe:2.3:a:bestpractical:request_tracker:4.0.6:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.7 cpe:2.3:a:bestpractical:request_tracker:4.0.7:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.8 cpe:2.3:a:bestpractical:request_tracker:4.0.8:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.9 cpe:2.3:a:bestpractical:request_tracker:4.0.9:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.10 cpe:2.3:a:bestpractical:request_tracker:4.0.10:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.11 cpe:2.3:a:bestpractical:request_tracker:4.0.11:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.12 cpe:2.3:a:bestpractical:request_tracker:4.0.12:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.13 cpe:2.3:a:bestpractical:request_tracker:4.0.13:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.14 cpe:2.3:a:bestpractical:request_tracker:4.0.14:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.15 cpe:2.3:a:bestpractical:request_tracker:4.0.15:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.16 cpe:2.3:a:bestpractical:request_tracker:4.0.16:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.17 cpe:2.3:a:bestpractical:request_tracker:4.0.17:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.18 cpe:2.3:a:bestpractical:request_tracker:4.0.18:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.19 cpe:2.3:a:bestpractical:request_tracker:4.0.19:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.20 cpe:2.3:a:bestpractical:request_tracker:4.0.20:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.21 cpe:2.3:a:bestpractical:request_tracker:4.0.21:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.22 cpe:2.3:a:bestpractical:request_tracker:4.0.22:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.23 cpe:2.3:a:bestpractical:request_tracker:4.0.23:*:*:*:*:*:*:*
bestpractical request_tracker 4.0.24 cpe:2.3:a:bestpractical:request_tracker:4.0.24:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.0 cpe:2.3:a:bestpractical:request_tracker:4.2.0:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.1 cpe:2.3:a:bestpractical:request_tracker:4.2.1:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.2 cpe:2.3:a:bestpractical:request_tracker:4.2.2:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.3 cpe:2.3:a:bestpractical:request_tracker:4.2.3:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.4 cpe:2.3:a:bestpractical:request_tracker:4.2.4:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.5 cpe:2.3:a:bestpractical:request_tracker:4.2.5:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.6 cpe:2.3:a:bestpractical:request_tracker:4.2.6:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.7 cpe:2.3:a:bestpractical:request_tracker:4.2.7:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.8 cpe:2.3:a:bestpractical:request_tracker:4.2.8:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.9 cpe:2.3:a:bestpractical:request_tracker:4.2.9:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.10 cpe:2.3:a:bestpractical:request_tracker:4.2.10:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.11 cpe:2.3:a:bestpractical:request_tracker:4.2.11:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.12 cpe:2.3:a:bestpractical:request_tracker:4.2.12:*:*:*:*:*:*:*
bestpractical request_tracker 4.2.13 cpe:2.3:a:bestpractical:request_tracker:4.2.13:*:*:*:*:*:*:*
bestpractical request_tracker 4.4.0 cpe:2.3:a:bestpractical:request_tracker:4.4.0:*:*:*:*:*:*:*
bestpractical request_tracker 4.4.1 cpe:2.3:a:bestpractical:request_tracker:4.4.1:*:*:*:*:*:*:*

References for CVE-2017-5361

cvelogic Threat Intelligence