Ebts Base Radio FirmwareOperating system · Motorola

CVE-2023-23773

HIGH · 8.8 CVSS v3.1 Published 2023-08-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Motorola EBTS/MBTS Base Radio fails to check firmware authenticity. The Motorola MBTS Base Radio lacks cryptographic signature validation for firmware update packages, allowing an authenticated attacker to gain arbitrary code execution, extract secret key material, and/or leave a persistent implant on the device.

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 confidence

The Motorola MBTS Base Radio does not perform cryptographic signature validation on firmware update packages, allowing an authenticated attacker to install malicious firmware. This enables arbitrary code execution, extraction of secret key material, and persistent implant installation.

MitigationImplement cryptographic signature validation for all firmware updates using a secure boot chain, ensuring only signed firmware from trusted sources can be loaded onto the device.

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
Ebts Base Radio FirmwareOperating system
Affected:= r05.x2.57
Mbts Base Radio FirmwareOperating system
Affected:= r05.x2.57

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the radio's administrative interface or CLI and retrieve the device model information. Look for 'Ebts Base Radio' or 'Mbts Base Radio' in the system information or device status.
    Affected if The device is not a Motorola Ebts or Mbts Base Radio, then this CVE does not apply.
  2. Check firmware version
    Execute the appropriate command or navigate to the firmware version display section in the device management interface. Common commands include 'show version', 'system info', or checking the firmware details page.
    Affected if The installed firmware version is exactly r05.x2.57, indicating the affected version.
  3. Verify firmware signature validation configuration
    Access the firmware update or secure boot configuration settings. Look for options related to 'firmware signature verification', 'secure boot', 'code signing', or 'update authentication'. Check whether signature validation is enabled or disabled.
    Affected if Firmware signature validation is disabled, not configured, or not available as an option in the update settings, indicating the vulnerability is present.
  4. Check firmware update mechanism
    Examine the firmware upload/update process in the device admin panel or CLI. Identify if there is any mechanism for verifying the authenticity of firmware files before installation.
    Affected if The device allows firmware updates without requiring cryptographic signature verification or trust chain validation, leaving the update process vulnerable to malicious firmware injection.

If the device is a Motorola Ebts or Mbts Base Radio running firmware version r05.x2.57 and firmware signature validation is not enabled or not enforced during the update process, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement cryptographic signature validation for all firmware updates using a secure boot chain, ensuring only signed firmware from trusted sources can be loaded onto the device.

Fix this in Ebts Base Radio Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA12.0 h
84.0 hours of engineering $14,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $23,296.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23773 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-23773 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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