Device tampering via improperly verified firmware updates
Published Apr 14, 2022 · Updated Apr 16, 2025
Improper firmware signature verification in affected B. Braun communication devices allows physically proximate attackers to tamper with them. The firmware update verifier accepts attacker-generated update packages containing arbitrary content as cryptographically valid. Physical access and a high-complexity update operation are required; successful installation can replace trusted firmware content and tamper with device operation.
Summary
What happened
Improper firmware signature verification in affected B. Braun communication devices allows physically proximate attackers to tamper with them. The firmware update verifier accepts attacker-generated update packages containing arbitrary content as cryptographically valid. Physical access and a high-complexity update operation are required; successful installation can replace trusted firmware content and tamper with device operation.
The record
- CVE
- CVE-2020-25166
- Published
- Apr 14, 2022
- Updated
- Apr 16, 2025
- Vendor
- B. Braun Melsungen AG
- Product
- Battery-Pack SP with WiFi
- Classifications
- CWE-347, T1601
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 14, 2022CVE publishedPublication date reported by the CVE source.
- Apr 16, 2025Record 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=unspecified <=L81
- Affected versionversion=unspecified <=U61
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