# CVE-2023-23119: Security feature bypass in n/a

> An attacker can bypass firmware integrity checks via MITM to install malicious firmware on Ubiquiti airFiber radios.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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:** 2 Feb 2023
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-c4v2-98hc-pvh9

## What is CVE-2023-23119?

CVE-2023-23119 is a medium-severity vulnerability in n/a, published on 2 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The use of the cyclic redundancy check (CRC) algorithm for integrity check during firmware update makes Ubiquiti airFiber AF2X Radio firmware version 3.2.2 and earlier vulnerable to firmware modification attacks. An attacker can conduct a man-in-the-middle (MITM) attack to modify the new firmware image and bypass the checksum verification.

Weakness: CWE-354 (Improper Validation of Integrity Check Value)

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

It affects 1 product.


Products: Ui Af-2x Firmware.

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

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

## Is CVE-2023-23119 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-23119 is a medium-severity vulnerability in n/a, published on 2 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-23119 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-2023-23119/ (Markdown: https://insights.sbomify.com/CVE-2023-23119/index.md)
```

## Sources

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

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