{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:jira. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000412 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:jira to 3.0.2 or later.","what":"CVE-2018-1000412 is a high-severity missing authorization vulnerability in n/a, published on 9 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1000412 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000412 is a high-severity missing authorization vulnerability in n/a, published on 9 Jan 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-2018-1000412 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:jira (Maven): affected all versions; fixed in 3.0.2\n- org.jenkins-ci.plugins:jira (Maven): affected all versions; fixed in 3.0.2\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-2018-1000412/ (Markdown: https://insights.sbomify.com/CVE-2018-1000412/index.md)","id":"CVE-2018-1000412","markdown":"https://insights.sbomify.com/CVE-2018-1000412/index.md","name":"CVE-2018-1000412","record":{"aliases":["GHSA-fpg6-xqj4-j7wf"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Jira Plugin","requires_auth":"low_privilege","summary":"Attackers with read access can force Jenkins to connect to malicious URLs, capturing stored credentials due to improper authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jira","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-863","name":"Incorrect Authorization"}],"description":"An improper authorization vulnerability exists in Jenkins Jira Plugin 3.0.1 and earlier in JiraSite.java that allows attackers with Overall/Read access to have Jenkins connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.","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 Jira Plugin Incorrect Authorization vulnerability","id":"CVE-2018-1000412","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"Stored XSS vulnerability in Config File Provider Plugin","id":"CVE-2018-1000413"},"packages":[{"ecosystem":"Maven","fixed":["3.0.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:jira","purl":null,"source":"GHSA-fpg6-xqj4-j7wf"},{"ecosystem":"Maven","fixed":["3.0.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:jira","purl":"pkg:maven/org.jenkins-ci.plugins/jira","source":"GHSA-fpg6-xqj4-j7wf"}],"prev":{"headline":"Jenkins JUnit Plugin CSRF vulnerability","id":"CVE-2018-1000411"},"products":["n/a"],"published":"2019-01-09","related":[{"cvss_score":9.9,"headline":"Jenkins JIRA Plugin allows users to select and use credentials with System scope","id":"CVE-2019-16541","kev_date_added":null,"published":"2019-11-21"},{"cvss_score":6.5,"headline":"Jenkins Jira Plugin vulnerable to exposure of system-scoped credentials","id":"CVE-2023-49653","kev_date_added":null,"published":"2023-11-29"},{"cvss_score":5.4,"headline":"Stored Cross-site Scripting vulnerability in Jenkins Jira Plugin","id":"CVE-2022-29041","kev_date_added":null,"published":"2022-04-12"}],"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":["n/a"]},"summary":"Attackers with read access can force Jenkins to connect to malicious URLs, capturing stored credentials due to improper authorization checks.","url":"https://insights.sbomify.com/CVE-2018-1000412/"}