{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:sonar. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000425 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:sonar to 2.8.1 or later.","what":"CVE-2018-1000425 is a high-severity vulnerability in n/a, published on 9 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1000425 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000425 is a high-severity vulnerability in n/a, published on 9 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1000425 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:sonar (Maven): affected all versions; fixed in 2.8.1\n- org.jenkins-ci.plugins:sonar (Maven): affected all versions; fixed in 2.8.1\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-2018-1000425/ (Markdown: https://insights.sbomify.com/CVE-2018-1000425/index.md)","id":"CVE-2018-1000425","markdown":"https://insights.sbomify.com/CVE-2018-1000425/index.md","name":"CVE-2018-1000425","record":{"aliases":["GHSA-3ccq-gccx-pm7j"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Jenkins SonarQube plugin","requires_auth":"low_privilege","summary":"Attackers with local file system access can obtain SonarQube credentials stored by the Jenkins plugin, leading to credential exposure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sonarqube_scanner","vendor":"sonarsource"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"An insufficiently protected credentials vulnerability exists in Jenkins SonarQube Scanner Plugin 2.8 and earlier in SonarInstallation.java that allows attackers with local file system access to obtain the credentials used to connect to SonarQube.","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":"Jenkins SonarQube Scanner Plugin stored server authentication token in plain text","id":"CVE-2018-1000425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"Stored XSS vulnerability in Jenkins Git Changelog Plugin","id":"CVE-2018-1000426"},"packages":[{"ecosystem":"Maven","fixed":["2.8.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:sonar","purl":null,"source":"GHSA-3ccq-gccx-pm7j"},{"ecosystem":"Maven","fixed":["2.8.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:sonar","purl":"pkg:maven/org.jenkins-ci.plugins/sonar","source":"GHSA-3ccq-gccx-pm7j"}],"prev":{"headline":"Jenkins Artifactory Plugin stored old directly entered credentials unencrypted on disk","id":"CVE-2018-1000424"},"products":["n/a"],"published":"2019-01-09","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers with local file system access can obtain SonarQube credentials stored by the Jenkins plugin, leading to credential exposure.","url":"https://insights.sbomify.com/CVE-2018-1000425/"}