{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2297 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2297 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2297 is a high-severity authentication bypass vulnerability in Puppet Puppet Enterprise, published on 1 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-2297 and fix it if it is affected.\n\nWhat it is: CVE-2017-2297 is a high-severity authentication bypass vulnerability in Puppet Puppet Enterprise, published on 1 Feb 2018. 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-2297 in the wild and no public exploit code.\n\nAffected product: Puppet Puppet Enterprise. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2297/ (Markdown: https://insights.sbomify.com/CVE-2017-2297/index.md)","id":"CVE-2017-2297","markdown":"https://insights.sbomify.com/CVE-2017-2297/index.md","name":"CVE-2017-2297","record":{"aliases":["GHSA-86rf-m4cq-ghm6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Puppet Enterprise","requires_auth":"low_privilege","summary":"Attackers can bypass authentication to obtain labeled RBAC access tokens in Puppet Enterprise when labeled tokens are enabled.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"puppet","cpe":[{"product":"puppet_enterprise","vendor":"puppet"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Puppet Enterprise versions prior to 2016.4.5 and 2017.2.1 did not correctly authenticate users before returning labeled RBAC access tokens. This issue has been fixed in Puppet Enterprise 2016.4.5 and 2017.2.1. This only affects users with labeled tokens, which is not the default for tokens.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in Puppet Enterprise","id":"CVE-2017-2297","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"puppet:puppet_enterprise","products":["puppet:puppet_enterprise"],"type":"auth_bypass","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in mcollective","id":"CVE-2017-2298"},"packages":[],"prev":{"headline":"Denial of service in Puppet Enterprise","id":"CVE-2017-2296"},"products":["Puppet Enterprise"],"published":"2018-02-01","related":[{"cvss_score":9.8,"headline":"Privilege escalation in Puppet Enterprise","id":"CVE-2023-2530","kev_date_added":null,"published":"2023-06-07"},{"cvss_score":9.8,"headline":"Hardcoded credentials in Puppet Enterprise","id":"CVE-2019-10694","kev_date_added":null,"published":"2019-12-11"},{"cvss_score":9.8,"headline":"Information disclosure in Puppet Enterprise","id":"CVE-2018-11749","kev_date_added":null,"published":"2018-08-24"},{"cvss_score":8.8,"headline":"Other in Puppet Enterprise","id":"CVE-2021-27020","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2015-5686","kev_date_added":null,"published":"2020-02-27"},{"cvss_score":8.8,"headline":"Code injection in Puppet Enterprise","id":"CVE-2016-5716","kev_date_added":null,"published":"2017-08-09"},{"cvss_score":8.8,"headline":"Security feature bypass in n/a","id":"CVE-2015-7330","kev_date_added":null,"published":"2016-04-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["Puppet"]},"summary":"Attackers can bypass authentication to obtain labeled RBAC access tokens in Puppet Enterprise when labeled tokens are enabled.","url":"https://insights.sbomify.com/CVE-2017-2297/"}