# CVE-2023-26942: Weak cryptography in n/a

> Weak encryption in Yale IA-210 Alarm RFID tags allows attackers to clone tags via physical proximity, bypassing security controls.

- **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:** 4 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-v8rc-qj98-2pv7

## What is CVE-2023-26942?

CVE-2023-26942 is a medium-severity vulnerability in n/a, published on 4 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Weak encryption mechanisms in RFID Tags in Yale IA-210 Alarm v1.0 allows attackers to create a cloned tag via physical proximity to the original.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2023-26942?

It affects 1 product.


Products: Assaabloy Yale Ia-210 Firmware.

## How do I fix CVE-2023-26942?

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

## Is CVE-2023-26942 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26942 and fix it if it is affected.

What it is: CVE-2023-26942 is a medium-severity vulnerability in n/a, published on 4 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-26942 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-2023-26942/ (Markdown: https://insights.sbomify.com/CVE-2023-26942/index.md)
```

## Sources

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

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