HIGH 7.5

CVE-2026-57875: GeoVision Camera NULL Pointer Crash – Denial of Service Vulnerability

GeoVision's GV-LPC2011 and GV-LPC2211 network cameras running firmware V1.12 and earlier contain a flaw in how they handle incoming web requests. An attacker on the network can send a malformed HTTP request that causes the camera's web service to crash, temporarily taking the device offline. No authentication is required to trigger this issue, and the attacker doesn't gain access to data—the sole impact is service disruption.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses (CWE)
CWE-476
Affected products
0 configuration(s)
Published / Modified
2026-06-26 / 2026-06-26

NVD description (verbatim)

An unauthenticated NULL pointer dereference vulnerability exists in the HTTP request parsing logic of multiple CGI components in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability is caused by improper validation of required HTTP request metadata before it is used by the affected components. A remote attacker may exploit this vulnerability by sending a specially crafted HTTP request, causing the affected process to crash and resulting in a denial of service.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

The vulnerability is a NULL pointer dereference (CWE-476) in the HTTP request parsing logic of multiple CGI components within affected GeoVision devices. The root cause is insufficient validation of required HTTP request metadata before dereferencing pointers. When a specially crafted HTTP request arrives without proper metadata, the parsing routine attempts to access memory that has not been initialized or validated, triggering a crash of the affected process. The flaw is unauthenticated and requires no special privileges to exploit.

Business impact

Deployments of these GeoVision cameras in surveillance or monitoring roles will experience service outages if attacked. Organizations relying on continuous video feeds for security, facility monitoring, or compliance purposes face operational disruption and potential blind spots. The impact is availability-focused rather than confidentiality or integrity; no user data or system configuration is compromised by this vulnerability itself. However, repeated or sustained attacks could create a pattern of denial of service affecting business continuity.

Affected systems

GeoVision GV-LPC2011 and GV-LPC2211 network cameras running firmware version V1.12 and earlier are vulnerable. Later firmware versions are not mentioned in the advisory, implying updates may be available. Organizations should verify the exact firmware version installed on each device in their environment.

Exploitability

Exploitability is straightforward and does not require authentication, specialized network position, or user interaction. The attack vector is network-based, and the complexity is low—any remote attacker can send a malformed HTTP request to the camera's web service. The barrier to exploitation is minimal, making this vulnerability practically exploitable by any entity with network access to the affected devices. No public exploit code status is indicated, but the simplicity of the flaw suggests potential rapid weaponization if details become widely known.

Remediation

Firmware updates resolving this vulnerability are the primary remediation path. Organizations should contact GeoVision for guidance on available patches for their specific camera models and check the manufacturer's support portal for firmware version numbering and availability. Until patches are applied, network segmentation and access controls should restrict direct HTTP access to these cameras to trusted administrative networks only.

Patch guidance

Verify the current firmware version on each affected device through the camera's administrative interface. GeoVision firmware updates are typically applied through the device's web interface or management platform. Consult the vendor's official advisory and release notes to identify which firmware version resolves CVE-2026-57875 and confirm compatibility with your deployment. Test updates in a non-production environment first, as firmware changes can affect video streaming or integration with existing systems. Document the update process and maintain backups of current configurations before upgrading.

Detection guidance

Monitor for HTTP requests sent to affected cameras that contain malformed or missing required metadata fields in the HTTP header. Look for log entries showing CGI process crashes or unexpected restarts on these devices. Network-based detection could involve analyzing HTTP traffic for requests lacking standard headers (Host, User-Agent, Content-Length, etc.) sent to the camera's web service. Endpoint detection on the camera itself—if available—should flag process crashes in the web service daemon. Correlate any service restarts with external network activity to identify attack attempts.

Why prioritize this

This vulnerability scores 7.5 CVSS (HIGH) due to its network accessibility, lack of authentication requirement, and direct denial of service impact on availability. While not listed on the CISA Known Exploited Vulnerabilities catalog, the straightforward nature of NULL pointer dereference exploits and the public disclosure merit treating this as a near-term security concern. Organizations with internet-facing GeoVision cameras or cameras in untrusted network segments should prioritize patching. Even cameras on internal networks face risk from insider threats or lateral movement by compromised systems.

Risk score, explained

The CVSS 3.1 score of 7.5 (HIGH) reflects: network accessibility (AV:N) allows remote exploitation without physical access; low attack complexity (AC:L) means standard tools and methods suffice; no authentication (PR:N) or user interaction (UI:N) is required; the scope is unchanged (S:U), limiting blast radius; and high availability impact (A:H) results from process crashes. The lack of confidentiality or integrity impact (C:N, I:N) prevents a critical rating, but the ease of exploitation and direct service disruption justify the HIGH severity designation.

Frequently asked questions

Are GeoVision cameras with this vulnerability at immediate risk if they're on an internal network?

Internal network placement reduces but does not eliminate risk. Compromised systems on the same network, malicious employees, or attackers who gain lateral access can still exploit the vulnerability. For cameras containing sensitive monitoring footage or supporting critical operations, patching remains important regardless of network location.

Can this vulnerability allow an attacker to access recorded video or change camera settings?

No. This specific vulnerability only causes the web service to crash, resulting in temporary unavailability. It does not bypass authentication, expose data, or modify configuration. However, the denial of service could blind your surveillance during an attack, so this should not be viewed as a low-impact flaw in a security-sensitive environment.

How can we quickly assess exposure if we have dozens of these cameras deployed?

Inventory your GeoVision cameras and document their model and firmware versions. Most organizations can query this via the management interface or API if one is in use. Cross-reference against the vendor advisory to identify which units run V1.12 or earlier. Prioritize patching cameras exposed to the internet or in high-security zones first, then work through internal deployments.

What should we do if we cannot update immediately?

Implement network access controls to restrict HTTP and HTTPS traffic to affected cameras to trusted administrative subnets only. Use firewall rules, VLANs, or access control lists to prevent untrusted sources from reaching the camera's web service. Monitor camera availability and process restarts for signs of attack. Coordinate with GeoVision support on patch availability timelines and any interim workarounds they may offer.

This analysis is based on the published CVE record as of the date provided. Vendors and affected product information were not included in the source data; verify current patch status and product applicability directly with GeoVision's official advisory and support channels. CVSS scores and severity ratings reflect the CVSS 3.1 standard and are subject to interpretation based on organizational context. This document is for informational purposes and should not be construed as professional security or legal advice. Organizations must conduct their own risk assessments and testing before deploying patches in production environments. Source: NVD (public-domain), retrieved 2026-08-04. Analysis generated by SEC.co (claude-haiku-4-5).