{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:azure-ad. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10318 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:azure-ad to 0.3.4 or later.","what":"CVE-2019-10318 is a high-severity vulnerability in Jenkins Azure AD Plugin, published on 30 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-10318 and fix it if it is affected.\n\nWhat it is: CVE-2019-10318 is a high-severity vulnerability in Jenkins Azure AD Plugin, published on 30 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-10318 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:azure-ad (Maven): affected all versions; fixed in 0.3.4\n- org.jenkins-ci.plugins:azure-ad (Maven): affected all versions; fixed in 0.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-10318/ (Markdown: https://insights.sbomify.com/CVE-2019-10318/index.md)","id":"CVE-2019-10318","markdown":"https://insights.sbomify.com/CVE-2019-10318/index.md","name":"CVE-2019-10318","record":{"aliases":["GHSA-jcwj-j574-8j2c"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Azure AD Plugin","requires_auth":"low_privilege","summary":"Attackers with file system access can read unencrypted Azure AD client secrets from the Jenkins configuration file.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"azure_ad","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 AD Plugin 0.3.3 and earlier stored the client secret unencrypted in the global config.xml configuration file on the Jenkins master where it 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 AD Plugin stored the client secret unencrypted","id":"CVE-2019-10318","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":"Missing authorization in Jenkins PAM Authentication Plugin","id":"CVE-2019-10319"},"packages":[{"ecosystem":"Maven","fixed":["0.3.4"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:azure-ad","purl":null,"source":"GHSA-jcwj-j574-8j2c"},{"ecosystem":"Maven","fixed":["0.3.4"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:azure-ad","purl":"pkg:maven/org.jenkins-ci.plugins/azure-ad","source":"GHSA-jcwj-j574-8j2c"}],"prev":{"headline":"Jenkins SiteMonitor Plugin globally and unconditionally disables SSL/TLS certificate validation","id":"CVE-2019-10317"},"products":["Jenkins Azure AD Plugin"],"published":"2019-04-30","related":[{"cvss_score":8.8,"headline":"Insufficient Session Expiration in Jenkins Azure AD Plugin","id":"CVE-2023-24426","kev_date_added":null,"published":"2023-01-24"},{"cvss_score":8.8,"headline":"Jenkins Azure AD Plugin allows bypassing CSRF protection for any URL","id":"CVE-2021-21679","kev_date_added":null,"published":"2021-08-31"},{"cvss_score":7.5,"headline":"Non-constant time nonce comparison in Jenkins Microsoft Entra ID (previously Azure AD) Plugin","id":"CVE-2023-41935","kev_date_added":null,"published":"2023-09-06"},{"cvss_score":5.3,"headline":"Client secret transmitted in plain text by Azure AD Plugin","id":"CVE-2020-2119","kev_date_added":null,"published":"2020-02-12"},{"cvss_score":4.3,"headline":"Jenkins Microsoft Entra ID (previously Azure AD) Plugin has an open redirect vulnerability","id":"CVE-2026-42525","kev_date_added":null,"published":"2026-04-29"}],"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 file system access can read unencrypted Azure AD client secrets from the Jenkins configuration file.","url":"https://insights.sbomify.com/CVE-2019-10318/"}