CVE-2024-6047
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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. OS command injection puts shell syntax into the request. WAF rules catch common shell commands but miss encoded or unusual payloads.
Also consider: shlex/execve-style APIs
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-6047 being exploited?
Yes. CVE-2024-6047 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-6047?
CVE-2024-6047 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-6047?
Not known from our data. No patch reference has been recorded for CVE-2024-6047, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2024-6047 affect?
CVE-2024-6047 affects geovision:gv-dsp_lpr_firmware, geovision:gv-bx130_firmware, geovision:gv-bx1500_firmware, geovision:gv-cb220_firmware, and 16 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 7 May 2025 (SSVC 2.0.3).
timeline
- 17 Jun 2024Published
- 7 May 2025Added to CISA KEV (exploited in the wild) · 324 days (about 11 months) later
- 7 May 2025CISA SSVC assessment: exploitation active · 1 day later
- 28 May 2025CISA remediation due date (US federal agencies) · 20 days later
- 21 Oct 2025CVE record last updated · 147 days (about 5 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Advisorytwcert.org.tw /tw/cp-132-7883-f5635-1.html
- Advisorytwcert.org.tw /en/cp-139-7884-c5a8b-2.html
- Linkakamai.com /blog/security-research/active-exploitation-mirai-geovision-iot-botnet
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-6047
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.