dbcve.org
Geovision Gv As210 FirmwareOperating system · Usavisionsys

CVE-2020-3928

CRITICAL · 9.8 CVSS v3.1 Published 2020-06-12
Fix available
A fix is available. Upgrade to 1.10 / 1.32 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
GeoVision Door Access Control device family is hardcoded with a root password, which adopting an identical password in all devices.

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

GeoVision Door Access Control devices contain a hardcoded root password embedded in firmware that is identical across all units. An attacker with network access can use these static credentials to authenticate as root, gaining full administrative control over the access control system including the ability to unlock doors, modify user permissions, and access audit logs.

MitigationImmediately change the default root password on all affected devices to a unique, strong password and contact GeoVision for a firmware update that removes the hardcoded credentials. Implement network segmentation and firewall rules to restrict unauthorized access to management interfaces.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Geovision Gv As210 FirmwareOperating system
Affected:< 2.21
Geovision Gv As410 FirmwareOperating system
Affected:< 2.21
Geovision Gv As810 FirmwareOperating system
Affected:< 2.21
Geovision Gv As1010 FirmwareOperating system
Affected:< 1.32
Geovision Gv Gf192x FirmwareOperating system
Affected:< 1.10

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 web interface or check the physical device label to confirm the exact model number (GV-AS210, GV-AS410, GV-AS810, GV-AS1010, or GV-GF192x)
    Affected if The device model is one of the five listed in the affected products
  2. Check the installed firmware version
    Log into the device web interface and navigate to the System Information or Firmware version page. Compare the displayed version against the affected ranges: AS210/AS410/AS810 < 2.21, AS1010 < 1.32, GF192x < 1.10
    Affected if The firmware version is below the specified threshold for your model
  3. Verify if the default root password is still in use
    Attempt to access the device via SSH or the web management interface using the default root account. If authentication succeeds without the password having been changed, the hardcoded credentials are still active
    Affected if The default root password has not been changed from the factory setting
  4. Assess network exposure of the management interface
    Check firewall rules and network configuration to determine if the device management interface (HTTP/HTTPS/SSH ports) is accessible from untrusted networks or the internet
    Affected if The management interface is exposed to untrusted networks without proper access controls

You are affected if you own one of the listed models with a firmware version below the threshold AND the default root password has not been changed from the hardcoded factory value.

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
Upgrade available Upgrade to 1.10 / 1.32 / 2.21 or later
Fixed in 1.101.322.21
Interim mitigation

Immediately change the default root password on all affected devices to a unique, strong password and contact GeoVision for a firmware update that removes the hardcoded credentials. Implement network segmentation and firewall rules to restrict unauthorized access to management interfaces.

Recommended fix High confidence

Firmware 2.21 (for As210/As410/As810), 1.32 (for As1010), 1.10 (for Gf192x)

  1. 1. Identify the exact model of the Geovision device from the affected product list (Gv As210, As410, As810, As1010, or Gf192x)
  2. 2. Download the latest firmware from Geovision's official website or contact their support
  3. 3. For Gv As210, As410, As810: upgrade to firmware version 2.21 or later
  4. 4. For Gv As1010: upgrade to firmware version 1.32 or later
  5. 5. For Gv Gf192x: upgrade to firmware version 1.10 or later
  6. 6. After upgrading, immediately change the default root password to a strong, unique password
  7. 7. Verify the new password works and the hardcoded credential no longer provides access
Caveat Review release notes for any configuration changes or feature modifications before upgrading production devices

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

Fix this in Geovision Gv As210 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3928 — 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-2020-3928 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