Camera and NVR Vulnerability Tracking: CVEs, Vendor Bulletins and Prioritization

Match your camera and NVR inventory against CVEs, bulletins and CISA KEV; weigh CVSS against exposure, and decide on compensating controls and EOL when patches are delayed.
Technical summary
Technology
CVE, CVSS, EPSS, CISA KEV, NVD, PSIRT
Topic
Tracking and prioritizing camera and NVR vulnerabilities
Level
Intermediate–advanced
Prerequisites
  • A camera inventory including model and firmware information
  • Knowledge of camera network segmentation and access rules
In this article8 sections

Cameras and NVRs are the least monitored devices on the corporate network, the ones that stay in place longest and get updated last. If you can’t answer “do we have this model, and if so how urgent is it?” within minutes when a new security bulletin is published, vulnerability management isn’t being done. Below we cover matching the camera inventory with CVE records and vendor bulletins, weighing the CVSS score together with exposure, and the decisions to make when patches will be delayed or support has ended, in the order they’re applied on site.

Why camera vulnerabilities are tracked separately

Corporate vulnerability management programs focus on servers and clients. Embedded devices where no agent can be installed either don’t appear in reports at all or stay on the “unknown device” line. Reasons cameras need to be handled separately:

  • No agent: version information comes only from the device API, the VMS or the inventory.
  • A different patch cycle: a firmware update reboots the camera, creates a recording gap and can’t be done without testing VMS compatibility.
  • The OEM chain: the same firmware base can be sold under different brands; the vulnerability appears in the original manufacturer’s bulletin, not the label brand’s.
  • Long life: cameras often stay in the field longer than the manufacturer’s support period.
  • Unclear ownership: the camera system may belong to the security department, the network to IT and maintenance to a contractor. If who a vulnerability ticket is assigned to isn’t written down from the start, the ticket goes to nobody.

Matching the inventory with CVEs

Vulnerability tracking can’t be better than the inventory. Minimum fields needed for matching:

Field Example Why it’s needed
Original manufacturer / label brand Manufacturer A / Brand B Catching OEM vulnerabilities
Model and hardware revision Model X, rev. 2 Bulletins are published per model
Firmware version 5.7.x Checking the affected version range
Network location and exposure Camera VLAN, no NAT Prioritization
Open services HTTPS, RTSP, manufacturer SDK port Matching with the attack vector
End-of-support date From the manufacturer’s lifecycle page Patch expectation

Keeping firmware versions by hand collapses within a few months. As sources, you can use the VMS device list export, the manufacturer’s device management software or the ONVIF GetDeviceInformation call; in this call ONVIF returns the manufacturer, model, firmware version, serial number and hardware ID. For the structure of inventory fields, see the how to keep a camera inventory guide.

If you’ll run a service scan to verify the inventory, be cautious on the camera network. Some embedded devices stop responding or reboot under heavy scanning; recording gaps caused by scanning are seen on site. Run the scan in a maintenance window, at low speed and on a pilot subnet first:

# Low-speed scan of typical services and version info on the camera subnet
nmap -sV -T2 -p 80,443,554,8000,37777 10.20.30.0/24 -oX camera-scan.xml

Ports 8000 and 37777 in the example are default ports some manufacturers use for SDK/client protocols. These ports appearing open also gives a clue for guessing the original manufacturer behind the label.

Sources: vendor bulletins, NVD, CISA KEV

Source What it grants Limitation
Vendor PSIRT bulletins Affected model, version and fixed firmware Format differs for each manufacturer; OEM brands may not publish
NVD (CVE + CVSS + CPE) Standard record, score, machine-readable API Enrichment may be delayed; CPE matching may be incomplete
CISA KEV catalog CVEs known to be actively exploited Only records with confirmed exploitation
CISA ICS advisories Detailed advisories for industrial and surveillance products Doesn’t cover all manufacturers
FIRST EPSS Estimated probability of exploitation in the next 30 days A probabilistic model; doesn’t know the organization’s context
USOM announcements Warnings and notices aimed at Türkiye (from USOM, Türkiye’s national CERT) Coverage varies by announcement

The primary source is the vendor bulletin; only the manufacturer says which firmware contains the fix. Record the security bulletin page of every manufacturer in the inventory and, if available, the email or RSS subscription. The CISA KEV catalog is also published in JSON format; regularly matching it with the manufacturers in the inventory is a few lines of work:

curl -sO https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json

jq -r '.vulnerabilities[]
  | select(.vendorProject | test("Hikvision|Dahua|Axis|Hanwha|Bosch"; "i"))
  | [.cveID, .vendorProject, .product, .dateAdded] | @tsv' \
  known_exploited_vulnerabilities.json

Don’t write the manufacturer list by hand; generate it from your inventory. For example, the command injection vulnerability in the Hikvision web server, CVE-2021-36260, is in this catalog. Camera products appearing on active exploitation lists shows the risk isn’t theoretical.

Prioritization: CVSS and exposure

The CVSS base score gives a vulnerability’s technical severity; it doesn’t give its urgency on your network. On a camera network, three questions determine urgency: Is active exploitation known? Who can reach the attack vector? Is authentication required? The matrix below is an example policy; set target times according to your own maintenance capacity.

