{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:github-oauth. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-1003018 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:github-oauth to 0.31 or later.","what":"CVE-2019-1003018 is a medium-severity vulnerability in Jenkins GitHub Authentication Plugin, published on 6 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-1003018 and fix it if it is affected.\n\nWhat it is: CVE-2019-1003018 is a medium-severity vulnerability in Jenkins GitHub Authentication Plugin, published on 6 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-1003018 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:github-oauth (Maven): affected all versions; fixed in 0.31\n- org.jenkins-ci.plugins:github-oauth (Maven): affected all versions; fixed in 0.31\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-1003018/ (Markdown: https://insights.sbomify.com/CVE-2019-1003018/index.md)","id":"CVE-2019-1003018","markdown":"https://insights.sbomify.com/CVE-2019-1003018/index.md","name":"CVE-2019-1003018","record":{"aliases":["GHSA-87pj-9q82-m9qh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins GitHub Auth Plugin","requires_auth":"none","summary":"Attackers with browser access can retrieve the configured client secret from the Jenkins GitHub Authentication Plugin configuration page.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"github_oauth","vendor":"jenkins"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An exposure of sensitive information vulnerability exists in Jenkins GitHub Authentication Plugin 0.29 and earlier in GithubSecurityRealm/config.jelly that allows attackers able to view a Jenkins administrator's web browser output, or control the browser (e.g. malicious extension) to retrieve the configured client secret.","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":"GitHub Authentication Plugin showed plain text client secret in configuration form","id":"CVE-2019-1003018","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"GitHub Authentication Plugin session fixation vulnerability","id":"CVE-2019-1003019"},"packages":[{"ecosystem":"Maven","fixed":["0.31"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:github-oauth","purl":null,"source":"GHSA-87pj-9q82-m9qh"},{"ecosystem":"Maven","fixed":["0.31"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:github-oauth","purl":"pkg:maven/org.jenkins-ci.plugins/github-oauth","source":"GHSA-87pj-9q82-m9qh"}],"prev":{"headline":"Jenkins Job Import Plugin CSRF vulnerability","id":"CVE-2019-1003017"},"products":["Jenkins GitHub Authentication Plugin"],"published":"2019-02-06","related":[{"cvss_score":5.9,"headline":"GitHub Authentication Plugin session fixation vulnerability","id":"CVE-2019-1003019","kev_date_added":null,"published":"2019-02-06"}],"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-09-16","vendors":["Jenkins project"]},"summary":"Attackers with browser access can retrieve the configured client secret from the Jenkins GitHub Authentication Plugin configuration page.","url":"https://insights.sbomify.com/CVE-2019-1003018/"}