dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-47910

HIGH · 7.2 CVSS v3.1 Published 2024-10-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
An issue was discovered in SonarSource SonarQube before 9.9.5 LTA and 10.x before 10.5. A SonarQube user with the Administrator role can modify an existing configuration of a GitHub integration to exfiltrate a pre-signed JWT.

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 confidence

An authenticated Administrator user in SonarQube versions before 9.9.5 LTA and 10.x before 10.5 can modify an existing GitHub integration configuration to exfiltrate a pre-signed JWT token. This allows the attacker to steal the token which could be used for further privilege escalation or unauthorized API access.

MitigationUpgrade SonarQube to version 9.9.5 LTA or 10.5 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check SonarQube version
    Navigate to Administration > System > About in the UI, or query the API endpoint GET /api/system/info to retrieve the installed version number.
    Affected if The installed version is before 9.9.5 for the 9.x branch, or before 10.5 for the 10.x branch.
  2. Verify GitHub integration is configured
    Navigate to Administration > Configuration > GitHub in the UI, or query the API endpoint GET /api/github/list to see if any GitHub integration settings exist.
    Affected if A GitHub integration configuration exists and is enabled in SonarQube.
  3. Confirm Administrator role exists
    Check if any user account holds the Administrator role by navigating to Administration > Security > Users in the SonarQube UI.
    Affected if At least one user account with Administrator privileges exists in the system.
  4. Review audit logs for configuration changes
    Examine SonarQube audit logs (typically found in the administration or logging section) for any recent modifications to GitHub integration settings, specifically looking for changes to token or webhook configuration.
    Affected if Unexpected or unauthorized modifications to GitHub integration settings are found in the audit logs.

A user is affected if their SonarQube version is before 9.9.5 (9.x branch) or before 10.5 (10.x branch) AND GitHub integration is configured with an active user who has Administrator privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SonarQube to version 9.9.5 LTA or 10.5 or later to remediate this vulnerability.

Recommended fix High confidence

SonarQube 9.9.5 LTA (for 9.x branches) or SonarQube 10.5+ (for 10.x branch)

  1. Identify your current SonarQube version by checking the SonarQube administration interface or your deployment configuration
  2. If running SonarQube 9.x, plan to upgrade to version 9.9.5 LTA (Long Term Access) or later
  3. If running SonarQube 10.x, plan to upgrade to version 10.5 or later
  4. Review the SonarQube upgrade guide for your specific migration path: https://docs.sonarqube.org/10.5/setup-and-upgrade/
  5. Perform a backup of your SonarQube database and configuration before upgrading
  6. Execute the upgrade following SonarSource's standard upgrade procedures
  7. After upgrade, verify the GitHub integration settings are intact and review admin permissions
Caveat Standard SonarQube upgrade considerations apply - review release notes for deprecations and migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47910 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47910 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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