SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2024-6047Public Intelligence Dossier
Source: geovision · Limited verification•Last verified: •Collection Degraded
CVE-2024-6047ListedCRITICAL (raw)CVSS 9.8CWE-78

Certain EOL GeoVision devices fail to properly filter user input for the specific functionality

Published: 17 Jun 2024•Last updated: 17 Jun 2026, 01:47 PM IST•Source identifier: twcert@cert.org.tw
Dossier completeness: source-provided sections 3 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Listed
Added07 May 2025
Due28 May 2025
RansomwareUnknown
CVSS score
9.8CRITICAL (raw)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Metric sourcetwcert@cert.org.tw
EPSS probability
10.1%0.101
Percentile96th
Weakness type
CWE-78
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

Certain EOL GeoVision devices fail to properly filter user input for the specific functionality. Unauthenticated remote attackers can exploit this vulnerability to inject and execute arbitrary system commands on the device.

SOC priority

Immediate Attention

Actively exploited (source statement)

Yes

Publicly disclosed

Unknown

Risk basis: CISA KEV exploitation signal; CRITICAL severity; Known exploitation signal from CISA KEV or ransomware metadata; Source-confirmed exploitation or CISA KEV/ransomware metadata

Affected Products & Remediation

20 source-backed products
Affected products and versions (source)
  • geovision gv-dsp lpr firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-bx130 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-bx1500 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-cb220 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-ebl1100 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-efd1100 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-fd2410 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-fd3400 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-fe3401 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-fe420 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-gm8186 vs14 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-vs14 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-vs03 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-vs2410 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-vs21600 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-vs04a firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-vs04h firmware · version range not provided by source · NVD CPE · Source
  • geovision gvlx 4 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-vs2800 firmware · version range not provided by source · NVD CPE · Source
  • geovision gv-vs2820 firmware · version range not provided by source · NVD CPE · Source
NVD applicability prerequisites: cpe:2.3:h:geovision:gv-dsp_lpr:2.0:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-bx130:-:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-bx1500:-:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-cb220:-:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-ebl1100:-:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-efd1100:-:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-fd2410:-:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-fd3400:-:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-fe3401:-:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-fe420:-:*:*:*:*:*:*:*. These are conditions, not proof that an environment is exposed or unaffected.
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

  • CISA KEV: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Listed
Exploited (source statement)
Yes
Publicly disclosed (source)
Unknown

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched kev-network-exposure (CVSS AV:N, CISA KEV Listed); command-injection (CWE-78)

Exposure

  1. Identify assets with the exact CVE and confirm the affected product/version against the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · KEV listing raises urgency, but inventory is needed to establish local exposure. · Rule kev-network-exposure
  2. Identify installations of the affected product and compare versions with the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · A weakness class does not establish local exposure. · Rule command-injection

Exploitation evidence

  1. Review relevant edge or application access logs for unusual requests around the advisory window.Telemetry: CommonSecurityLog · Log review is a hunting hypothesis; KEV listing alone does not show local exploitation. · Rule kev-network-exposure
Show more (2)

Exploitation evidence

  1. Review command interpreters spawned by the affected service or application.Telemetry: DeviceProcessEvents · Unexpected process lineage can support command-injection hunting. · Rule command-injection

Response

  1. Recheck the affected assets after the source-stated mitigation or update is applied.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies local remediation. · Rule kev-network-exposure

CISA KEV Record

Catalog entry
07 May 2025
Required action due
28 May 2025
Known ransomware use
Unknown

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Change History & Source Data

— No recorded material change

CNA / source
twcert@cert.org.tw
Record status · verification
UPDATED · CISA KEV confirmed
CPE
cpe:2.3:o:geovision:gv-dsp_lpr_firmware:-:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-dsp_lpr:2.0:*:*:*:*:*:*:*, cpe:2.3:o:geovision:gv-bx130_firmware:-:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-bx130:-:*:*:*:*:*:*:*, cpe:2.3:o:geovision:gv-bx1500_firmware:-:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-bx1500:-:*:*:*:*:*:*:*, cpe:2.3:o:geovision:gv-cb220_firmware:-:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-cb220:-:*:*:*:*:*:*:*, cpe:2.3:o:geovision:gv-ebl1100_firmware:-:*:*:*:*:*:*:*, cpe:2.3:h:geovision:gv-ebl1100:-:*:*:*:*:*:*:*

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2024-6047
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2024-6047
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2024-6047"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.

Looking up related community queries…

Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.