Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2015-4464: Missing Authentication in Kguard DVR 104/108/v2

Published Aug 18, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3
EPSS4.7%92nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
KGuard Security
IdentifiersCVE-2015-4464CWE-306

Kguard Digital Video Recorder models 104, 108, and v2 lack any form of authorization or authentication between the ActiveX client and the application server. This means that any client can connect to the server and interact with it without providing credentials or being subject to access controls.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can connect to the DVR application server without authentication, potentially gaining full access to video feeds, device configuration, and other sensitive functions. This exposes the device to unauthorized access, surveillance, and manipulation.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to the DVR to trusted hosts only, segment the device from untrusted networks, and monitor for unauthorized connection attempts until a patch is available.

Remediation

Patch, then assume compromise.

Implement proper authentication and authorization mechanisms between the ActiveX client and the application server. Ensure that only authenticated and authorized users can access the DVR's functions.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
KGuard SecurityKg-Sha104 Firmwareoperating_system
KGuard SecurityKg-Sha108 Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2015-4464 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2015-4464 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2015-4464?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2015-4464.
Is there a patch for CVE-2015-4464?
Implement proper authentication and authorization mechanisms between the ActiveX client and the application server. Ensure that only authenticated and authorized users can access the DVR's functions.
What products are affected by CVE-2015-4464?
KGuard Security Kg-Sha104 Firmware and KGuard Security Kg-Sha108 Firmware.
How severe is CVE-2015-4464?
CVE-2015-4464 has a CVSS v3 score of 9.8 (Critical) and an EPSS score of 4.7% (92nd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.