dbcve.org
Tetra\Application · Midnightblue

CVE-2022-24401

HIGH · 8.1 CVSS v3.1 Published 2023-10-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Adversary-induced keystream re-use on TETRA air-interface encrypted traffic using any TEA keystream generator. IV generation is based upon several TDMA frame counters, which are frequently broadcast by the infrastructure in an unauthenticated manner. An active adversary can manipulate the view of these counters in a mobile station, provoking keystream re-use. By sending crafted messages to the MS and analyzing MS responses, keystream for arbitrary frames can be recovered.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

TETRA air-interface encryption uses TDMA frame counters to generate initialization vectors (IVs) for TEA keystream generation. These frame counters are broadcast unauthenticated, allowing an active attacker to manipulate the mobile station's view of these counters. This causes keystream re-use, enabling the attacker to recover keystream for arbitrary frames by sending crafted messages and analyzing responses.

MitigationImplement authenticated encryption for TDMA frame counter broadcasts or modify the IV generation scheme to include secret entropy that cannot be controlled by an external adversary. This may require firmware updates to TETRA infrastructure and mobile station equipment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tetra\Application
Affected:= burst

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Midnightblue Tetra equipment in your environment
    Inventory all TETRA radio infrastructure and mobile stations, specifically looking for Midnightblue Tetra devices. Check device labels, management interfaces, or network scans for 'Midnightblue' or 'TETRA' product identifiers.
    Affected if Any Midnightblue Tetra equipment is present in the environment
  2. Locate firmware or software version information
    Access the device management console, firmware update system, or maintenance records. Look for version strings or build numbers associated with the TETRA equipment.
    Affected if The installed version matches or predates any version where this vulnerability was addressed by the vendor
  3. Determine if frame counter broadcasts are unauthenticated
    Analyze network traffic or protocol documentation for TETRA air-interface communications. Inspect whether TDMA frame counter values are transmitted with cryptographic authentication or integrity protection.
    Affected if Frame counter values are transmitted in plaintext without authentication or integrity checks
  4. Check for indicators of keystream reuse
    Monitor TETRA traffic for repeated keystream patterns or analyze captured radio frames for identical keystream outputs when frame counter values should differ.
    Affected if Analysis reveals keystream reuse across different frames that should have unique IVs

You are affected if you deploy Midnightblue Tetra equipment and the frame counter broadcasts on your TETRA network lack authentication, allowing potential keystream reuse.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement authenticated encryption for TDMA frame counter broadcasts or modify the IV generation scheme to include secret entropy that cannot be controlled by an external adversary. This may require firmware updates to TETRA infrastructure and mobile station equipment.

Fix this in Tetra\ Scoped from the published advisory
  • Consultation16.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA12.0 h
92.0 hours of engineering $16,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $25,856.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24401 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24401 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data