OS Command Injection in GeoVision LPC2011/LPC2211 (CVE-2026-42364)
Summary
OS command injection in GeoVision LPC2011/LPC2211 (CVE-2026-42364). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
An os command injection vulnerability exists in the DdnsSetting.cgi functionality of GeoVision LPC2011/LPC2211 1.10. A specially crafted DDNS configuration can lead to arbitrary command execution. An attacker can modify a configuration value to trigger this vulnerability.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42364 has been found in GeoVision LPC2011/LPC2211.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "GeoVision LPC2011/LPC2211 CVE-2026-42364" on the vendor's site.
CVE-2026-42364 (GeoVision LPC2011/LPC2211) — CWE-78 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in GeoVision LPC2011/LPC2211.
Check the vendor advisory for the affected versions of GeoVision LPC2011/LPC2211.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで GeoVision LPC2011/LPC2211 を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory talosintelligence.com
- patch geovision.com.tw
- web nvd.nist.gov
- web talosintelligence.com
- web talosintelligence.com
- web github.com