{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2294 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2294 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2294 is a high-severity vulnerability in Puppet Puppet Enterprise, published on 5 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-2294 and fix it if it is affected.\n\nWhat it is: CVE-2017-2294 is a high-severity vulnerability in Puppet Puppet Enterprise, published on 5 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-2294 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-2294/ (Markdown: https://insights.sbomify.com/CVE-2017-2294/index.md)","id":"CVE-2017-2294","markdown":"https://insights.sbomify.com/CVE-2017-2294/index.md","name":"CVE-2017-2294","record":{"aliases":["GHSA-p5c4-h8f6-v559"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Puppet Enterprise","requires_auth":"none","summary":"Attackers with access to logs or PuppetDB can read exposed MCollective server private keys due to missing sensitive data marking.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Versions of Puppet Enterprise prior to 2016.4.5 or 2017.2.1 failed to mark MCollective server private keys as sensitive (a feature added in Puppet 4.6), so key values could be logged and stored in PuppetDB. These releases use the sensitive data type to ensure this won't happen anymore.","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":"Information disclosure in Puppet Enterprise","id":"CVE-2017-2294","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"puppet:puppet_enterprise","products":["puppet:puppet_enterprise"],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Deserialization in Puppet server","id":"CVE-2017-2295"},"packages":[],"prev":{"headline":"Missing authorization in Puppet Enterprise","id":"CVE-2017-2293"},"products":["Puppet Enterprise"],"published":"2017-07-05","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 with access to logs or PuppetDB can read exposed MCollective server private keys due to missing sensitive data marking.","url":"https://insights.sbomify.com/CVE-2017-2294/"}