GV-LPC2011/LPC2211 - unauthorized out-of-bounds writing vulnerability (onvif.cgi)
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-787 and the CVSS impact.
Summary
An unauthenticated out-of-bounds write vulnerability exists in onvif.cgi in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability is caused by insufficient bounds checking when processing HTTP request body data. A remote attacker may exploit this vulnerability by sending a crafted request with excessive input, causing memory corruption and resulting in a denial of service.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA GV-LPCLPC2011/2211 (GeoVision Inc.) Fixed in 1.13
Timeline
- 2026-10-02 Threatist record created from CVE-2026-57876
- 2026-10-03 Alias added: GHSA-9qp6-g7r6-cvp4
References
More GeoVision vulnerabilities
- TI-2024-10304 GeoVision EOL devices - OS Command Injection KEVCVSS 3.1CRITICAL 9.8
- TI-2024-05603 GeoVision EOL device - OS Command Injection KEVCVSS 3.1CRITICAL 9.8
- TI-2018-15344 GeoVision Command Injection RCE via /PictureCatch.cgi CVSS 4.0CRITICAL 10.0
- TI-2021-22411 GeoVision Geowebserver 5.3.3 - Local FIle Inclusion CVSS 4.0HIGH 8.7
- TI-2026-41681 GV-LPC2011/LPC2211 - unauthorized buffer overflow via RTSP Digest username (ssvr) CVSS 3.1CRITICAL 9.8
- TI-2026-41680 GV-LPC2011/LPC2211 - unauthorized buffer overflow via AuthMode/AuthValue path (ssvr) CVSS 3.1CRITICAL 9.8
Sources
- CVE-2026-57876 · CVE Program
- CVE-2026-57876 · NVD
- FIRST EPSS
- GHSA-9qp6-g7r6-cvp4 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences