CVE-2024-47911
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn SonarSource SonarQube 10.4 through 10.5 before 10.6, a vulnerability was discovered in the authorizations/group-memberships API endpoint that allows SonarQube users with the administrator role to inject blind SQL commands.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA blind SQL injection vulnerability exists in the authorizations/group-memberships API endpoint of SonarQube versions 10.4 through 10.5. Authenticated users with the administrator role can inject malicious SQL commands through unsanitized input in this API endpoint, allowing them to execute arbitrary SQL queries against the underlying database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 10.4, < 10.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed SonarQube versionCheck the SonarQube About page in the web UI or inspect the wrapper.conf or manifest file in the SonarQube installation directory for the exact version numberAffected if Version is 10.4.x or 10.5.x (any patch release within these minor versions)
-
Confirm API endpoint accessibilityVerify that the SonarQube web interface is running and accessible. The vulnerable endpoint is at /api/authorizations/group-membershipsAffected if The SonarQube server is reachable and this API endpoint responds to requests
-
Verify admin role existsCheck SonarQube user administration panel for accounts with the administrator global permission. The SQL injection requires an authenticated user with admin privilegesAffected if At least one active user account possesses administrator role permissions
-
Check network exposure of APIDetermine if SonarQube is exposed to untrusted networks or the public internet by reviewing network configuration, firewall rules, or reverse proxy settingsAffected if The SonarQube server is accessible from untrusted networks without proper access controls
You are affected if your SonarQube version is between 10.4 and 10.5 inclusive, the API endpoint is reachable, and an authenticated administrator can access it.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.6
Upgrade SonarQube to version 10.6 or later to remediate this vulnerability. As a precautionary measure, restrict admin access to only trusted personnel and monitor API activity for suspicious queries.
SonarQube 10.6 or later
- Review SonarQube 10.6 release notes for any breaking changes or migration requirements
- Perform a full backup of the current SonarQube instance including database and configuration
- Plan maintenance window for the upgrade
- Upgrade SonarQube from version 10.4 or 10.5 to version 10.6 or later
- Verify the upgrade was successful by logging into the UI and checking the version
- Confirm the authorizations/group-memberships API endpoint no longer accepts SQL injection payloads
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47911 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47911 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data