# CVE-2020-36283: Cross-site request forgery in n/a

> Remote attackers can exploit CSRF in HID OMNIKEY readers using EEM driver to upload malicious configuration files, potentially leading to further attacks.

- **Severity:** Critical 9.6 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3f7c-f4gm-hmv7

## What is CVE-2020-36283?

CVE-2020-36283 is a critical vulnerability in n/a, published on 24 Mar 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

HID OMNIKEY 5427 and OMNIKEY 5127 readers are vulnerable to CSRF when using the EEM driver (Ethernet Emulation Mode). By persuading an authenticated user to visit a malicious Web site, a remote attacker could send a malformed HTTP request to upload a configuration file to the device. An attacker could exploit this vulnerability to perform cross-site scripting attacks, Web cache poisoning, and other malicious activities.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 2 products.


Products: Hidglobal Omnikey 5127 Firmware, Hidglobal Omnikey 5427 Firmware.

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

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

## Is CVE-2020-36283 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36283 is a critical vulnerability in n/a, published on 24 Mar 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-36283 in the wild and no public exploit code.

Affected product: n/a. 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-36283/ (Markdown: https://insights.sbomify.com/CVE-2020-36283/index.md)
```

## Sources

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

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