CVE-2024-29949
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThere is a command injection vulnerability in some Hikvision NVRs. This could allow an authenticated user with administrative rights to execute arbitrary commands.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a command injection vulnerability (CWE-78) in Hikvision Network Video Recorders (NVRs). An authenticated user with administrative privileges can inject and execute arbitrary operating system commands due to insufficient input validation, potentially leading to complete device compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Hikvision NVR deviceAccess the device web interface or check network scan results for Hikvision NVR login page (typically port 80/443). Look for 'Hikvision' or 'NVR' in the web interface title or favicon.Affected if The device is a Hikvision Network Video Recorder with web management interface exposed.
-
Confirm web management is network-accessibleCheck if ports 80, 443, or 8080 are open and responding on the NVR device from your detection position. Use 'nmap -p 80,443 <device-ip>' or similar network scan.Affected if The NVR web management interface is accessible from network segments that contain untrusted users.
-
Verify administrative user existsLog into the NVR web interface with administrative credentials, or check user configuration to confirm at least one admin-level account is configured.Affected if An authenticated user with administrative privileges can access the NVR.
-
Check firmware versionIn the NVR web interface, navigate to System > Maintenance > System Info or similar path to view the firmware version. Compare against any Hikvision security advisories for CVE-2024-29949.Affected if The installed firmware version matches the affected version range for this vulnerability (if published by vendor).
A user is affected if they have a Hikvision NVR with web interface exposed to network and an admin-authenticated user can access the command injection point.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply available vendor firmware patches, restrict administrative access to trusted IPs only, and implement network segmentation to isolate NVR devices from untrusted networks.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29949 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-29949 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data