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

> Attackers can perform man-in-the-middle attacks and decrypt traffic due to shared cryptographic keys in GeoVision door access devices.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-pqc7-3qg5-vwc6

## What is CVE-2020-3929?

CVE-2020-3929 is a medium-severity vulnerability in GeoVision Door Access Control Device, published on 12 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2020-3929?

It affects 5 products.


Products: Usavisionsys Geovision Gv-As1010 Firmware, Usavisionsys Geovision Gv-As210 Firmware, Usavisionsys Geovision Gv-As410 Firmware, Usavisionsys Geovision Gv-As810 Firmware, Usavisionsys Geovision Gv-Gf192x Firmware.

## How do I fix CVE-2020-3929?

No fix has been published for CVE-2020-3929 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-3929 being exploited?

There is no known exploitation of CVE-2020-3929 in the wild and no public exploit code.

## Other vulnerabilities in GeoVision Door Access Control Device

- [CVE-2020-3928](https://insights.sbomify.com/CVE-2020-3928/): GeoVision Door Access Control Device - Hardcoded privileged password (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-3929 and fix it if it is affected.

What it is: CVE-2020-3929 is a medium-severity vulnerability in GeoVision Door Access Control Device, published on 12 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-3929 in the wild and no public exploit code.

Affected product: GeoVision Door Access Control Device. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-3929/ (Markdown: https://insights.sbomify.com/CVE-2020-3929/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-3929
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-3929
- OSV: https://osv.dev/vulnerability/CVE-2020-3929

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-3929/
Summaries are generated and may contain mistakes; the official description above is the record.