CVE-2022-24404
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 · uneditedLack of cryptographic integrity check on TETRA air-interface encrypted traffic. Since a stream cipher is employed, this allows an active adversary to manipulate cleartext data in a bit-by-bit fashion.
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 (Terrestrial Trunked Radio) air-interface protocol lacks cryptographic integrity verification for encrypted traffic. Because a stream cipher is used without an associated message authentication code (MAC), an active attacker can perform bit-flipping attacks: by XORing a chosen bit in the ciphertext at a known position, the corresponding bit in the decrypted plaintext flips predictably, allowing manipulation of cleartext data without detection.
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 Midnightblue Tetra installationLocate the Midnightblue Tetra software package on your system. Check installed packages, firmware, or application inventory for 'midnightblue' or 'tetra' components.Affected if The software is present and matches the 'burst' version or falls within the Midnightblue Tetra product line.
-
Verify TETRA air-interface protocol is activeConfirm that the TETRA (Terrestrial Trunked Radio) air-interface protocol is enabled and processing traffic. Check running services, radio configurations, or network interfaces handling TETRA communications.Affected if TETRA air-interface protocol is actively processing encrypted radio traffic.
-
Inspect encryption cipher mode configurationExamine the cryptographic configuration for TETRA traffic. Look for stream cipher settings in the radio/software configuration files or management interface. Check if AES-CTR, AES-CBC, or other stream cipher modes are in use without integrity verification.Affected if A stream cipher (such as AES in CTR mode or similar) is configured for TETRA traffic without an associated MAC or authenticated encryption mode.
-
Check for integrity verification mechanismReview the security configuration to determine if MAC, HMAC, or authenticated encryption (AES-GCM, AES-CCM) is implemented for TETRA traffic integrity. Inspect cryptographic policy settings or protocol parameters.Affected if No MAC, HMAC, or authenticated encryption mode is present for the TETRA air-interface encrypted traffic.
You are affected if Midnightblue Tetra 'burst' version is in use and the TETRA air-interface is configured with a stream cipher lacking cryptographic integrity verification (no MAC or authenticated 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 dataImplement authenticated encryption (e.g., AES in GCM mode or AES-CCM) or add a cryptographic integrity mechanism (MAC/HMAC) to TETRA air-interface traffic to detect tampering. Until firmware updates are available, consider network segmentation and physical security to reduce attack surface.
- 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-24404 — 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-24404 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