# CVE-2022-45914: Missing authorization in n/a

> Attackers can modify electronic shelf label data via unauthenticated RF signals, impacting retail pricing and inventory organization.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-mp8x-36fv-pwv3

## What is CVE-2022-45914?

CVE-2022-45914 is a medium-severity missing authorization vulnerability in n/a, published on 27 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ESL (Electronic Shelf Label) protocol, as implemented by (for example) the OV80e934802 RF transceiver on the ETAG-2130-V4.3 20190629 board, does not use authentication, which allows attackers to change label values via 433 MHz RF signals, as demonstrated by disrupting the organization of a hospital storage unit, or changing retail pricing.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2022-45914?

It affects 1 product.


Products: Electronic Shelf Label Protocol Project Electronic Shelf Label Protocol.

## How do I fix CVE-2022-45914?

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

## Is CVE-2022-45914 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45914 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45914 and fix it if it is affected.

What it is: CVE-2022-45914 is a medium-severity missing authorization vulnerability in n/a, published on 27 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45914 exists.

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-2022-45914/ (Markdown: https://insights.sbomify.com/CVE-2022-45914/index.md)
```

## Sources

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

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