{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-51629 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-51629 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-51629 is a medium-severity vulnerability in D-Link DCS-8300LHV2, published on 3 May 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-51629 and fix it if it is affected.\n\nWhat it is: CVE-2023-51629 is a medium-severity vulnerability in D-Link DCS-8300LHV2, published on 3 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-51629 in the wild and no public exploit code.\n\nAffected product: D-Link DCS-8300LHV2. 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-2023-51629/ (Markdown: https://insights.sbomify.com/CVE-2023-51629/index.md)","id":"CVE-2023-51629","markdown":"https://insights.sbomify.com/CVE-2023-51629/index.md","name":"CVE-2023-51629","record":{"aliases":["GHSA-cw65-c3g7-7rw3"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"D-Link IP camera","requires_auth":"none","summary":"Network-adjacent attackers can bypass authentication on D-Link IP cameras by exploiting a hardcoded PIN in the ONVIF API configuration.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"dcs-8300lhv2_firmware","vendor":"dlink"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-259","name":"Use of Hard-coded Password"}],"description":"D-Link DCS-8300LHV2 ONVIF Hardcoded PIN Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of D-Link DCS-8300LHV2 IP cameras. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the configuration of the ONVIF API. The issue results from the use of a hardcoded PIN. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-21492.","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":"D-Link DCS-8300LHV2 ONVIF Hardcoded PIN Authentication Bypass Vulnerability","id":"CVE-2023-51629","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Paessler PRTG Network Monitor Cross-Site Scripting Authentication Bypass Vulnerability","id":"CVE-2023-51630"},"packages":[],"prev":{"headline":"D-Link DCS-8300LHV2 ONVIF SetHostName Stack-Based Buffer Overflow Remote Code Execution Vulnerability","id":"CVE-2023-51628"},"products":["DCS-8300LHV2"],"published":"2024-05-03","related":[{"cvss_score":8.8,"headline":"Memory corruption in DCS-8300LHV2","id":"CVE-2023-51624","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":8.8,"headline":"Memory corruption in DCS-8300LHV2","id":"CVE-2023-51626","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":8,"headline":"D-Link DCS-8300LHV2 ONVIF SetSystemDateAndTime Command Injection Remote Code Execution Vulnerability","id":"CVE-2023-51625","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":8,"headline":"D-Link DCS-8300LHV2 ONVIF Duration Stack-Based Buffer Overflow Remote Code Execution Vulnerability","id":"CVE-2023-51627","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":8,"headline":"D-Link DCS-8300LHV2 ONVIF SetHostName Stack-Based Buffer Overflow Remote Code Execution Vulnerability","id":"CVE-2023-51628","kev_date_added":null,"published":"2024-05-03"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["D-Link"]},"summary":"Network-adjacent attackers can bypass authentication on D-Link IP cameras by exploiting a hardcoded PIN in the ONVIF API configuration.","url":"https://insights.sbomify.com/CVE-2023-51629/"}