Skip to main content
cve.nowby Sazabi
← Vulnerabilities
GHSA-7XW9-549R-8JRC

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

Exploited
No known exploitation
Fix
Fixed in 8.0.79, 9.0.22, 9.1.10
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 8.0.79, 9.0.22, 9.1.10.

Published
Last modified
Reference
Last checked
17/100 · provisional
High (ghsa)
None on Exploit-DB, Metasploit or GitHub

Summary

DIRAC's PilotManager service has SQL injection and missing access control, so any authenticated user can read, change, or delete other users' pilot jobs. The flaw is reached by sending crafted parameters to the service's functions, which requires a valid login because the service only checks that the caller is authenticated.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

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/

cve.now Index

17Pcve.now Index 17 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach10/20Affects PyPI packages
  • Severity7/10Rated high by ghsa
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 39 if advisories confirm default setups are exposed

How the score works · Rankings

Impact

  • Widely used

    dirac has 63.4k weekly downloads.Source: pypistats.org

    12 packages depend on dirac.Source: deps.dev

What to do

  • Upgrade to a fixed version: 8.0.79, 9.0.22, 9.1.10.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by GHSA-7XW9-549R-8JRC (DIRAC: SQL injection and lack of access control in PilotManager service), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for GHSA-7XW9-549R-8JRC (entry last updated 2026-11-10):
Affected:
- PyPI package dirac: from 6, fixed in 8.0.79
- PyPI package dirac: from 8.1.0a1, fixed in 9.0.22
- PyPI package dirac: from 9.1.0, fixed in 9.1.10
Fixed versions: 8.0.79, 9.0.22, 9.1.10.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: GHSA-7XW9-549R-8JRC is not listed as of cve.now's last read.
This KEV status is for GHSA-7XW9-549R-8JRC only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/DIRACGrid/DIRAC/security/advisories/GHSA-7xw9-549r-8jrc
- https://github.com/DIRACGrid/DIRAC/commit/8731de576cf96826dbbf505508526ada31efb927
- https://github.com/DIRACGrid/DIRAC/commit/f67f754d4eef5bf40a8223dab77cf2591808031f
- https://github.com/DIRACGrid/DIRAC
- https://pypi.org/project/DIRAC/8.0.79
- https://pypi.org/project/DIRAC/9.0.22
- https://pypi.org/project/DIRAC/9.1.10
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/GHSA-7XW9-549R-8JRC
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id GHSA-7XW9-549R-8JRC.

Timeline

  1. Advisory published120 days
  2. Record last updated

Affected versions

  • diracPyPI

    From 6 · fixed in 8.0.79

    Fixed in 8.0.79 (released Jun 1, 2026, 42 days before disclosure).

  • diracPyPI

    From 8.1.0a1 · fixed in 9.0.22

    Fixed in 9.0.22 (released Jun 4, 2026, 39 days before disclosure).

  • diracPyPI

    From 9.1.0 · fixed in 9.1.10

    Fixed in 9.1.10 (released Jun 4, 2026, 39 days before disclosure).

    The latest release, 9.1.24, is not affected.

Evidence 7

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

Other links · 6

  1. Repository
  2. Repository
  3. Repository
  4. Link
  5. Link
  6. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about GHSA-7XW9-549R-8JRC

Is GHSA-7XW9-549R-8JRC being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by GHSA-7XW9-549R-8JRC?

dirac (PyPI): from 6 before 8.0.79. dirac (PyPI): from 8.1.0a1 before 9.0.22. dirac (PyPI): from 9.1.0 before 9.1.10.Source: cve.now feed data

How do I fix GHSA-7XW9-549R-8JRC?

Upgrade to a fixed version: 8.0.79, 9.0.22, 9.1.10.Source: cve.now feed data

Sources

Related

More vulnerabilities