{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:google-oauth-plugin. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10436 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:google-oauth-plugin to 0.10 or later.","what":"CVE-2019-10436 is a medium-severity path traversal vulnerability in Jenkins Google OAuth Credentials Plugin, published on 16 Oct 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-10436 and fix it if it is affected.\n\nWhat it is: CVE-2019-10436 is a medium-severity path traversal vulnerability in Jenkins Google OAuth Credentials Plugin, published on 16 Oct 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-10436 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:google-oauth-plugin (Maven): affected all versions; fixed in 0.10\n- org.jenkins-ci.plugins:google-oauth-plugin (Maven): affected all versions; fixed in 0.10\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-10436/ (Markdown: https://insights.sbomify.com/CVE-2019-10436/index.md)","id":"CVE-2019-10436","markdown":"https://insights.sbomify.com/CVE-2019-10436/index.md","name":"CVE-2019-10436","record":{"aliases":["GHSA-8qh4-fghr-6fxg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins OAuth plugin","requires_auth":"low_privilege","summary":"Attackers with job configuration privileges can read arbitrary files on the Jenkins master via the Google OAuth Credentials Plugin.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"google_oauth_credentials","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":[],"description":"An arbitrary file read vulnerability in Jenkins Google OAuth Credentials Plugin 0.9 and earlier allowed attackers able to configure jobs and credentials in Jenkins to obtain the contents of any file on the Jenkins master.","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":"Improper Limitation of a Pathname to a Restricted Directory in Jenkins Google OAuth Credentials Plugin","id":"CVE-2019-10436","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Jenkins CRX Content Package Deployer Plugin subject to Cross-Site Request Forgery","id":"CVE-2019-10437"},"packages":[{"ecosystem":"Maven","fixed":["0.10"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:google-oauth-plugin","purl":null,"source":"GHSA-8qh4-fghr-6fxg"},{"ecosystem":"Maven","fixed":["0.10"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:google-oauth-plugin","purl":"pkg:maven/org.jenkins-ci.plugins/google-oauth-plugin","source":"GHSA-8qh4-fghr-6fxg"}],"prev":{"headline":"Jenkins SourceGear Vault plugin transmits credentials in plain text","id":"CVE-2019-10435"},"products":["Jenkins Google OAuth Credentials Plugin"],"published":"2019-10-16","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":"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 job configuration privileges can read arbitrary files on the Jenkins master via the Google OAuth Credentials Plugin.","url":"https://insights.sbomify.com/CVE-2019-10436/"}