{"answers":{"affected":"2 open source packages ship an affected version, including org.jvnet.hudson.plugins:favorite. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000243 in the wild and no public exploit code.","fix":"Upgrade org.jvnet.hudson.plugins:favorite to 2.3.0 or later.","what":"CVE-2017-1000243 is a medium-severity missing authorization vulnerability in n/a, published on 1 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1000243 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000243 is a medium-severity missing authorization vulnerability in n/a, published on 1 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-1000243 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jvnet.hudson.plugins:favorite (Maven): affected all versions; fixed in 2.3.0\n- org.jvnet.hudson.plugins:favorite (Maven): affected all versions; fixed in 2.3.0\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-2017-1000243/ (Markdown: https://insights.sbomify.com/CVE-2017-1000243/index.md)","id":"CVE-2017-1000243","markdown":"https://insights.sbomify.com/CVE-2017-1000243/index.md","name":"CVE-2017-1000243","record":{"aliases":["GHSA-268v-2qq7-84pf"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Favorite Plugin","requires_auth":"low_privilege","summary":"Attackers can modify other users' favorite settings due to missing permission checks in the Jenkins Favorite Plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"favorite_plugin","vendor":"jenkins"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Jenkins Favorite Plugin 2.1.4 and older does not perform permission checks when changing favorite status, allowing any user to set any other user's favorites","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":"Missing permission check in Jenkins Favorite Plugin","id":"CVE-2017-1000243","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2017"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins Favorite Plugin vulnerable to Cross-Site Request Forgery","id":"CVE-2017-1000244"},"packages":[{"ecosystem":"Maven","fixed":["2.3.0"],"introduced":["0"],"last_affected":[],"package":"org.jvnet.hudson.plugins:favorite","purl":null,"source":"GHSA-268v-2qq7-84pf"},{"ecosystem":"Maven","fixed":["2.3.0"],"introduced":["0"],"last_affected":[],"package":"org.jvnet.hudson.plugins:favorite","purl":"pkg:maven/org.jvnet.hudson.plugins/favorite","source":"GHSA-268v-2qq7-84pf"}],"prev":{"headline":"Insecure temporary file usage in Jenkins Git Client Plugin","id":"CVE-2017-1000242"},"products":["n/a"],"published":"2017-11-01","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-05","vendors":["n/a"]},"summary":"Attackers can modify other users' favorite settings due to missing permission checks in the Jenkins Favorite Plugin.","url":"https://insights.sbomify.com/CVE-2017-1000243/"}