CVE-2017-5944

The 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 remote authenticated users with certain privileges to execute arbitrary code via a crafted saved search name.

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-5944 is rated High Risk (65.3/100): CVSS High severity, with medium exploitation likelihood (EPSS 2.78%). High exploitation likelihood—assess exposure and prioritize remediation.

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-5944

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-06-15 2.27% 2.78% +0.51%
2 2026-05-14 4.16% 2.27% -1.88%
3 2026-03-06 — 4.16% —

Full EPSS history (13 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
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:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
6.5 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.0 6.4 [email protected]

Weakness enumeration for CVE-2017-5944

OS Trackers for CVE-2017-5944

vendor priority summary link
debian not yet assigned CVE-2017-5944 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-5944
ubuntu medium CVE-2017-5944 medium priority: Ubuntu including 1 source packages (request-tracker4), 22 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): not-affected 17, released 2, DNE 1, ignored 1, needed 1. https://ubuntu.com/security/CVE-2017-5944

Affected software / configurations for CVE-2017-5944

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-5944

cvelogic Threat Intelligence