CVE-2024-24825CWE-200

TokenManager not checking permissions on cached tokens in DIRAC

Critical · published February 8, 2024

CVSS v3.1
9.1
EPSS
1%
Percentile
44.3
In the wild
Unconfirmed
What it is

🚨 An unauthorized user can snag a resource token from another user! With DIRAC's flaws, it's like someone sneaking in and grabbing your suitcase at the baggage claim—absolutely catastrophic! 🔥 Think of DIRAC as a busy hotel check-in where guests can mistakenly hand over their room key to the wrong person. When a resource token falls into the wrong hands, it grants access like a stranger waltzing into someone else's room and rifling through their belongings! An attacker could easily access sensitive resources belonging to other users, potentially leading to data leaks or unauthorized actions within the system. With the stakes this high, it’s like leaving your front door wide open for intruders—serious trouble is just around the corner!

Put simply

Think of DIRAC as a busy hotel check-in where guests can mistakenly hand over their room key to the wrong person. When a resource token falls into the wrong hands, it grants access like a stranger waltzing into someone else's room and rifling through their belongings! This vulnerability allows any user to obtain a token that has been previously requested by another user, compromising the integrity and confidentiality of the resource access. Essentially, DIRAC isn't validating token ownership properly, leading to unauthorized access.

What to do

An attacker could easily access sensitive resources belonging to other users, potentially leading to data leaks or unauthorized actions within the system. With the stakes this high, it’s like leaving your front door wide open for intruders—serious trouble is just around the corner! Upgrade DIRAC to version 8.0.37 immediately to patch the vulnerability. Since there are no workarounds, this step is crucial for maintaining the security of your resources. Don't delay—ensure all users are on the newer version! You can tackle this! Follow the steps to upgrade and you'll be back in the safe zone in no time. 🛡️

The record
Technical detail
CVSS v3.1
9.1 · CRITICAL
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS v4.0
Not supplied
EPSS
0.00534 · 44.3th percentile
Weakness
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
Published
2024-02-08T23:39Z
EPSS history
Timeline
  • 08 FEB 23:39Z
    TokenManager not checking permissions on cached tokens in DIRAC
    cvelistv5