{"answers":{"affected":"2 open source packages ship an affected version, including org.jvnet.hudson.plugins:perforce. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000147 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1000147 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1000147 is a medium-severity vulnerability in n/a, published on 5 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1000147 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000147 is a medium-severity vulnerability in n/a, published on 5 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1000147 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jvnet.hudson.plugins:perforce (Maven): affected all versions up to 1.3.36; no fix listed\n- org.jvnet.hudson.plugins:perforce (Maven): affected all versions up to 1.3.36; no fix listed\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-1000147/ (Markdown: https://insights.sbomify.com/CVE-2018-1000147/index.md)","id":"CVE-2018-1000147","markdown":"https://insights.sbomify.com/CVE-2018-1000147/index.md","name":"CVE-2018-1000147","record":{"aliases":["GHSA-jrhw-r343-pjwj"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Perforce Plugin","requires_auth":"low_privilege","summary":"Attackers with insufficient permissions can obtain Perforce passwords configured in jobs due to sensitive information exposure in the Jenkins Perforce Plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"perforce","vendor":"perforce"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An exposure of sensitive information vulnerability exists in Jenkins Perforce Plugin version 1.3.36 and older in PerforcePasswordEncryptor.java that allows attackers with insufficient permission to obtain Perforce passwords configured in jobs to obtain them","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":false,"headline":"Jenkins Perforce Plugin exposure of sensitive information vulnerability exists","id":"CVE-2018-1000147","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Jenkins Copy To Slave Plugin allows access to arbitrary files on the Jenkins controller file system","id":"CVE-2018-1000148"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.3.36"],"package":"org.jvnet.hudson.plugins:perforce","purl":null,"source":"GHSA-jrhw-r343-pjwj"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.3.36"],"package":"org.jvnet.hudson.plugins:perforce","purl":"pkg:maven/org.jvnet.hudson.plugins/perforce","source":"GHSA-jrhw-r343-pjwj"}],"prev":{"headline":"Liquibase Runner Plugin allows users to load arbitrary Java code into controller JVM","id":"CVE-2018-1000146"},"products":["n/a"],"published":"2018-04-05","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-09-16","vendors":["n/a"]},"summary":"Attackers with insufficient permissions can obtain Perforce passwords configured in jobs due to sensitive information exposure in the Jenkins Perforce Plugin.","url":"https://insights.sbomify.com/CVE-2018-1000147/"}