Security readout for executives and security teams
Plain-English summary
CVE-2024-6047 lets an unauthenticated remote attacker run system commands on certain end-of-life GeoVision devices. For exposed cameras or video servers, this can mean full device compromise, service disruption, and a foothold for botnet activity.
Executive priority
Treat this as a near-term operational risk, not routine patching. The vulnerability is critical, unauthenticated, remotely exploitable, listed in KEV, and affects EOL security devices that may lack normal patch paths.
Technical view
This is a CWE-78 OS command injection flaw in specific functionality on listed EOL GeoVision GV devices. The CVSS 3.1 score is 9.8 because exploitation is network-reachable, low complexity, requires no credentials or user interaction, and can impact confidentiality, integrity, and availability.
Likely exposure
Exposure is most likely where the listed GeoVision EOL camera, LPR, or video server models are reachable from the internet, partner networks, or flat internal networks. The sources identify listed products and all versions, but do not establish exposure for any specific environment.
Exploitation context
Active exploitation is supported by CISA KEV status and Akamai reporting on Mirai-related exploitation of GeoVision IoT devices. The source bundle does not justify assuming every listed device is compromised, but internet-facing instances should be treated as urgent.
Researcher notes
The evidence supports critical severity, unauthenticated remote command execution, and active exploitation. Product coverage is limited to the listed EOL GeoVision models. The bundle does not provide exploit mechanics or a confirmed universal patch, so validation should stay inventory- and exposure-focused.
Mitigation direction
- Identify and prioritize listed EOL GeoVision devices in asset inventory.
- Remove affected devices from direct internet exposure immediately.
- Place required devices behind VPN, firewall rules, and network isolation.
- Check GeoVision or TWCERT guidance for product-specific replacement or mitigation.
- Replace or retire affected EOL devices where no supported fix exists.
- Monitor for botnet, command execution, and unusual outbound traffic indicators.
Validation and detection
- Search inventories for the exact listed GeoVision model names.
- Confirm whether device management interfaces are internet-reachable.
- Review firewall, NAT, and remote access rules for exposed devices.
- Check logs and network telemetry for unusual outbound connections.
- Verify segmentation prevents affected devices reaching sensitive systems.
- Track CISA KEV handling through vulnerability management records.
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-6047 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-7883-f5635-1.htmlCVE reference · third-party-advisory
- https://www.twcert.org.tw/en/cp-139-7884-c5a8b-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-6047CVE 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.