{"answers":{"affected":"2 open source packages ship an affected version, including org.sonarsource.sonarqube:sonar-web. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-38460 in the wild and no public exploit code.","fix":"Upgrade org.sonarsource.sonarqube:sonar-web to 9.9.4 or later.","what":"CVE-2024-38460 is a medium-severity vulnerability in n/a, published on 16 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-38460 and fix it if it is affected.\n\nWhat it is: CVE-2024-38460 is a medium-severity vulnerability in n/a, published on 16 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-38460 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.sonarsource.sonarqube:sonar-web (Maven): affected all versions; fixed in 9.9.4\n- org.sonarsource.sonarqube:sonar-web (Maven): affected all versions; fixed in 9.9.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-38460/ (Markdown: https://insights.sbomify.com/CVE-2024-38460/index.md)","id":"CVE-2024-38460","markdown":"https://insights.sbomify.com/CVE-2024-38460/index.md","name":"CVE-2024-38460","record":{"aliases":["GHSA-hw2c-8xgw-mf57"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SonarQube code quality","requires_auth":"high_privilege","summary":"Attackers can read encrypted settings in cleartext from logs, exposing sensitive configuration data in SonarQube.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sonarqube","vendor":"sonarsource"}],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AC:L/AV:N/A:N/C:H/I:N/PR:H/S:U/UI:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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).","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"SonarQube logs sensitive information","id":"CVE-2024-38460","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2024-38461"},"packages":[{"ecosystem":"Maven","fixed":["9.9.4"],"introduced":["0"],"last_affected":[],"package":"org.sonarsource.sonarqube:sonar-web","purl":null,"source":"GHSA-hw2c-8xgw-mf57"},{"ecosystem":"Maven","fixed":["9.9.4"],"introduced":["0"],"last_affected":[],"package":"org.sonarsource.sonarqube:sonar-web","purl":"pkg:maven/org.sonarsource.sonarqube/sonar-web","source":"GHSA-hw2c-8xgw-mf57"}],"prev":{"headline":"langchain_experimental Code Execution via Python REPL access","id":"CVE-2024-38459"},"products":["n/a"],"published":"2024-06-16","related":[{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-27986","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":6.7,"headline":"SQL injection in n/a","id":"CVE-2024-47911","kev_date_added":null,"published":"2024-10-04"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-17579","kev_date_added":null,"published":"2019-10-14"},{"cvss_score":5.3,"headline":"Auth bypass in n/a","id":"CVE-2020-28002","kev_date_added":null,"published":"2020-10-30"},{"cvss_score":4.3,"headline":"Exposure of Sensitive Information to an Unauthorized Actor in SonarSource SonarQube API","id":"CVE-2018-19413","kev_date_added":null,"published":"2018-12-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-13","vendors":["n/a"]},"summary":"Attackers can read encrypted settings in cleartext from logs, exposing sensitive configuration data in SonarQube.","url":"https://insights.sbomify.com/CVE-2024-38460/"}