Midnightblue develops the Tetra communications platform, a focused product line where disclosed vulnerabilities cluster around authentication and integrity-validation weaknesses, including authorization bypass mechanisms, excessive authentication-attempt handling, and integrity-check validation issues. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Midnightblue over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2022-24404HIGH Lack 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 | Oct 19, 2023 | 7.5 | 22 | NO | NO |
CVE-2022-24402HIGH The 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, | Oct 19, 2023 | 7.5 | 22 | NO | NO |
CVE-2022-24401HIGH 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 fr | Oct 19, 2023 | 8.1 | 20 | NO | NO |
CVE-2022-24400MEDIUM A flaw in the TETRA authentication procecure allows a MITM adversary that can predict the MS challenge RAND2 to set session key DCK to zero. | Oct 19, 2023 | 5.9 | 18 | NO | NO |
CVE-2022-24403MEDIUM The TETRA TA61 identity encryption function internally uses a 64-bit value derived exclusively from the SCK (Class 2 networks) or CCK (Class 3 networks). The structure of TA61 allo | Dec 5, 2023 | 4.3 | 15 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Midnightblue.
Media articles that mention a CVE ID that affects a product developed by Midnightblue — matched by CVE ID, not by vendor name.