Skip to main content
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

Unauthenticated OS Command Injection in GeoVision EoL Devices

IdentifiersCVE-2024-11120CWE-78· Improper Neutralization of Special…

CVE-2024-11120 is an unauthenticated operating system command injection vulnerability affecting select end-of-life GeoVision devices, including GV-VS12, GV-VS11, GV-DSP_LPR_V3, GVLX 4 V2, and GVLX 4 V3. Available reporting indicates attackers can remotely inject arbitrary system commands via a vulnerable web-exposed interface, with observed exploitation abusing the /DateSetting.cgi endpoint and injecting commands through the szSrvIpAddr parameter. The flaw allows remote command execution on the underlying device OS without authentication. Reporting also states the vulnerability has been exploited in the wild, including activity observed by Akamai in campaigns delivering and executing an ARM-based Mirai variant dubbed LZRD.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation allows an unauthenticated remote attacker to execute arbitrary system commands on the affected GeoVision device. This can result in full compromise of the appliance, malware installation, botnet enrollment, persistence, service disruption, device manipulation, and use of the device as a foothold for further malicious activity. Public reporting specifically links exploitation of this flaw to Mirai-family malware deployment in the wild.

Mitigation

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

If immediate replacement is not possible, remove affected devices from direct Internet exposure, restrict access to management/web interfaces to trusted administrative networks only, place devices behind firewalls or VPNs, and monitor for exploitation attempts against /DateSetting.cgi and suspicious use of the szSrvIpAddr parameter. Organizations should also inspect devices for signs of compromise, including unexpected process execution, malware downloads, or Mirai/LZRD-related artifacts, and isolate any suspected compromised systems. Given active exploitation, mitigation should be treated as temporary until the devices are replaced or otherwise fully remediated.

Remediation

Patch, then assume compromise.

Affected organizations should follow vendor guidance for CVE-2024-11120. Because the impacted GeoVision models are reported to be end-of-life, patch availability may be limited or nonexistent. Where a vendor fix is unavailable, the appropriate remediation is to decommission and replace affected devices with supported models. CISA reporting referenced mitigation or device decommissioning for the GeoVision flaws in KEV-related guidance.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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
GeovisionGv-Dsp Lpr Firmwareoperating_system
GeovisionGv-Dsp Lpr V3 Firmwareoperating_system
GeovisionGv-Vs11 Firmwareoperating_system
GeovisionGv-Vs12 Firmwareoperating_system
GeovisionGvlx 4 Firmwareoperating_system
GeovisionGvlx 4 V2 Firmwareoperating_system
GeovisionGvlx 4 V3 Firmwareoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence1

Every observed campaign linking this CVE to a named adversary.

Associated malware2

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity8

Community discussion across Reddit, Mastodon, and other social sources.