LiveActive security incident?Get immediate response
CVE Record

CVE-2020-3929: GeoVision Door Access Control Device - Shared cryptographic keys

GeoVision Door Access Control device family employs shared cryptographic private keys for SSH and HTTPS. Attackers may conduct MITM attack with the derived keys and plaintext recover of encrypted messages.

MediumCVSS 5.9Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some GeoVision door access controllers were reported to ship with shared private keys for SSH and HTTPS. If an attacker can intercept device communications and derive those keys, encrypted traffic could be exposed. The main business risk is confidentiality loss around access-control administration, not direct denial of service or code execution based on the provided sources.

Executive priority

Treat this as a moderate-risk infrastructure confidentiality issue. Prioritize sites where these controllers protect sensitive facilities or expose management traffic beyond a tightly controlled network.

Technical view

CVE-2020-3929 affects GeoVision GV-AS210, GV-AS410, GV-AS810, GV-GF192x, and GV-AS1010 devices. The issue is shared cryptographic private keys used for SSH and HTTPS, enabling potential man-in-the-middle decryption or plaintext recovery. CVSS 3.1 is 5.9, network attack vector, high attack complexity, no privileges or user interaction, confidentiality high impact only.

Likely exposure

Exposure is most relevant where affected GeoVision door access controllers are deployed and SSH or HTTPS management traffic crosses untrusted or shared networks. Internet-exposed management interfaces increase concern.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. Exploitation would require a favorable network position for man-in-the-middle interception and access to derived shared keys.

Researcher notes

Evidence is limited to the CVE description, affected model list, CVSS metadata, and TWCERT reference. No CWE, patch version, exploit code, or active exploitation evidence is provided in the bundle.

Mitigation direction

  • Inventory deployments of the affected GeoVision models.
  • Restrict SSH and HTTPS management access to trusted administrative networks or VPNs.
  • Remove management interfaces from direct internet exposure.
  • Check GeoVision and TWCERT guidance for firmware, key replacement, or device-specific remediation.
  • Consider replacement where unique key material cannot be confirmed or remediated.

Validation and detection

  • Identify affected models in physical access-control environments.
  • Confirm whether SSH or HTTPS management is enabled on each device.
  • Check whether management interfaces are reachable from untrusted networks.
  • Compare owned-device SSH and HTTPS key fingerprints for unintended sharing.
  • Review vendor advisories for updated remediation status.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-3929 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2020-3929Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GeoVisionDoor Access Control DeviceGV-AS210, GV-AS410, GV-AS810, GV-GF192x, GV-AS1010Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.