Strix
26.1K

CVE-2017-5361

UnknownEPSS 1.37%

Last modified

CVE-2017-5361 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.37% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
1.37%

68.3th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
BestpracticalRequest Tracker4.0.0
BestpracticalRequest Tracker4.0.1
BestpracticalRequest Tracker4.0.2
BestpracticalRequest Tracker4.0.3
BestpracticalRequest Tracker4.0.4
BestpracticalRequest Tracker4.0.5
BestpracticalRequest Tracker4.0.6
BestpracticalRequest Tracker4.0.7
BestpracticalRequest Tracker4.0.8
BestpracticalRequest Tracker4.0.9
BestpracticalRequest Tracker4.0.10
BestpracticalRequest Tracker4.0.11
BestpracticalRequest Tracker4.0.12
BestpracticalRequest Tracker4.0.13
BestpracticalRequest Tracker4.0.14
BestpracticalRequest Tracker4.0.15
BestpracticalRequest Tracker4.0.16
BestpracticalRequest Tracker4.0.17
BestpracticalRequest Tracker4.0.18
BestpracticalRequest Tracker4.0.19
BestpracticalRequest Tracker4.0.20
BestpracticalRequest Tracker4.0.21
BestpracticalRequest Tracker4.0.22
BestpracticalRequest Tracker4.0.23
BestpracticalRequest Tracker4.0.24
BestpracticalRequest Tracker4.2.0
BestpracticalRequest Tracker4.2.1
BestpracticalRequest Tracker4.2.2
BestpracticalRequest Tracker4.2.3
BestpracticalRequest Tracker4.2.4
BestpracticalRequest Tracker4.2.5
BestpracticalRequest Tracker4.2.6
BestpracticalRequest Tracker4.2.7
BestpracticalRequest Tracker4.2.8
BestpracticalRequest Tracker4.2.9
BestpracticalRequest Tracker4.2.10
BestpracticalRequest Tracker4.2.11
BestpracticalRequest Tracker4.2.12
BestpracticalRequest Tracker4.2.13
BestpracticalRequest Tracker4.4.0
BestpracticalRequest Tracker4.4.1

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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.
How severe is CVE-2017-5361?
Severity scoring for CVE-2017-5361 is pending analysis. The EPSS model estimates a 1.37% probability of exploitation in the next 30 days.
How do I fix CVE-2017-5361?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-5361?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST