CVE-2022-24400
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 · uneditedA flaw in the TETRA authentication procecure allows a MITM adversary that can predict the MS challenge RAND2 to set session key DCK to zero.
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 · moderate confidenceA vulnerability in the TETRA (Terrestrial Trunked Radio) authentication procedure allows a man-in-the-middle attacker who can predict the mobile station challenge RAND2 to set the derived cipher key (DCK) to zero, effectively neutralizing encryption for the session.
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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/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 modelReview network infrastructure documentation or physically inspect TETRA base stations and terminals to confirm vendor is Midnightblue Tetra and model is 'burst'Affected if Using Midnightblue Tetra burst equipment for TETRA communications
-
Verify RAND2 generation mechanismExamine authentication logs or capture network traffic during authentication handshake to observe if the mobile station challenge RAND2 follows predictable patterns or repeats across sessionsAffected if RAND2 values are predictable, repeating, or showing low entropy across multiple authentication attempts
-
Inspect cipher key derivation outputCapture or log the derived cipher key (DCK) values generated during authentication sessions and verify if any sessions produce a zero-valued DCKAffected if Any session produces DCK equal to zero or uses a weak/null key derivation function
-
Check authentication configurationReview TETRA device configuration settings for authentication parameters, specifically looking for legacy or reduced security modes that may allow weak key derivationAffected if Device is configured with vulnerable authentication mode or uses weak random number generation for RAND2
Affected if using Midnightblue Tetra burst equipment where RAND2 can be predicted and DCK may be set to zero, neutralizing session encryption
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 dataUpdate TETRA infrastructure and devices with vendor patches that implement improved random number generation for RAND2 and strengthen the key derivation function to prevent predictable or zero-valued session keys.
- 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-24400 — 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-24400 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