Authenticated code execution via unsigned firmware updates
Published Aug 29, 2023 · Updated Oct 1, 2024
Firmware authentication failure in Motorola EBTS/MBTS Base Radio R05.x2.57 allows remote authenticated users to execute arbitrary code. The firmware update path installs packages without validating a cryptographic signature, allowing attacker-supplied images to run as device firmware. Access to the authenticated update interface is required; successful exploitation permits secret-key extraction and a persistent implant.
Summary
What happened
Firmware authentication failure in Motorola EBTS/MBTS Base Radio R05.x2.57 allows remote authenticated users to execute arbitrary code. The firmware update path installs packages without validating a cryptographic signature, allowing attacker-supplied images to run as device firmware. Access to the authenticated update interface is required; successful exploitation permits secret-key extraction and a persistent implant.
The record
- CVE
- CVE-2023-23773
- Published
- Aug 29, 2023
- Updated
- Oct 1, 2024
- Vendor
- Motorola Solutions
- Product
- EBTS/MBTS Base Radio
- Classifications
- CWE-347, CAPEC-475, CAPEC-463, T1601
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 29, 2023CVE publishedPublication date reported by the CVE source.
- Oct 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=r05.x2.57
- Affected versionversion=R05.x2.57
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo