dbcve.org
NULL Pointer DereferenceWeakness · CWE-476

CVE-2026-57873

HIGH · 7.5 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An unauthenticated NULL pointer dereference vulnerability exists in IEEE8021x_upload.cgi in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability is caused by improper validation of multipart upload headers when processing certificate-related upload fields. A remote attacker may exploit this vulnerability by sending a malformed multipart request, causing the affected CGI process to crash and resulting in a denial of service.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An unauthenticated NULL pointer dereference exists in IEEE8021x_upload.cgi on GeoVision GV-LPC2011 and GV-LPC2211 devices (V1.12 and earlier). The vulnerability stems from improper validation of multipart upload headers when processing certificate-related upload fields, allowing a remote attacker to crash the CGI process via malformed multipart requests.

MitigationApply vendor firmware update if available; otherwise restrict network access to the device's web interface via firewall or VLAN segmentation to prevent unauthenticated requests from reaching the CGI endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device's web interface or check the device label/documentation to confirm it is a GeoVision GV-LPC2011 or GV-LPC2211 model. If using a different GeoVision model, this specific CVE does not apply.
    Affected if The device is NOT a GV-LPC2011 or GV-LPC2211 model.
  2. Check the firmware version
    Log into the device web interface and navigate to the system or firmware information page, or use the device's CLI/management interface to retrieve the firmware version. Compare it to V1.12.
    Affected if The firmware version is V1.12 or earlier (including V1.11, V1.10, etc.). Versions newer than V1.12 are not affected.
  3. Verify the IEEE8021x_upload.cgi endpoint exists
    Attempt to access the CGI script directly via HTTP/HTTPS by navigating to the URL path /cgi-bin/IEEE8021x_upload.cgi (or the equivalent path on the device). A 404 response indicates the endpoint may not be present or has been renamed.
    Affected if The IEEE8021x_upload.cgi endpoint is accessible and responds to requests.
  4. Assess network exposure of the web interface
    Determine whether the device's web management interface (port 80/443) is reachable from untrusted networks, such as the public internet or adjacent network segments without firewall filtering. Check firewall rules, VLAN configurations, or NAT settings.
    Affected if The web interface is exposed to networks where unauthenticated attackers can send requests directly to the device.

The device is affected if it is a GeoVision GV-LPC2011 or GV-LPC2211 running firmware V1.12 or earlier, the IEEE8021x_upload.cgi endpoint is present, and the web interface is reachable by unauthenticated network attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware update if available; otherwise restrict network access to the device's web interface via firewall or VLAN segmentation to prevent unauthenticated requests from reaching the CGI endpoint.

Recommended fix Moderate confidence

Firmware version newer than V1.12 (check GeoVision website for the specific fixed release)

  1. 1. Identify the current firmware version of the GeoVision GV-LPC2011 or GV-LPC2211 device by accessing the device's web interface or admin panel.
  2. 2. Navigate to the device settings or firmware upgrade section in the web interface.
  3. 3. Check GeoVision's official support website (www.geovision.com.tw) for the latest firmware version for your device model.
  4. 4. Download the firmware update file from the official GeoVision website.
  5. 5. Follow GeoVision's firmware upgrade instructions to apply the update, ensuring stable power during the process.
  6. 6. After upgrading, verify the new firmware version and test that the IEEE8021x_upload.cgi functionality works correctly.
  7. 7. Confirm the vulnerability is no longer present by ensuring the device no longer crashes when processing multipart upload requests to IEEE8021x_upload.cgi.
Caveat Standard firmware upgrade risks apply - ensure backup of configuration and stable power during update; review release notes for any configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57873 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57873 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data