Security readout for executives and security teams
Plain-English summary
This is a critical remote command execution flaw in certain end-of-life GeoVision devices. An unauthenticated internet attacker could take control of an exposed device. The source bundle states it has already been exploited, and CISA lists it in KEV, so this should be treated as urgent for any environment using these products.
Executive priority
Treat this as an immediate exposure-reduction issue, not routine patching. The devices are end-of-life, unauthenticated exploitation is reported, and CISA KEV confirms known exploitation. Leadership should fund rapid discovery, isolation, and replacement planning.
Technical view
CVE-2024-11120 is CWE-78 OS command injection affecting certain EOL GeoVision devices, including GV-VS12, GV-VS11, GV-DSP_LPR_V3, GVLX 4 V2, and GVLX 4 V3. CVSS is 9.8: network reachable, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Highest risk is internet-facing GeoVision video, DSP, or LPR appliances matching the named EOL products. Internal-only devices still matter if attackers gain network access. The provided affected-version data is sparse, so asset confirmation should rely on model inventory and vendor/TWCERT guidance.
Exploitation context
Active exploitation is supported by the CVE description, Akamai’s Mirai-focused research reference, and CISA KEV inclusion. The public bundle supports botnet-style targeting of exposed IoT devices, but does not provide enough detail here to confirm every campaign, payload, or victim profile.
Researcher notes
The bundle confirms command injection, unauthenticated remote reachability, critical CVSS, KEV status, and named EOL GeoVision products. It does not include exact vulnerable firmware ranges, exploit mechanics, indicators, or definitive patch availability. Avoid over-claiming beyond those sources.
Mitigation direction
- Inventory for the named GeoVision EOL models across external and internal networks.
- Remove internet exposure for any matching device immediately.
- Check GeoVision and TWCERT guidance before assuming a firmware fix exists.
- Prioritize replacing affected EOL devices where supported remediation is unavailable.
- Monitor perimeter logs for suspicious access to exposed GeoVision devices.
- Segment remaining devices from sensitive business systems.
Validation and detection
- Confirm whether GV-VS12, GV-VS11, GV-DSP_LPR_V3, GVLX 4 V2, or GVLX 4 V3 are deployed.
- Check external attack surface records for public exposure of matching devices.
- Review CISA KEV tracking for required remediation deadlines in regulated environments.
- Verify whether vendor or TWCERT guidance identifies supported updates or replacement steps.
- Look for unexpected outbound traffic or device behavior consistent with compromise.
Public sources used
Michael Williams reviewed this cited source version on .
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-11120 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.twcert.org.tw/tw/cp-132-8236-d4836-1.htmlCVE reference · third-party-advisory
- https://www.twcert.org.tw/en/cp-139-8237-26d7a-2.htmlCVE reference · third-party-advisory
- https://www.akamai.com/blog/security-research/active-exploitation-mirai-geovision-iot-botnetCVE reference
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-11120CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.