{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:veracode-scanner. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-1003070 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-1003070 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-1003070 is a high-severity vulnerability in Jenkins veracode-scanner Plugin, published on 4 Apr 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-1003070 and fix it if it is affected.\n\nWhat it is: CVE-2019-1003070 is a high-severity vulnerability in Jenkins veracode-scanner Plugin, published on 4 Apr 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-1003070 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:veracode-scanner (Maven): affected all versions up to 1.6; no fix listed\n- org.jenkins-ci.plugins:veracode-scanner (Maven): affected all versions up to 1.6; 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-2019-1003070/ (Markdown: https://insights.sbomify.com/CVE-2019-1003070/index.md)","id":"CVE-2019-1003070","markdown":"https://insights.sbomify.com/CVE-2019-1003070/index.md","name":"CVE-2019-1003070","record":{"aliases":["GHSA-5722-v5wc-x7h8"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins veracode-scanner Plugin","requires_auth":"low_privilege","summary":"The Jenkins veracode-scanner Plugin stores credentials unencrypted, allowing users with master file system access to view them.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"veracode-scanner","vendor":"jenkins"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"Jenkins veracode-scanner Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with access to the master file system.","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 veracode-scanner Plugin stores credentials in plain text","id":"CVE-2019-1003070","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":2,"n_references":3,"next":{"headline":"Jenkins Octopus Deploy Plugin stores credentials in plain text","id":"CVE-2019-1003071"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.6"],"package":"org.jenkins-ci.plugins:veracode-scanner","purl":null,"source":"GHSA-5722-v5wc-x7h8"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.6"],"package":"org.jenkins-ci.plugins:veracode-scanner","purl":"pkg:maven/org.jenkins-ci.plugins/veracode-scanner","source":"GHSA-5722-v5wc-x7h8"}],"prev":{"headline":"Jenkins Aqua Security Scanner Plugin stores credentials in plain text","id":"CVE-2019-1003069"},"products":["Jenkins veracode-scanner Plugin"],"published":"2019-04-04","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":["Jenkins project"]},"summary":"The Jenkins veracode-scanner Plugin stores credentials unencrypted, allowing users with master file system access to view them.","url":"https://insights.sbomify.com/CVE-2019-1003070/"}