CVE-2024-38460 is a medium-severity (CVSS 4.9) CWE-532 vulnerability in org.sonarsource.sonarqube:sonar-web. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.sonarsource.sonarqube:sonar-web — see the affected versions and patch details below.
SonarQube logs sensitive information
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-38460.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.sonarsource.sonarqube:sonar-webReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
In SonarQube before 10.4 and 9.9.4 LTA, encrypted values generated using the Settings Encryption feature are potentially exposed in cleartext as part of the URL parameters in the logs (such as SonarQube Access Logs, Proxy Logs, etc).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.sonarsource.sonarqube:sonar-web | all versions | 9.9.4org.sonarsource.sonarqube:sonar-web:9.9.4 |
Affected Products
sonarqubesonarsourceResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.sonarsource.sonarqube:sonar-web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.sonarsource.sonarqube:sonar-web to 9.9.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-38460 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2024-38460 in your dependencies?
Find it across Maven, including transitive dependencies.