CVE Vulnerabilities

CVE-2021-38562

Observable Discrepancy

Published: Oct 18, 2021 | Modified: Nov 07, 2023
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu
LOW

Best 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 timing attack against lib/RT/REST2/Middleware/Auth.pm.

Weakness

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.

Affected Software

Name Vendor Start Version End Version
Request_tracker Bestpractical 4.2.0 (including) 4.2.17 (excluding)
Request_tracker Bestpractical 4.4.0 (including) 4.4.5 (excluding)
Request_tracker Bestpractical 5.0.0 (including) 5.0.2 (excluding)
Request-tracker4 Ubuntu bionic *
Request-tracker4 Ubuntu devel *
Request-tracker4 Ubuntu esm-apps/bionic *
Request-tracker4 Ubuntu esm-apps/xenial *
Request-tracker4 Ubuntu focal *
Request-tracker4 Ubuntu hirsute *
Request-tracker4 Ubuntu impish *
Request-tracker4 Ubuntu jammy *
Request-tracker4 Ubuntu kinetic *
Request-tracker4 Ubuntu lunar *
Request-tracker4 Ubuntu mantic *
Request-tracker4 Ubuntu noble *
Request-tracker4 Ubuntu oracular *
Request-tracker4 Ubuntu trusty *
Request-tracker4 Ubuntu xenial *
Request-tracker5 Ubuntu impish *
Request-tracker5 Ubuntu kinetic *
Request-tracker5 Ubuntu lunar *
Request-tracker5 Ubuntu mantic *
Request-tracker5 Ubuntu trusty *
Request-tracker5 Ubuntu upstream *
Request-tracker5 Ubuntu xenial *

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
  • Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
  • If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
  • Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.

References