CVE-2023-0888
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 · uneditedAn improper neutralization of directives in dynamically evaluated code vulnerability in the WiFi Battery embedded web server in versions L90/U70 and L92/U92 can be used to gain administrative access to the WiFi communication module. An authenticated user, having access to both the medical device WiFi network (such as a biomedical engineering staff member) and the specific B.Braun Battery Pack SP with WiFi web server credentials, could get administrative (root) access on the infusion pump communication module. This could be used as a vector to start further attacks
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 confidenceImproper neutralization of directives in dynamically evaluated code in the embedded web server of WiFi Battery packs (versions L90/U70 and L92/U92) used with B.Braun infusion pumps allows an authenticated attacker to inject and execute arbitrary code, achieving root administrative access to the WiFi communication module.
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<= 053l000092<= 054u000092CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 the battery pack modelLocate the physical device or check inventory/documentation for the WiFi Battery Pack model number - look for L90, U70, L92, or U92 designationsAffected if The device model is L90, U70, L92, or U92 (these are the affected models)
-
Check the installed firmware versionAccess the embedded web server on the WiFi module (typically via HTTP/HTTPS on the device IP) and navigate to the system information or firmware version page; alternatively, consult device management interfaces or B.Braun documentation for version retrieval methodsAffected if Firmware version is 053l000092 or earlier, OR 054u000092 or earlier (versions with 'l' or 'u' prefix followed by 000092 or lower)
-
Verify the web server is accessibleAttempt to reach the device web interface by accessing its IP address on common web ports (80, 443, 8080) from within your networkAffected if The web interface is reachable over the network - this indicates the attack surface is present
-
Confirm authentication is configuredCheck whether the web interface requires authentication or if default/admin credentials are in use; review access control settings for the WiFi moduleAffected if The web interface permits authentication (even with default credentials) - this is required for the authenticated attack vector to apply
You are affected if you have a WiFi Battery Pack model L90/U70 or L92/U92 with firmware version 053l000092 or lower (for L90/U70) or 054u000092 or lower (for L92/U92), and the embedded web server is 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 dataRestrict network access to the WiFi module through network segmentation, implement strict access controls, and apply vendor-provided firmware updates when available. Consider disabling the web interface if not operationally essential.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0888 — 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-2023-0888 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