Skip to content

DIRAC: Unauthorized users can read proxy contents during generation

High severity GitHub Reviewed Published Apr 9, 2024 in DIRACGrid/DIRAC • Updated Apr 9, 2024

Package

pip DIRAC (pip)

Affected versions

< 8.0.41

Patched versions

8.0.41

Description

Impact

During the proxy generation process (e.g., when using dirac-proxy-init) it is possible for unauthorized users on the same machine to gain read access to the proxy. This allows the user to then perform any action that is possible with the original proxy.

This vulnerability only exists for a short period of time (sub-millsecond) during the generation process.

Patches

Has the problem been patched? What versions should users upgrade to?

Workarounds

Setting the X509_USER_PROXY environment variable to a path that is inside a directory that is only readable to the current user avoids the potential risk. After the file has been written it can be safely copied to the standard location (/tmp/x509up_uNNNN).

References

References

@fstagni fstagni published to DIRACGrid/DIRAC Apr 9, 2024
Published to the GitHub Advisory Database Apr 9, 2024
Reviewed Apr 9, 2024
Published by the National Vulnerability Database Apr 9, 2024
Last updated Apr 9, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L

EPSS score

0.043%
(11th percentile)

Weaknesses

CVE ID

CVE-2024-29905

GHSA ID

GHSA-v6f3-gh5h-mqwx

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.