{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2016-1551 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2016-1551 is a low-severity vulnerability in Ntp Ntp, published on 27 Jan 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-1551 and fix it if it is affected.\n\nWhat it is: CVE-2016-1551 is a low-severity vulnerability in Ntp Ntp, published on 27 Jan 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-1551 in the wild and no public exploit code.\n\nAffected product: Ntp Ntp. 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-1551/ (Markdown: https://insights.sbomify.com/CVE-2016-1551/index.md)","id":"CVE-2016-1551","markdown":"https://insights.sbomify.com/CVE-2016-1551/index.md","name":"CVE-2016-1551","record":{"aliases":["GHSA-xhrh-m85j-g7hf"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"NTP time server","requires_auth":"none","summary":"Attackers can spoof reference clock packets to manipulate system time if OS-level martian packet filtering is disabled.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"ntp","vendor":"ntp"},{"product":"ntpsec","vendor":"ntpsec"}],"cvss":{"score":3.7,"severity":"low","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-254","name":null}],"description":"ntpd in NTP 4.2.8p3 and NTPsec a5fb34b9cc89b92a8fef2f459004865c93bb7f92 relies on the underlying operating system to protect it from requests that impersonate reference clocks. Because reference clocks are treated like other peers and stored in the same structure, any packet with a source ip address of a reference clock (127.127.1.1 for example) that reaches the receive() function will match that reference clock's peer record and will be treated as a trusted peer. Any system that lacks the typical martian packet filtering which would block these packets is in danger of having its time controlled by an attacker.","ecosystems":[],"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":"Security feature bypass in NTP","id":"CVE-2016-1551","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ntp:ntp","products":["ntp:ntp"],"type":"security_feature_bypass","year":"2016"},"n_packages":0,"n_references":7,"next":{"headline":"NETGEAR Multiple WAP Devices Command Injection","id":"CVE-2016-1555"},"packages":[],"prev":{"headline":"Information disclosure in NTP","id":"CVE-2016-1550"},"products":["NTP","NTPSec"],"published":"2017-01-27","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-12327","kev_date_added":null,"published":"2018-06-20"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-6460","kev_date_added":null,"published":"2017-03-27"},{"cvss_score":8.1,"headline":"Other in n/a","id":"CVE-2019-11331","kev_date_added":null,"published":"2019-04-18"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-6451","kev_date_added":null,"published":"2017-03-27"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-6452","kev_date_added":null,"published":"2017-03-27"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-6462","kev_date_added":null,"published":"2017-03-27"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2015-7978","kev_date_added":null,"published":"2017-01-30"}],"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-05","vendors":["NTP Project","NTPsec Project"]},"summary":"Attackers can spoof reference clock packets to manipulate system time if OS-level martian packet filtering is disabled.","url":"https://insights.sbomify.com/CVE-2016-1551/"}