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

> Attackers can clone RFID tags due to missing encryption, allowing them to disarm the Hozard alarm system via physical proximity.

- **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:** 11 Jan 2024
- **Updated:** 3 Jun 2025
- **Also known as:** GHSA-4p3v-q232-wxm8

## What is CVE-2023-50126?

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

### Official description

Missing encryption in the RFID tags of the Hozard alarm system (Alarmsysteem) v1.0 allow attackers to create a cloned tag via brief physical proximity to one of the original tags, which results in an attacker being able to bring the alarm system to a disarmed state.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 1 product.


Products: Hozard Alarm System.

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

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

## Is CVE-2023-50126 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-50123](https://insights.sbomify.com/CVE-2023-50123/): Auth bypass in n/a (high 8.1)
- [CVE-2023-50125](https://insights.sbomify.com/CVE-2023-50125/): Hardcoded credentials in n/a (medium 5.9)
- [CVE-2023-50127](https://insights.sbomify.com/CVE-2023-50127/): Auth bypass in n/a (medium 5.9)
- [CVE-2023-50128](https://insights.sbomify.com/CVE-2023-50128/): Security feature bypass in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50126 is a medium-severity vulnerability in n/a, published on 11 Jan 2024. 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-50126 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-50126/ (Markdown: https://insights.sbomify.com/CVE-2023-50126/index.md)
```

## Sources

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

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