{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-10180 exists.","fix":"No fix has been published for CVE-2016-10180 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-10180 is a high-severity vulnerability in n/a, published on 30 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-10180 and fix it if it is affected.\n\nWhat it is: CVE-2016-10180 is a high-severity vulnerability in n/a, published on 30 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-10180 exists.\n\nAffected product: n/a. 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-10180/ (Markdown: https://insights.sbomify.com/CVE-2016-10180/index.md)","id":"CVE-2016-10180","markdown":"https://insights.sbomify.com/CVE-2016-10180/index.md","name":"CVE-2016-10180","record":{"aliases":["GHSA-8vx9-59h6-x23v"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"D-Link router","requires_auth":"none","summary":"Weak WPS PIN generation using time-based seeding allows attackers to bypass authentication on D-Link routers.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dwr-932b_firmware","vendor":"dlink"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-335","name":"Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)"},{"id":"CWE-330","name":"Use of Insufficiently Random Values"},{"id":"CWE-1241","name":"Use of Predictable Algorithm in Random Number Generator"}],"description":"An issue was discovered on the D-Link DWR-932B router. WPS PIN generation is based on srand(time(0)) seeding.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Weak cryptography in n/a","id":"CVE-2016-10180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2016-10181"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2016-10179"},"products":["n/a"],"published":"2017-01-30","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2016-10177","kev_date_added":null,"published":"2017-01-30"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2016-10178","kev_date_added":null,"published":"2017-01-30"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2016-10182","kev_date_added":null,"published":"2017-01-30"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2016-10179","kev_date_added":null,"published":"2017-01-30"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2016-10181","kev_date_added":null,"published":"2017-01-30"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2016-10183","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Weak WPS PIN generation using time-based seeding allows attackers to bypass authentication on D-Link routers.","url":"https://insights.sbomify.com/CVE-2016-10180/"}