{"answers":{"affected":"5 open source packages ship an affected version, including dirac and DIRAC. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-24825 in the wild and no public exploit code.","fix":"Upgrade dirac to 8.0.37 or later.","what":"CVE-2024-24825 is a critical missing authorization vulnerability in DIRACGrid DIRAC, published on 8 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-24825 and fix it if it is affected.\n\nWhat it is: CVE-2024-24825 is a critical missing authorization vulnerability in DIRACGrid DIRAC, published on 8 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-24825 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- dirac (PyPI): affected all versions; fixed in 8.0.37\n- dirac (PyPI): affected all versions; fixed in 8.0.37\n- dirac (PyPI): affected all versions; fixed in 8.0.37\n- dirac (PyPI): affected from 8.0.0; fixed in 8.0.37\n- DIRAC (PyPI): affected from 8.0.0; fixed in 8.0.37\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-24825/ (Markdown: https://insights.sbomify.com/CVE-2024-24825/index.md)","id":"CVE-2024-24825","markdown":"https://insights.sbomify.com/CVE-2024-24825/index.md","name":"CVE-2024-24825","record":{"aliases":["GHSA-59qj-jcjv-662j","PYSEC-2024-125"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"DIRAC distributed resource framework","requires_auth":"none","summary":"Attackers can access tokens requested by other users, exposing resources to unintended parties in the DIRAC distributed resource framework.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"dirac","vendor":"diracgrid"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"DIRAC is a distributed resource framework. In affected versions any user could get a token that has been requested by another user/agent. This may expose resources to unintended parties. This issue has been addressed in release version 8.0.37. Users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"TokenManager not checking permissions on cached tokens in DIRAC","id":"CVE-2024-24825","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":5,"n_references":2,"next":{"headline":"Out-of-bounds read in QuickTimeVideo::NikonTagsDecoder in Exiv2","id":"CVE-2024-24826"},"packages":[{"ecosystem":"PyPI","fixed":["8.0.37"],"introduced":["8.0.0"],"last_affected":[],"package":"DIRAC","purl":null,"source":"GHSA-59qj-jcjv-662j"},{"ecosystem":"PyPI","fixed":["8.0.37"],"introduced":["0"],"last_affected":[],"package":"dirac","purl":null,"source":"GHSA-59qj-jcjv-662j"},{"ecosystem":"PyPI","fixed":["8.0.37"],"introduced":["0"],"last_affected":[],"package":"dirac","purl":"pkg:pypi/dirac","source":"GHSA-59qj-jcjv-662j"},{"ecosystem":"PyPI","fixed":["8.0.37"],"introduced":["0"],"last_affected":[],"package":"dirac","purl":"pkg:pypi/dirac","source":"PYSEC-2024-125"},{"ecosystem":"PyPI","fixed":["8.0.37"],"introduced":["8.0.0"],"last_affected":[],"package":"dirac","purl":"pkg:pypi/dirac","source":"GHSA-59qj-jcjv-662j"}],"prev":{"headline":"graylog2-server vulnerable to instantiation of arbitrary classes triggered by API request","id":"CVE-2024-24824"},"products":["DIRAC"],"published":"2024-02-08","related":[{"cvss_score":8.1,"headline":"DIRAC: Unauthorized users can read proxy contents during generation","id":"CVE-2024-29905","kev_date_added":null,"published":"2024-04-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["DIRACGrid"]},"summary":"Attackers can access tokens requested by other users, exposing resources to unintended parties in the DIRAC distributed resource framework.","url":"https://insights.sbomify.com/CVE-2024-24825/"}