DIRAC: SQL injection and lack of access control in PilotManager service
The DIRAC PilotManager service contains a SQL injection vulnerability due to unsafe parameter handling in database queries combined with insufficient access control. Functions in the PilotManager pass parameters directly to the database without proper escaping, enabling crafted inputs to manipulate or retrieve unauthorized data. Additionally, the PilotManager access control is set only to "authenticated," allowing any authenticated user to invoke these sensitive functions. This vulnerability allows unauthorized users to read or delete pilot job data. The issue is fixed in DIRAC versions 8.0.79, 9.0.22, and 9.1.10 by implementing proper parameter substitution and stricter access controls.
AI Analysis
Technical Summary
The DIRAC PilotManager service improperly handles input parameters by passing them directly to the database layer without escaping, leading to SQL injection vulnerabilities. Although multiple SQL statements separated by semicolons are not accepted, crafted inputs can still alter or disclose database entries. The access control for PilotManager functions is insufficient, requiring only authentication but no further authorization, allowing any authenticated user to manage pilot jobs. The vulnerability is addressed by changing SQL statements to use parameter substitution and enforcing appropriate access rules. Affected versions include DIRAC >=6 and <8.0.79, and >=9.1.0 and <9.1.10.
Potential Impact
An attacker with authenticated access can exploit SQL injection to read or modify database entries related to pilot jobs. The lack of proper access control means any authenticated user can perform these actions, potentially leading to unauthorized data disclosure and modification. The vulnerability does not allow denial of service or privilege escalation beyond the authenticated user level but compromises data integrity and confidentiality within the PilotManager service.
Mitigation Recommendations
A fix is available in DIRAC versions 8.0.79, 9.0.22, and 9.1.10. Users should upgrade to one of these patched versions to address the SQL injection and access control issues. The patch implements proper parameter substitution in SQL queries and enforces stricter access control rules for PilotManager functions.
DIRAC: SQL injection and lack of access control in PilotManager service
Description
The DIRAC PilotManager service contains a SQL injection vulnerability due to unsafe parameter handling in database queries combined with insufficient access control. Functions in the PilotManager pass parameters directly to the database without proper escaping, enabling crafted inputs to manipulate or retrieve unauthorized data. Additionally, the PilotManager access control is set only to "authenticated," allowing any authenticated user to invoke these sensitive functions. This vulnerability allows unauthorized users to read or delete pilot job data. The issue is fixed in DIRAC versions 8.0.79, 9.0.22, and 9.1.10 by implementing proper parameter substitution and stricter access controls.
CVSS v3.1
Score 8.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The DIRAC PilotManager service improperly handles input parameters by passing them directly to the database layer without escaping, leading to SQL injection vulnerabilities. Although multiple SQL statements separated by semicolons are not accepted, crafted inputs can still alter or disclose database entries. The access control for PilotManager functions is insufficient, requiring only authentication but no further authorization, allowing any authenticated user to manage pilot jobs. The vulnerability is addressed by changing SQL statements to use parameter substitution and enforcing appropriate access rules. Affected versions include DIRAC >=6 and <8.0.79, and >=9.1.0 and <9.1.10.
Potential Impact
An attacker with authenticated access can exploit SQL injection to read or modify database entries related to pilot jobs. The lack of proper access control means any authenticated user can perform these actions, potentially leading to unauthorized data disclosure and modification. The vulnerability does not allow denial of service or privilege escalation beyond the authenticated user level but compromises data integrity and confidentiality within the PilotManager service.
Mitigation Recommendations
A fix is available in DIRAC versions 8.0.79, 9.0.22, and 9.1.10. Users should upgrade to one of these patched versions to address the SQL injection and access control issues. The patch implements proper parameter substitution in SQL queries and enforces stricter access control rules for PilotManager functions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-7xw9-549r-8jrc
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["PyPI"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a55ffa968715ace432fa011
Added to database: 07/14/2026, 09:21:45 UTC
Last enriched: 07/14/2026, 09:55:23 UTC
Last updated: 07/31/2026, 13:21:56 UTC
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.