GeoVision GV-LPCLPC2011/GV-LPCLPC2211 up to 1.12 ssvr stack-based overflow

Summaryinfo

A vulnerability marked as critical has been reported in GeoVision GV-LPCLPC2011 and GV-LPCLPC2211 up to 1.12. Affected by this issue is some unknown functionality of the component ssvr. Performing a manipulation results in stack-based overflow. This vulnerability was named CVE-2026-57879. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as very critical, was found in GeoVision GV-LPCLPC2011 and GV-LPCLPC2211 up to 1.12. This affects an unknown code of the component ssvr. The manipulation with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

An unauthenticated stack-based buffer overflow vulnerability exists in ssvr in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability is caused by insufficient bounds checking when processing RTSP custom authentication data. A remote attacker may exploit this vulnerability by sending a crafted RTSP request, resulting in memory corruption, denial of service, or potentially arbitrary code execution.

The weakness was presented by Le Yu and Jincheng Wang. The advisory is shared at geovision.com.tw. This vulnerability is uniquely identified as CVE-2026-57879 since 06/26/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/26/2026).

Upgrading to version 1.13 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• GeoVision

Name

• GV-LPCLPC2011
• GV-LPCLPC2211

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion