{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.main:maven-plugin. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10358 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.main:maven-plugin to 3.4 or later.","what":"CVE-2019-10358 is a medium-severity vulnerability in Jenkins Maven Integration Plugin, published on 31 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10358 and fix it if it is affected.\n\nWhat it is: CVE-2019-10358 is a medium-severity vulnerability in Jenkins Maven Integration Plugin, published on 31 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10358 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.main:maven-plugin (Maven): affected all versions; fixed in 3.4\n- org.jenkins-ci.main:maven-plugin (Maven): affected all versions; fixed in 3.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-2019-10358/ (Markdown: https://insights.sbomify.com/CVE-2019-10358/index.md)","id":"CVE-2019-10358","markdown":"https://insights.sbomify.com/CVE-2019-10358/index.md","name":"CVE-2019-10358","record":{"aliases":["GHSA-hr96-qfvm-52r6"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Maven plugin","requires_auth":"low_privilege","summary":"Attackers can view sensitive build variables in logs because the Jenkins Maven Integration Plugin fails to apply log decorators to module builds.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"maven","vendor":"jenkins"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Jenkins Maven Integration Plugin 3.3 and earlier did not apply build log decorators to module builds, potentially revealing sensitive build variables in the build log.","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":"Maven Integration Plugin did not mask sensitive values in module build logs","id":"CVE-2019-10358","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins Maven Release Plugin contains Cross-Site Request Forgery vulnerability","id":"CVE-2019-10359"},"packages":[{"ecosystem":"Maven","fixed":["3.4"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.main:maven-plugin","purl":null,"source":"GHSA-hr96-qfvm-52r6"},{"ecosystem":"Maven","fixed":["3.4"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.main:maven-plugin","purl":"pkg:maven/org.jenkins-ci.main/maven-plugin","source":"GHSA-hr96-qfvm-52r6"}],"prev":{"headline":"Missing Authorization in Jenkins Pipeline: Shared Groovy Libraries Plugin","id":"CVE-2019-10357"},"products":["Jenkins Maven Integration Plugin"],"published":"2019-07-31","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery (CSRF) vulnerability in Jenkins Maven Release Plugin","id":"CVE-2019-16550","kev_date_added":null,"published":"2019-12-17"},{"cvss_score":8.1,"headline":"Jenkins Maven Release Plug-in Plugin XXE vulnerability","id":"CVE-2019-16549","kev_date_added":null,"published":"2019-12-17"},{"cvss_score":5.9,"headline":"MitM on Jenkins Maven Plugin","id":"CVE-2017-1000397","kev_date_added":null,"published":"2018-01-26"}],"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-04","vendors":["Jenkins project"]},"summary":"Attackers can view sensitive build variables in logs because the Jenkins Maven Integration Plugin fails to apply log decorators to module builds.","url":"https://insights.sbomify.com/CVE-2019-10358/"}