{"answers":{"affected":"2 open source packages ship an affected version, including io.jenkins.blueocean:blueocean. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000110 in the wild and no public exploit code.","fix":"Upgrade io.jenkins.blueocean:blueocean to 1.2.0 or later.","what":"CVE-2017-1000110 is a medium-severity missing authorization vulnerability in n/a, published on 4 Oct 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-1000110 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000110 is a medium-severity missing authorization vulnerability in n/a, published on 4 Oct 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-1000110 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.jenkins.blueocean:blueocean (Maven): affected all versions; fixed in 1.2.0\n- io.jenkins.blueocean:blueocean (Maven): affected all versions; fixed in 1.2.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-1000110/ (Markdown: https://insights.sbomify.com/CVE-2017-1000110/index.md)","id":"CVE-2017-1000110","markdown":"https://insights.sbomify.com/CVE-2017-1000110/index.md","name":"CVE-2017-1000110","record":{"aliases":["GHSA-rm5m-9mx4-g5r7"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Blue Ocean plugin","requires_auth":"low_privilege","summary":"Attackers with read access can reconfigure GitHub organization folders to steal access tokens due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"blue_ocean","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-287","name":"Improper Authentication"}],"description":"Blue Ocean allows the creation of GitHub organization folders that are set up to scan a GitHub organization for repositories and branches containing a Jenkinsfile, and create corresponding pipelines in Jenkins. It did not properly check the current user's authentication and authorization when configuring existing GitHub organization folders. This allowed users with read access to the GitHub organization folder to reconfigure it, including changing the GitHub API endpoint for the organization folder to an attacker-controlled server to obtain the GitHub access token, if the organization folder was initially created using Blue Ocean.","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 Authentication in Jenkins Blue Ocean Plugin","id":"CVE-2017-1000110","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2017"},"n_packages":2,"n_references":1,"next":{"headline":"Race condition in n/a","id":"CVE-2017-1000111"},"packages":[{"ecosystem":"Maven","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"io.jenkins.blueocean:blueocean","purl":null,"source":"GHSA-rm5m-9mx4-g5r7"},{"ecosystem":"Maven","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"io.jenkins.blueocean:blueocean","purl":"pkg:maven/io.jenkins.blueocean/blueocean","source":"GHSA-rm5m-9mx4-g5r7"}],"prev":{"headline":"Persistent XSS vulnerability in Jenkins OWASP Dependency-Check Plugin","id":"CVE-2017-1000109"},"products":["n/a"],"published":"2017-10-04","related":[{"cvss_score":8.8,"headline":"Jenkins Blue Ocean Plugin cross-site request forgery vulnerability","id":"CVE-2023-40341","kev_date_added":null,"published":"2023-08-16"},{"cvss_score":8.5,"headline":"Improper Authentication in Jenkins Blue Ocean Plugin","id":"CVE-2017-1000106","kev_date_added":null,"published":"2017-10-04"},{"cvss_score":6.5,"headline":"Insufficiently Protected Credentials in Jenkins Pipeline SCM API for Blue Ocean Plugin","id":"CVE-2022-30952","kev_date_added":null,"published":"2022-05-17"},{"cvss_score":6.5,"headline":"Cross Site Request Forgery in Jenkins Blue Ocean Plugin","id":"CVE-2022-30953","kev_date_added":null,"published":"2022-05-17"},{"cvss_score":6.5,"headline":"Missing permission check in Jenkins Blue Ocean Plugin","id":"CVE-2022-30954","kev_date_added":null,"published":"2022-05-17"},{"cvss_score":6.5,"headline":"Path traversal vulnerability in Blue Ocean Plugin","id":"CVE-2020-2254","kev_date_added":null,"published":"2020-09-16"},{"cvss_score":6.5,"headline":"Cross-Site Request Forgery in Jenkins Blue Ocean Plugin","id":"CVE-2019-1003012","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-17","vendors":["n/a"]},"summary":"Attackers with read access can reconfigure GitHub organization folders to steal access tokens due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2017-1000110/"}