Threats / GeoVision / CVE-2024-6047
CVE-2024-6047
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
GeoVision Multiple Devices vulnerability
Multiple GeoVision devices are vulnerable to OS command injection, allowing remote unauthenticated attackers to execute arbitrary system commands. Affected products may be end-of-life or end-of-service.
Verdict
Today item — known-exploited.
Remote unauthenticated OS command injection in GeoVision devices enables direct system compromise without authentication. Active exploitation in the wild and high EPSS score indicate immediate risk. Discontinuation of affected products is recommended.
CISA KEV Yes · 2025-05-075EPSS 0.10072 (verify live)6CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
9 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-05-07).
Probability (EPSS)
EPSS 0.10072 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: GeoVision, Multiple Devices. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 324 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify a GeoVision device exposed on the network without authentication requirements.
Business
Surveillance infrastructure becomes a direct entry point for network compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft a malicious request containing shell metacharacters to inject OS commands through an unvalidated input parameter.
Business
Attacker gains arbitrary code execution with device privileges, bypassing all access controls.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute reconnaissance commands to map the network, escalate privileges, or establish persistence.
Business
Compromised device becomes a foothold for lateral movement and data exfiltration across the organization.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05