{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-9995 exists.","fix":"No fix has been published for CVE-2018-9995 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-9995 is a critical authentication bypass vulnerability in n/a, published on 10 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-9995 and fix it if it is affected.\n\nWhat it is: CVE-2018-9995 is a critical authentication bypass vulnerability in n/a, published on 10 Apr 2018. 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-2018-9995 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-2018-9995/ (Markdown: https://insights.sbomify.com/CVE-2018-9995/index.md)","id":"CVE-2018-9995","markdown":"https://insights.sbomify.com/CVE-2018-9995/index.md","name":"CVE-2018-9995","record":{"aliases":["GHSA-mjcj-jjh8-28r2"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"DVR security system","requires_auth":"none","summary":"Remote attackers can bypass authentication on TBK DVR devices by sending a specific cookie header, gaining admin access to view user credentials.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tbk-dvr4104_firmware","vendor":"tbkvision"},{"product":"tbk-dvr4216_firmware","vendor":"tbkvision"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"TBK DVR4104 and DVR4216 devices, as well as Novo, CeNova, QSee, Pulnix, XVR 5 in 1, Securus, Night OWL, DVR Login, HVR Login, and MDVR Login, which run re-branded versions of the original TBK DVR4104 and DVR4216 series, allow remote attackers to bypass authentication via a \"Cookie: uid=admin\" header, as demonstrated by a device.rsp?opt=user\u0026cmd=list request that provides credentials within JSON data in a response.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-04-29","github_poc":26,"max_poc_stars":559,"metasploit":0,"nuclei":1,"refs":[{"date":"2018-04-29T20:00:06Z","kind":"github_poc","ref":"https://github.com/ezelf/CVE-2018-9995_dvr_credentials","stars":559,"title":"(CVE-2018-9995) Get DVR Credentials"},{"date":"2018-09-23T20:58:40Z","kind":"github_poc","ref":"https://github.com/Cyb0r9/DVR-Exploiter","stars":112,"title":"DVR-Exploiter a Bash Script Program Exploit The DVR's Based on CVE-2018-9995"},{"date":"2025-10-28T15:30:18Z","kind":"github_poc","ref":"https://github.com/0xDamian/CVE-2018-9995-rs","stars":96,"title":"POC of CVE-2018-9995 written in Rust."},{"date":"2024-02-18T12:46:32Z","kind":"github_poc","ref":"https://github.com/X3RX3SSec/DVR_Sploit","stars":11,"title":"Simple python3 script to automate CVE-2018-9995"},{"date":"2018-05-08T12:07:26Z","kind":"github_poc","ref":"https://github.com/zzh217/CVE-2018-9995_Batch_scanning_exp","stars":4,"title":"CVE-2018-9995_Batch_scanning_exp"},{"date":"2021-06-07T05:57:43Z","kind":"github_poc","ref":"https://github.com/kienquoc102/CVE-2018-9995-2","stars":4,"title":null},{"date":"2020-02-15T04:42:17Z","kind":"github_poc","ref":"https://github.com/wmasday/HTC","stars":3,"title":"Hack The CCTV | DVRs; Credentials Exposed | CVE-2018-9995"},{"date":"2018-05-09T00:43:24Z","kind":"github_poc","ref":"https://github.com/Huangkey/CVE-2018-9995_check","stars":2,"title":"DVR系列摄像头批量检测"}],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2018-9995","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2018-9996"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2018-9994"},"products":["n/a"],"published":"2018-04-10","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2018-10676","kev_date_added":null,"published":"2018-05-02"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can bypass authentication on TBK DVR devices by sending a specific cookie header, gaining admin access to view user credentials.","url":"https://insights.sbomify.com/CVE-2018-9995/"}