{"answers":{"affected":"2 open source packages ship an affected version, including io.jenkins:configuration-as-code. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000609 in the wild and no public exploit code.","fix":"Upgrade io.jenkins:configuration-as-code to 0.8-alpha or later.","what":"CVE-2018-1000609 is a medium-severity vulnerability in n/a, published on 26 Jun 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-1000609 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000609 is a medium-severity vulnerability in n/a, published on 26 Jun 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-1000609 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.jenkins:configuration-as-code (Maven): affected all versions; fixed in 0.8-alpha\n- io.jenkins:configuration-as-code (Maven): affected all versions; fixed in 0.8-alpha\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-1000609/ (Markdown: https://insights.sbomify.com/CVE-2018-1000609/index.md)","id":"CVE-2018-1000609","markdown":"https://insights.sbomify.com/CVE-2018-1000609/index.md","name":"CVE-2018-1000609","record":{"aliases":["GHSA-393r-r9mq-g9jv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Attackers with read access can obtain the YAML export of Jenkins configuration, exposing sensitive information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"configuration_as_code","vendor":"jenkins"}],"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":"A exposure of sensitive information vulnerability exists in Jenkins Configuration as Code Plugin 0.7-alpha and earlier in ConfigurationAsCode.java that allows attackers with Overall/Read access to obtain the YAML export of the Jenkins configuration.","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 Configuration as Code Plugin vulnerable to Exposure of Sensitive Information","id":"CVE-2018-1000609","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 Configuration as Code Plugin has Insufficiently Protected Credentials","id":"CVE-2018-1000610"},"packages":[{"ecosystem":"Maven","fixed":["0.8-alpha"],"introduced":["0"],"last_affected":[],"package":"io.jenkins:configuration-as-code","purl":null,"source":"GHSA-393r-r9mq-g9jv"},{"ecosystem":"Maven","fixed":["0.8-alpha"],"introduced":["0"],"last_affected":[],"package":"io.jenkins:configuration-as-code","purl":"pkg:maven/io.jenkins/configuration-as-code","source":"GHSA-393r-r9mq-g9jv"}],"prev":{"headline":"Jenkins z/OS Connector Plugin allows local attacker to retrieve configured password","id":"CVE-2018-1000608"},"products":["n/a"],"published":"2018-06-26","related":[{"cvss_score":8.8,"headline":"Jenkins Configuration as Code Plugin has Insufficiently Protected Credentials","id":"CVE-2018-1000610","kev_date_added":null,"published":"2018-06-26"},{"cvss_score":5.5,"headline":"Insertion of Sensitive Information into Log File in Jenkins Configuration as Code Plugin","id":"CVE-2019-10367","kev_date_added":null,"published":"2019-08-07"},{"cvss_score":5.5,"headline":"Plaintext Storage of a Password in Jenkins Configuration as Code Plugin","id":"CVE-2019-10345","kev_date_added":null,"published":"2019-07-31"},{"cvss_score":5.4,"headline":"Improper Encoding or Escaping of Output in Jenkins Configuration as Code Plugin","id":"CVE-2019-10362","kev_date_added":null,"published":"2019-07-31"},{"cvss_score":5.3,"headline":"Observable Discrepancy and Observable Timing Discrepancy in Jenkins Configuration as Code Plugin","id":"CVE-2022-23106","kev_date_added":null,"published":"2022-01-12"},{"cvss_score":4.9,"headline":"Cleartext Transmission of Sensitive Information in Jenkins Configuration as Code Plugin","id":"CVE-2019-10363","kev_date_added":null,"published":"2019-07-31"}],"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-17","vendors":["n/a"]},"summary":"Attackers with read access can obtain the YAML export of Jenkins configuration, exposing sensitive information.","url":"https://insights.sbomify.com/CVE-2018-1000609/"}