CVE-2021-33843
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 · uneditedFresenius Kabi Agilia SP MC WiFi vD25 and prior has a default configuration page accessible without authentication. An attacker may use this functionality to change the exposed configuration values such as network settings.
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 Fresenius Kabi Agilia SP MC WiFi vD25 and prior infusion pump contains a configuration page accessible without any authentication. This allows any attacker on the network to access the device's configuration interface and modify network settings such as IP configuration, potentially disrupting infusion pump operations or enabling further network-based 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 data<= d25CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 Fresenius Kabi Agilia SP MC WiFi devices on the networkScan the network for devices matching the Fresenius Kabi Agilia SP MC WiFi infusion pump by checking DHCP leases, MAC vendor prefixes, or conducting a banner grab on common management ports (80, 443, 8080). Review network device inventories for these specific infusion pump models.Affected if A Fresenius Kabi Agilia SP MC WiFi infusion pump is present on the network.
-
Confirm the firmware versionAccess the device's web interface or administrative console and navigate to the system information or firmware version page. Alternatively, if SNMP is enabled, query the device using the system description OID. Compare the firmware version to the affected range: version d25 or earlier.Affected if The device firmware version is d25 or any version prior to d25.
-
Test for unauthenticated access to the configuration pageFrom a system on the same network segment as the pump, attempt to access the device configuration interface without providing any credentials. This is typically accessed via HTTP/HTTPS to the device IP address. Attempt common paths such as /config, /setup, /admin, or the root URL. Observe whether the configuration page loads without any login prompt.Affected if The configuration page loads and allows viewing or modification of network settings without requiring any authentication credentials.
-
Verify if default or no network segmentation is in placeReview network documentation and firewall rules to determine whether the infusion pump is placed on a dedicated VLAN or if it shares a network segment with other untrusted devices. Use network scanning tools to confirm the pump is reachable from network segments other than a dedicated management VLAN.Affected if The device is reachable from network segments other than a restricted management network without intervening firewall controls.
A user is affected if a Fresenius Kabi Agilia SP MC WiFi infusion pump with firmware version d25 or earlier is accessible on the network and its configuration interface can be reached without authentication.
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 dataImplement authentication requirements for the configuration page, ideally through a vendor-provided patch. If no patch is available, isolate the device on a restricted network segment (VLAN) with firewall rules preventing unauthorized access to the management interface.
- Consultation6.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33843 — 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-2021-33843 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