Status Priority Example target time
In KEV or exploit code published, and the device reachable from the internet / user network Emergency Restrict access the same day, apply the patch in the earliest maintenance window
Unauthenticated remote exploitation (CVSS critical), device only in the camera VLAN High Within a few weeks
Exploitation requiring authentication or from the local network, behind a strict ACL Intermediate In the planned firmware cycle
A vulnerability in an unused service (the service can be disabled) Low Disable the service, patch in the next cycle

Fill in the “reachable” column with evidence, not assumptions: firewall and ACL rules, NAT and port forwarding records, whether the manufacturer’s P2P cloud service is enabled. The last one is the point often skipped. An NVR with P2P cloud access enabled counts as reachable from outside even without port forwarding; we covered this in the P2P cloud access vs VPN comparison article.

Compensating controls when a patch can’t be applied

There are legitimate reasons for patch delays: VMS compatibility hasn’t been verified, the camera is in an area that can’t tolerate downtime, or the manufacturer hasn’t released a fix yet. This time shouldn’t be wasted. Compensating controls to choose depending on the vulnerability:

  • Narrowing access: access to the vulnerable service (web interface, SDK port) only from the recording server and management station; all other sources are denied by ACL.
  • Disabling the service: unused UPnP, P2P, Telnet/SSH, FTP or manufacturer SDK services are disabled. A disabled service can’t be exploited.
  • Blocking egress: connections the camera initiates to the internet and the user network are blocked; post-exploitation command-and-control connections and lateral movement become harder.
  • Tightening monitoring: for the vulnerable device group, thresholds for new destination IP, new port and authentication failure alarms are lowered.
  • Rotating credentials: for vulnerabilities that leak credentials, passwords and certificates are changed after patching too. A patch closes the hole; it doesn’t take back a stolen password.

Every compensating control should be recorded with which vulnerability it was applied for and when it will be removed. An unrecorded temporary exception turns into a permanent rule that nobody can explain a few years later.

Out-of-support devices: isolation or replacement

When the manufacturer stops releasing security updates, every new vulnerability for that device is permanent. No patch is coming. Verify end-of-support dates on the manufacturer’s current lifecycle page, record them in the inventory and make the decision explicitly:

Decision When it fits Condition
Replacement A device with access to the internet or the user network; a known exploited vulnerability Added to the budget and lifecycle plan
Isolation + risk acceptance A device that talks to no system other than the recording server and can’t be replaced in the short term Written risk acceptance, owner and review date
Decommissioning A device whose coverage is provided by another camera The port is shut down and the device removed from the inventory

Making replacement decisions together within a lifecycle plan, rather than one by one, is more manageable budget-wise; for details, see the camera system lifecycle and renewal plan guide.

Monthly vulnerability review cycle

  1. Refresh the inventory: pull the model and firmware list from the VMS and device management tool; fix differences with the inventory.
  2. Scan the sources: match records published in vendor bulletins, KEV and NVD since the last review with the manufacturers and models in the inventory.
  3. Prioritize: add exposure evidence to every match and apply the priority matrix.
  4. Assign: set an owner and date for the firmware update, compensating control or risk acceptance.
  5. Verify: read the firmware version of records closed the previous month from the device again. “Updated” in the inventory isn’t evidence; the version the device reports is.
  6. Report: the number of open records, overdue records and out-of-support devices are presented to management on a single page.

Urgent-priority records don’t wait for the monthly cycle; a record newly added to KEV that matches your inventory triggers an extraordinary review. To connect with the organization’s overall vulnerability program, the vulnerability management program article is complementary.

To independently establish the vulnerability status of your existing camera fleet, see our camera systems technical audit service, and for closing findings on the firmware side, our firmware update management service.

Frequently asked questions

Is a classic vulnerability scanner enough to find camera vulnerabilities?

Not on its own. Scanners can’t always read camera firmware versions correctly, and some cameras reboot under heavy scanning. The main method is matching the model and firmware information in the inventory with vendor bulletins; scanning is used to verify it.

Is every vulnerability with a high CVSS score urgent?

No. CVSS shows a vulnerability’s technical severity; urgency is determined by active exploitation information and who can reach the camera. A high-scoring vulnerability on a camera that can’t be reached from the internet, behind a strict ACL, can be handled after a medium-scoring, actively exploited vulnerability on an internet-facing NVR.

Can a camera that appears to be a different brand be affected by another manufacturer’s vulnerability?

Yes. Some brands sell other manufacturers’ hardware and firmware under their own label. The vulnerability is published in the original manufacturer’s bulletin, and the label brand may not publish a bulletin. So record the device’s original manufacturer and firmware base in the inventory.

Is it mandatory to replace an out-of-support camera immediately?

It isn’t mandatory, but it requires a risk decision. The camera can be used for a while in an isolated segment, restricted to talking only to the recording server, with a written risk acceptance. Out-of-support devices with access to the internet or the user network, however, should be added to the replacement plan.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Video Surveillance

IP cameras, recording and central management infrastructure. We plan blind spots, retention periods and the camera network around the risks of each site.

Knowledge Center

Other articles