CVE-2022-26943
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 Motorola MTM5000 series firmwares generate TETRA authentication challenges using a PRNG using a tick count register as its sole entropy source. Low boottime entropy and limited re-seeding of the pool renders the authentication challenge vulnerable to two attacks. First, due to the limited boottime pool entropy, an adversary can derive the contents of the entropy pool by an exhaustive search of possible values, based on an observed authentication challenge. Second, an adversary can use knowledge of the entropy pool to predict authentication challenges. As such, the unit is vulnerable to CVE-2022-24400.
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 Motorola MTM5000 series TETRA radio firmware uses a pseudo-random number generator (PRNG) that relies solely on a tick count register for entropy, resulting in insufficient randomness at boot time. This weak entropy allows an attacker to perform exhaustive search attacks to recover the entropy pool from observed authentication challenges and subsequently predict future authentication challenges, enabling impersonation attacks.
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 dataall versionsall versionsCVSS 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
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Motorola radio modelLocate the physical device or check inventory/documentation for Motorola Mtm5500 or Mtm5400 TETRA radios in your environmentAffected if Device model is Motorola Mtm5500 or Mtm5400 - all firmware versions are affected
-
Confirm firmware versionAccess the radio's management interface or check device documentation to retrieve the firmware version numberAffected if Any firmware version is present on Mtm5500 or Mtm5400 models - all versions are affected according to vendor advisory
-
Check network accessibility of radio management interfacesReview network segmentation and firewall rules to determine if the radio's authentication and management interfaces are reachable from network segmentsAffected if Radio management or authentication interfaces are accessible from network - this exposes the device to attack vectors described in the CVE
-
Audit authentication logs for pattern anomaliesIf logs are available from the radio or associated authentication systems, examine for repeated authentication challenges or unexpected patterns that could indicate enumeration or prediction attemptsAffected if Authentication challenges appear predictable or repeatable when observed over time - this is the symptom of the weak PRNG vulnerability
-
Verify entropy source configuration if accessibleIf the radio firmware exposes configuration or diagnostic interfaces, check whether the PRNG configuration indicates use of tick count or similar low-entropy sources versus cryptographically secure sourcesAffected if PRNG uses tick count register or similar low-entropy source without additional entropy mixing - confirms the vulnerability condition
Your environment is affected if you have Motorola Mtm5500 or Mtm5400 TETRA radios running any firmware version, especially if their management interfaces are network-accessible.
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 to firmware version that implements a cryptographically secure PRNG (CSPRNG) with proper entropy sources and reseeding mechanisms. Until a patch is available, monitor for unauthorized access attempts and consider network-level controls.
- Consultation12.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26943 — 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-26943 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