CVE-2021-23236
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 · uneditedRequests may be used to interrupt the normal operation of the device. When exploited, Fresenius Kabi Agilia Link+ version 3.0 must be rebooted via a hard reset triggered by pressing a button on the rack system.
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 confidenceThis is a denial of service vulnerability in Fresenius Kabi Agilia Link+ version 3.0, a medical infusion pump management system. Remote attackers can send malicious requests that disrupt normal device operation, causing the system to become unresponsive and requiring a manual hard reset via a button on the rack system to restore functionality.
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<= 3.3.0= 1.0= 1.0= 1.0<= d25< 3.0= 3.0CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Inventory Fresenius Kabi medical device management software in the environmentReview installed software, device inventories, or IT asset management systems for presence of Fresenius Kabi Agilia or Vigilant product linesAffected if Any Fresenius Kabi software from the affected product list is present in the environment
-
Identify Agilia Partner Maintenance Software versionCheck the installed software version through the application interface, Windows Programs and Features, or vendor documentation for this specific softwareAffected if Version is 3.3.0 or lower
-
Identify Vigilant product versions (Centerium, Insight, Mastermed)Check the installed software version for each Vigilant product through the application interface, system information, or vendor documentationAffected if Any of these three products are at version 1.0
-
Identify Agilia Connect firmware versionAccess the device firmware settings or system information screen for the Agilia Connect device; compare the firmware build identifierAffected if Firmware version is d25 or lower (note: version format uses alphanumeric build identifiers)
-
Identify Link+ Agilia firmware versionAccess the device firmware settings or system information screen for the Link+ Agilia pump; compare the firmware version numberAffected if Firmware version is 3.0 or any version below 3.0
-
Assess network exposure of affected devicesReview firewall rules, network segmentation, and access controls to determine if these medical devices are accessible from unauthorized network segments or external IP addressesAffected if Devices are directly accessible from network segments outside the intended medical device network without filtering
A defender is affected if any Fresenius Kabi product from the affected list is present in their environment AND the specific version matches the affected version range, particularly if the device has network accessibility from non-isolated segments.
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 data3.0
Isolate the medical device network segment, implement firewall rules to restrict unauthorized access, and monitor for anomalous request patterns. Coordinate with Fresenius Kabi for vendor-specific patch availability and follow medical device security best practices.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.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 $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23236 — 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-23236 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