LiveActive security incident?Get immediate response
CVE Record

CVE-2023-23119: The use of the cyclic redundancy check (CRC) algorithm for integrity check during firmware update makes Ubi...

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.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some Ubiquiti airFiber AF2X radios may accept modified firmware during updates because CRC is not a secure integrity check. The business risk is unauthorized firmware alteration if an attacker can intercept the update path. Public sources do not show active exploitation or a named patch in the provided bundle.

Executive priority

Prioritize identification and controlled updating of affected AF2X radios, but do not treat this as an internet-wide emergency based on the supplied evidence. Urgency rises where radios are operationally critical or updates occur over networks that could be intercepted.

Technical view

CVE-2023-23119 is a CWE-354 firmware integrity weakness affecting Ubiquiti airFiber AF2X Radio firmware 3.2.2 and earlier. A network MITM can modify a firmware image and bypass checksum verification because CRC is used for integrity. CVSS is 5.9 with high attack complexity and high integrity impact.

Likely exposure

Exposure appears limited to Ubiquiti airFiber AF2X Radio devices running firmware 3.2.2 or earlier, especially where firmware updates traverse networks an attacker could intercept. The provided CVE affected-product metadata is incomplete and lists vendor/product as n/a.

Exploitation context

The CVE description supports a MITM firmware-modification scenario, not remote takeover by itself. CISA KEV status is false in the bundle, and no cited source states active exploitation. Practical exploitation likely requires control or interception of the firmware update path.

Researcher notes

The core issue is insecure integrity verification, not a disclosed payload or public exploit path. The source bundle lacks a complete CPE list and does not name a fixed version. Validation should focus on version exposure, update-channel trust, and vendor release confirmation.

Mitigation direction

  • Inventory Ubiquiti airFiber AF2X radios and record firmware versions.
  • Check Ubiquiti security releases for vendor-confirmed fixed firmware or guidance.
  • Avoid firmware updates over untrusted or interceptable network paths.
  • Use only firmware sources and update mechanisms approved by the vendor.
  • Treat unknown firmware provenance as a change-control exception.

Validation and detection

  • Confirm whether any AF2X radios run firmware 3.2.2 or earlier.
  • Review how firmware images are obtained, transported, and applied.
  • Check vendor release notes for a referenced fix or mitigation.
  • Verify update workflows prevent untrusted network interception.
  • Document any AF2X devices awaiting vendor guidance or upgrade.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-354: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-23119 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2023-23119Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-354 · source CWE mapping

Improper Validation of Integrity Check Value

Improper Validation of Integrity Check Value represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.