CriticalCVE-2024-11120

    GeoVision EOL devices - OS Command Injection (CVE-2024-11120)

    Published In CISA KEV since Sources: pwn.watch, CVE.org

    What is affected, what to do

    Certain 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.

    The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • GeoVision GV-VS12 eq 0..0
    • GeoVision GV-VS11 eq 0..0
    • GeoVision GV-DSP_LPR_V3 eq 0..0
    • GeoVision GVLX 4 V2 eq 0..0
    • GeoVision GVLX 4 V3 eq 0..0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: pwn.watch, CVE.org

    28.4 %

    EPSS score

    Elevated — model estimates 10-50% exploitation likelihood.

    Source: FIRST EPSS, percentile 98.1

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    232.88 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    28.4 %
    Elevated — model estimates 10-50% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    98.1
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 7 May 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-78

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This CVE is on KEV because CISA and the vendor itself confirmed active exploitation by botnet operators recruiting GeoVision devices into DDoS and proxy networks. Because the flaw is network-reachable with no authentication and sits among the CVEs most likely to be exploited in the wild, every internet-exposed device should be treated as compromised until proven otherwise. KRITIS and NIS2-regulated organisations using these devices for perimeter surveillance, warehouse monitoring or access control must treat replacement as P1 — EoL hardware without a patch path is not a defensible residual risk under NIS2 and should be reflected accordingly in the risk register.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory all affected GeoVision models (GV-DSP_LPR_V3, GVLX 4 V2/V3, GV-VS11, GV-VS12). These are End-of-Life — no vendor patch will be issued. CISA's guidance is explicit: discontinue use.
      • Pull the devices off the public internet immediately: close port forwards for HTTP 80, HTTPS 443, RTSP 554 and the proprietary GeoVision ports (typically 10000/4550) at the perimeter, delete dynamic DNS entries, disable UPnP on upstream routers.
      • Validate external exposure via Shodan/Censys queries against your own ranges for "GeoVision", "GV-VS", "DVR" fingerprints — treat every hit as potentially compromised.
      • Move devices into an isolated VLAN with no routing to production, office LAN or internet; permit only the recording server as an authorised flow.
      • Run a compromise check: rotate admin credentials, review configuration for unknown RTSP streams, cron jobs and firmware modifications. If compromise indicators appear, treat the device as untrusted and replace it — a factory reset will not remove firmware-level implants.
      • Open a P1 ticket for hardware replacement with a supported product line. EoL hardware with no patch path is not an acceptable risk state under NIS2 Article 21 (risk management obligations).

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: dedicated CCTV/OT VLAN with default-deny egress policy, allowing only NVR/VMS flows; no outbound traffic to internet, mail or domain controllers.
      • Perimeter ACL: drop all inbound traffic to device management interfaces (HTTP/HTTPS/Telnet/SSH); permit remote access only via VPN with MFA plus a jump host.
      • If remote access is unavoidable, front the device with a reverse proxy or WAF that blocks shell metacharacters (;, |, `, $(, %0a, &&) in URL parameters and POST bodies to the GeoVision web UI.
      • Enable IPS coverage: Suricata/Snort signatures for HTTP requests to known GeoVision CGI endpoints carrying command-injection payloads. Emerging Threats has shipped rules for CVE-2024-11120 since May 2025 — refresh the ruleset.
      • IAM hardening: audit and replace default credentials (admin/admin, admin/geovision). The vulnerability is pre-auth, but this limits lateral abuse once an attacker lands.
      • Monitor firmware integrity where possible via SNMP/Syslog export; new processes or additional open ports on the device are strong compromise indicators.

    3. Runbook step 3

      Detection rules

      • Web access logs on the device or upstream proxy: GET/POST requests containing URL-encoded shell metacharacters against CGI paths. Sigma shape: selection: cs-uri-query|contains: ['%3B','%7C','%24%28','%60','wget','curl','busybox','/tmp/'].
      • Netflow/Zeek: outbound connections from CCTV VLAN IPs to any non-whitelisted destination, particularly ports 4444, 1337, Tor entry nodes or known bulletproof hosting ranges. Any egress from a camera is suspicious.
      • Suricata: alert on unusual user agents (curl, wget, Mozilla/5.0 (compatible; Mirai)) or empty user agents hitting GeoVision management ports.
      • Hunt for botnet behaviour: SYN scans or brute-force connection rates originating from camera IPs — classic signature of Mirai-/Hiatus-style infection.
      • SIEM correlation: login anomalies on the VMS/NVR from unexpected camera IPs; EDR on the recording server flagging atypical payload sizes from camera subnets.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Certain 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.

    Source: pwn.watch, NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    GeoVisionGV-DSP_LPR_V3
    • 0
    • —
    GeoVisionGV-VS11
    • 0
    • —
    GeoVisionGV-VS12
    • 0
    • —
    GeoVisionGVLX 4 V2
    • 0
    • —
    GeoVisionGVLX 4 V3
    • 0
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Othergeovisiongv-dsp_lpr_firmware—
    Othergeovisiongv-vs11_firmware—
    Othergeovisiongv-vs12_firmware—
    Othergeovisiongvlx_4_firmware—

    Weakness classes (CWE)

    • CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

      Base

      The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

      Entry at MITRE CWE-78

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • twcert.org.twtw/cp-132-8236-d4836-1.htmlThird-party advisory, Third-party advisory
    • twcert.org.twen/cp-139-8237-26d7a-2.htmlThird-party advisory, Third-party advisory
    • akamai.comblog/security-research/active-exploitation-mirai-geovision-iot-…Exploit, Third-party advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2024-11120government-resource, US government resource
    • pwn.watchpwn.watch: GeoVision Multiple Devices: 2 exploited vulnerabilities (CVE-2024-11120, CVE-2024-6047)pwn-watch
    • dlcdn.geovision.com.twGeoVision advisory: GeoVision Multiple Devicespwn-watch
    • NVD (NIST)NVD: CVE-2024-11120pwn-watch
    • NVD (NIST)NVD: CVE-2024-6047pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2024-11120
    <a href="https://intel.neosec.eu/en/cve/CVE-2024-11120"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-11120.svg?lang=en" alt="CVE-2024-11120 – NEOSEC Intel" height="20"></a>