Skip to content
Fencer Vulns
critical 9.8

CVE-2018-9995 in the critical feed json

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 Logi…

published 2018-04-10 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-21587

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
82.3%
EPSS 82.3% chance of exploitation in 30 days, percentile 99.6%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

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.

Timeline

  1. Published
  2. First public exploit (EDB-44577)

Exploit prediction

82.32% chance of exploitation in the next 30 days, higher than 99.6% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-44577 TBK DVR4104 / DVR4216 - Credentials Leak remote, 2018-05-02
  • Nuclei template TBK DVR4104/DVR4216 Devices - Authentication Bypass nuclei detection template
  • bleepingcomputer.com https://www.bleepingcomputer.com/news/security/new-hacking-tool-lets-users-access-a-bunch-of-dvrs-and-their-video-feeds/ referenced PoC, tagged "exploit" by a source, unverified
  • misteralfa-hack.blogspot.cl http://misteralfa-hack.blogspot.cl/2018/04/tbk-vision-dvr-login-bypass.html referenced PoC, tagged "exploit" by a source, unverified
  • misteralfa-hack.blogspot.cl http://misteralfa-hack.blogspot.cl/2018/04/update-dvr-login-bypass-cve-2018-9995.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.