{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19598 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19598 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19598 is a high-severity authentication bypass vulnerability in n/a, published on 5 Dec 2019. 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-2019-19598 and fix it if it is affected.\n\nWhat it is: CVE-2019-19598 is a high-severity authentication bypass vulnerability in n/a, published on 5 Dec 2019. 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-2019-19598 in the wild and no public exploit code.\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-2019-19598/ (Markdown: https://insights.sbomify.com/CVE-2019-19598/index.md)","id":"CVE-2019-19598","markdown":"https://insights.sbomify.com/CVE-2019-19598/index.md","name":"CVE-2019-19598","record":{"aliases":["GHSA-vh9x-535j-rc7j"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"D-Link wireless access point","requires_auth":"none","summary":"Attackers can bypass authentication on D-Link DAP-1860 devices by manipulating the HNAP_AUTH header timestamp, gaining administrator access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dap-1860_firmware","vendor":"dlink"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"D-Link DAP-1860 devices before v1.04b03 Beta allow access to administrator functions without authentication via the HNAP_AUTH header timestamp value. In HTTP requests, part of the HNAP_AUTH header is the timestamp used to determine the time when the user sent the request. If this value is equal to the value stored in the device's /var/hnap/timestamp file, the request will pass the HNAP_AUTH check function.","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":"Auth bypass in n/a","id":"CVE-2019-19598","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-19601"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2019-19597"},"products":["n/a"],"published":"2019-12-05","related":[{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2023-45208","kev_date_added":null,"published":"2023-10-10"},{"cvss_score":8.8,"headline":"Command injection in DAP-1860","id":"CVE-2020-27864","kev_date_added":null,"published":"2021-02-11"},{"cvss_score":8.8,"headline":"Auth bypass in DAP-1860","id":"CVE-2020-27865","kev_date_added":null,"published":"2021-02-11"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2019-19597","kev_date_added":null,"published":"2019-12-05"},{"cvss_score":8,"headline":"Command injection in DAP-1860","id":"CVE-2020-15631","kev_date_added":null,"published":"2020-07-23"}],"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":["n/a"]},"summary":"Attackers can bypass authentication on D-Link DAP-1860 devices by manipulating the HNAP_AUTH header timestamp, gaining administrator access.","url":"https://insights.sbomify.com/CVE-2019-19598/"}