{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-9686 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-9686 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-9686 is a medium-severity denial of service vulnerability in Puppet Puppet Enterprise, published on 8 Feb 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-2016-9686 and fix it if it is affected.\n\nWhat it is: CVE-2016-9686 is a medium-severity denial of service vulnerability in Puppet Puppet Enterprise, published on 8 Feb 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-2016-9686 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-2016-9686/ (Markdown: https://insights.sbomify.com/CVE-2016-9686/index.md)","id":"CVE-2016-9686","markdown":"https://insights.sbomify.com/CVE-2016-9686/index.md","name":"CVE-2016-9686","record":{"aliases":["GHSA-9pfr-f5q4-v4v8"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Puppet Enterprise","requires_auth":"none","summary":"An attacker can crash the Puppet Communications Protocol Broker by sending malformed message headers, preventing command execution on agents.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"puppet","cpe":[{"product":"puppet_enterprise","vendor":"puppet"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The Puppet Communications Protocol (PCP) Broker incorrectly validates message header sizes. An attacker could use this to crash the PCP Broker, preventing commands from being sent to agents. This is resolved in Puppet Enterprise 2016.4.3 and 2016.5.2.","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":"Denial of service in Puppet Enterprise","id":"CVE-2016-9686","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"puppet:puppet_enterprise","products":["puppet:puppet_enterprise"],"type":"denial_of_service","year":"2016"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2016-9687"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2016-9685"},"products":["Puppet Enterprise"],"published":"2017-02-08","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-08-06","vendors":["Puppet"]},"summary":"An attacker can crash the Puppet Communications Protocol Broker by sending malformed message headers, preventing command execution on agents.","url":"https://insights.sbomify.com/CVE-2016-9686/"}