GHSA-7XW9-549R-8JRC

GHSA-7XW9-549R-8JRC is a high-severity SQL injection vulnerability in DIRAC (pip), affecting versions >= 6, < 8.0.79. It is fixed in 8.0.79, 9.0.22, 9.1.10.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

DIRAC: SQL injection and lack of access control in PilotManager service

Details

A number of the functions in PilotManager pass parameters directly through to the database layer, which then does not do any escaping on the parameters. For example setPilotStatus:
https://github.com/DIRACGrid/DIRAC/blob/1738e7c6d2f31d26f1364255d9d2e87b4896c922/src/DIRAC/WorkloadManagementSystem/Service/PilotManagerHandler.py#L343-L349

https://github.com/DIRACGrid/DIRAC/blob/1738e7c6d2f31d26f1364255d9d2e87b4896c922/src/DIRAC/WorkloadManagementSystem/DB/PilotAgentsDB.py#L117

This won't accept multiple statements separated by a semicolon, but a carefully crafted set of parameters containing SQL escapes would likely be able to change or return other database entries.

Further to this, the PilotManager access control is only set to "authenticated"; this allows these functions to be called by any user. This allows any user to manage (e.g. delete, read output of) any pilot pilot job:
https://github.com/DIRACGrid/DIRAC/blob/1738e7c6d2f31d26f1364255d9d2e87b4896c922/src/DIRAC/WorkloadManagementSystem/ConfigTemplate.cfg#L111-L118

This is fixed by changing the SQL statements to use proper parameter substitution and providing a suitable set of access rules for the exported pilot management functions.

Patched versions:

https://pypi.org/project/DIRAC/8.0.79/
https://pypi.org/project/DIRAC/9.0.22/
https://pypi.org/project/DIRAC/9.1.10/

Impact

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

GHSA-7XW9-549R-8JRC has a CVSS score of 8.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.0.79, 9.0.22, 9.1.10); upgrading removes the vulnerable code path.

Affected versions

DIRAC (>= 6, < 8.0.79) DIRAC (>= 8.1.0a1, < 9.0.22) DIRAC (>= 9.1.0, < 9.1.10)

Security releases

DIRAC → 8.0.79 (pip) DIRAC → 9.0.22 (pip) DIRAC → 9.1.10 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

DIRAC to 8.0.79 or later; DIRAC to 9.0.22 or later; DIRAC to 9.1.10 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-7XW9-549R-8JRC? GHSA-7XW9-549R-8JRC is a high-severity SQL injection vulnerability in DIRAC (pip), affecting versions >= 6, < 8.0.79. It is fixed in 8.0.79, 9.0.22, 9.1.10. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
  2. How severe is GHSA-7XW9-549R-8JRC? GHSA-7XW9-549R-8JRC has a CVSS score of 8.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of DIRAC are affected by GHSA-7XW9-549R-8JRC? DIRAC (pip) versions >= 6, < 8.0.79 is affected.
  4. Is there a fix for GHSA-7XW9-549R-8JRC? Yes. GHSA-7XW9-549R-8JRC is fixed in 8.0.79, 9.0.22, 9.1.10. Upgrade to this version or later.
  5. Is GHSA-7XW9-549R-8JRC exploitable, and should I be worried? Whether GHSA-7XW9-549R-8JRC is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether GHSA-7XW9-549R-8JRC is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix GHSA-7XW9-549R-8JRC?
    • Upgrade DIRAC to 8.0.79 or later
    • Upgrade DIRAC to 9.0.22 or later
    • Upgrade DIRAC to 9.1.10 or later

Other vulnerabilities in DIRAC

Stop the waste.
Protect your environment with Kodem.