How severe is CVE-2018-9995?

CVE-2018-9995 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-9995?

Affected package information for CVE-2018-9995 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2018-9995?

No fixed version has been published for CVE-2018-9995 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2018-9995 actively exploited in the wild?

Yes. There are 28 known exploit references for CVE-2018-9995, including 1 documented proof-of-concept exploit on Exploit-DB and 18 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-9995?

CVE-2018-9995 has an EPSS (Exploit Prediction Scoring System) score of 94.1%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Which products and versions are affected by CVE-2018-9995?

CVE-2018-9995 affects tbkvision tbk-dvr4104 firmware; tbkvision tbk-dvr4216 firmware. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2018-9995?

A Nuclei detection template exists for CVE-2018-9995, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2018-9995 published, and has it been updated?

CVE-2018-9995 was published on April 10, 2018 and was last updated on November 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2018-9995

CRITICAL

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…

Published

Apr 10, 2018

Updated

Nov 21, 2024

Affected

0 pkgs

Patched

None yet

Exploits

28 known

EPSS Exploitation Probability

via FIRST.org ↗

94.1%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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&cmd=list request that provides credentials within JSON data in a response.

Affected Products

2 products · 2 configurations

tbk-dvr4104 firmwaretbkvision

all

tbk-dvr4216 firmwaretbkvision

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-44577remotehardware

TBK DVR4104 / DVR4216 - Credentials Leak

by ezelf · May 2, 2018

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-9995 in your stack?

O3 detects CVE-2018-9995 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works