{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:azure-publishersettings-credentials. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10303 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:azure-publishersettings-credentials to 1.5 or later.","what":"CVE-2019-10303 is a high-severity vulnerability in Jenkins Azure PublisherSettings Credentials Plugin, published on 18 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-10303 and fix it if it is affected.\n\nWhat it is: CVE-2019-10303 is a high-severity vulnerability in Jenkins Azure PublisherSettings Credentials Plugin, published on 18 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-10303 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:azure-publishersettings-credentials (Maven): affected all versions; fixed in 1.5\n- org.jenkins-ci.plugins:azure-publishersettings-credentials (Maven): affected all versions; fixed in 1.5\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-10303/ (Markdown: https://insights.sbomify.com/CVE-2019-10303/index.md)","id":"CVE-2019-10303","markdown":"https://insights.sbomify.com/CVE-2019-10303/index.md","name":"CVE-2019-10303","record":{"aliases":["GHSA-rfc8-wrrf-wp3w"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Azure plugin","requires_auth":"low_privilege","summary":"Attackers with master file system access can read unencrypted Azure credentials stored by the Jenkins Azure PublisherSettings Credentials Plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"azure_publishersettings_credentials","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-522","name":"Insufficiently Protected Credentials"}],"description":"Jenkins Azure PublisherSettings Credentials Plugin 1.2 and earlier stored credentials unencrypted in the credentials.xml file on the Jenkins master where they could 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":true,"headline":"Jenkins Azure PublisherSettings Credentials Plugin stored credentials in plain text","id":"CVE-2019-10303","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 XebiaLabs XL Deploy Plugin vulnerable to Cross-site request forgery (CSRF)","id":"CVE-2019-10304"},"packages":[{"ecosystem":"Maven","fixed":["1.5"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:azure-publishersettings-credentials","purl":null,"source":"GHSA-rfc8-wrrf-wp3w"},{"ecosystem":"Maven","fixed":["1.5"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:azure-publishersettings-credentials","purl":"pkg:maven/org.jenkins-ci.plugins/azure-publishersettings-credentials","source":"GHSA-rfc8-wrrf-wp3w"}],"prev":{"headline":"Jenkins jira-ext Plugin stores credentials unencrypted","id":"CVE-2019-10302"},"products":["Jenkins Azure PublisherSettings Credentials Plugin"],"published":"2019-04-18","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-04","vendors":["Jenkins project"]},"summary":"Attackers with master file system access can read unencrypted Azure credentials stored by the Jenkins Azure PublisherSettings Credentials Plugin.","url":"https://insights.sbomify.com/CVE-2019-10303/"}