CVE-2022-24402
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 · uneditedThe TETRA TEA1 keystream generator implements a key register initialization function that compresses the 80-bit key to only 32 bits for usage during the keystream generation phase, which is insufficient to safeguard against exhaustive search attacks.
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 confidenceThe TETRA TEA1 keystream generator contains a cryptographic weakness where the 80-bit secret key is compressed to just 32 bits during keystream generation. This dramatically reduces the effective keyspace from 2^80 to 2^32, enabling exhaustive search (brute-force) attacks to recover the keystream and potentially decrypt communications.
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= burstCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify TETRA equipment vendor and product lineInventory your radio/communication infrastructure to determine if any equipment uses the TETRA (Terrestrial Trunked Radio) standard. Check vendor documentation or device firmware strings for 'Midnightblue Tetra' branding.Affected if The organization deploys Midnightblue Tetra devices.
-
Determine the specific software versionAccess the device management interface or firmware metadata and locate the version identifier. Compare against the 'burst' version designation noted in the affected products.Affected if The installed version is Midnightblue Tetra burst.
-
Verify TEA1 cipher is activeInspect the device encryption or cipher configuration settings. Look for 'TEA1' or 'TEA' as the selected stream cipher algorithm in the encryption parameters.Affected if TEA1 is selected as the active keystream generator.
-
Check key configuration parametersReview the key management settings or cryptographic configuration for the encryption channel. Verify whether the 80-bit master key is being used directly or processed through the vulnerable compression mechanism.Affected if The device uses TEA1 with standard key processing (no additional entropy padding or key expansion).
You are affected if your TETRA deployment uses Midnightblue Tetra burst version with TEA1 cipher enabled and standard key handling.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace TEA1 with a cryptographically stronger algorithm or implement additional security layers (such as frequency hopping, encryption overlays, or protocol-level authentication) to compensate for the reduced key entropy. Organizations should audit TETRA deployments and consult with equipment vendors for firmware updates or alternative cipher options.
- Consultation16.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA12.0 h
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 locallyCheck whether your project pulls in CVE-2022-24402 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24402 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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