DIRACGrid DIRAC up to 8.0.40 /tmp/x509up_uNNNN exposure of resource

Summaryinfo

A vulnerability was found in DIRACGrid DIRAC up to 8.0.40. It has been classified as problematic. Affected is an unknown function of the file /tmp/x509up_uNNNN. Performing a manipulation results in exposure of resource. This vulnerability is cataloged as CVE-2024-29905. The attack must be initiated from a local position. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic has been found in DIRACGrid DIRAC up to 8.0.40. This affects an unknown code block of the file /tmp/x509up_uNNNN. The manipulation with an unknown input leads to a exposure of resource vulnerability. CWE is classifying the issue as CWE-668. The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

DIRAC is an interware, meaning a software framework for distributed computing. Prior to version 8.0.41, 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. Version 8.0.41 contains a patch for the issue. As a workaround, 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`).

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-29905 since 03/21/2024. The exploitability is told to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

Upgrading to version 8.0.41 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• DIRACGrid

Name

• DIRAC

Version

• 8.0.0
• 8.0.1
• 8.0.2
• 8.0.3
• 8.0.4
• 8.0.5
• 8.0.6
• 8.0.7
• 8.0.8
• 8.0.9
• 8.0.10
• 8.0.11
• 8.0.12
• 8.0.13
• 8.0.14
• 8.0.15
• 8.0.16
• 8.0.17
• 8.0.18
• 8.0.19
• 8.0.20
• 8.0.21
• 8.0.22
• 8.0.23
• 8.0.24
• 8.0.25
• 8.0.26
• 8.0.27
• 8.0.28
• 8.0.29
• 8.0.30
• 8.0.31
• 8.0.32
• 8.0.33
• 8.0.34
• 8.0.35
• 8.0.36
• 8.0.37
• 8.0.38
• 8.0.39
• 8.0.40

License

• open-source

Website

• Product: https://github.com/DIRACGrid/DIRAC/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion