CVE-2024-11120
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 · uneditedCertain EOL GeoVision devices have an OS Command Injection vulnerability. Unauthenticated remote attackers can exploit this vulnerability to inject and execute arbitrary system commands on the device. Moreover, this vulnerability has already been exploited by attackers, and we have received related reports.
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 · high confidenceThis is an OS command injection vulnerability in End-of-Life (EOL) GeoVision devices that allows unauthenticated remote attackers to inject and execute arbitrary system commands on the affected devices. The vulnerability has a CVSS score of 9.8 (Critical) and is being actively exploited in the wild.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsCVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the device modelLog into the device admin interface or check physical device labeling to confirm the exact model number. GeoVision devices are typically NVRs, cameras, or access control panels.Affected if The model is Gv Vs12, Gv Vs11, Gv Dsp Lpr, or Gvlx 4
-
Verify the firmware versionAccess the device web interface under System > Information or use the GV Device Manager software to retrieve the installed firmware version.Affected if The device is one of the four affected models regardless of firmware version (all versions are vulnerable)
-
Assess network exposureReview firewall rules, NAT configurations, and network segmentation to determine if the device is directly accessible from the internet or untrusted networks.Affected if The device is reachable from external networks without firewall filtering
-
Check for unauthorized access or compromiseReview device logs for unfamiliar IP addresses, unexpected administrative accounts, or commands initiated from unknown sources. Look for new scheduled tasks or processes.Affected if Logs show commands or configuration changes from unexpected sources, or new admin accounts exist that were not created by your team
You are affected if you have a GeoVision Gv Vs12, Gv Vs11, Gv Dsp Lpr, or Gvlx 4 device on your network, especially if it is network-exposed.
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 dataSince these are EOL devices no longer receiving vendor security updates, organizations should replace them with supported alternatives. If continued operation is unavoidable, implement strict network isolation, firewall rules, and access controls to minimize exposure to unauthenticated attackers.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11120 — 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-11120 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