CVE-2021-23233
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 · uneditedSensitive endpoints in Fresenius Kabi Agilia Link+ v3.0 and prior can be accessed without any authentication information such as the session cookie. An attacker can send requests to sensitive endpoints as an unauthenticated user to perform critical actions or modify critical configuration parameters.
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 confidenceAuthentication bypass vulnerability in Fresenius Kabi Agilia Link+ v3.0 and prior allows unauthenticated attackers to access sensitive endpoints without session cookies, enabling critical actions or configuration parameter modifications.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 installed Fresenius Kabi software versionsCheck the installed version of Fresenius Kabi software by inspecting the application metadata, About dialog, or version file in the installation directory. For firmware versions, access the device management interface or check the firmware package metadata.Affected if The installed version falls within these ranges: Agilia Partner Maintenance Software <= 3.3.0, Vigilant Centerium = 1.0, Vigilant Insight = 1.0, Vigilant Mastermed = 1.0, Agilia Connect Firmware <= d25, Link+ Agilia Firmware < 3.0 or = 3.0
-
Identify network-exposed interfacesReview network configuration and firewall rules to determine if the Fresenius Kabi application or device exposes HTTP/HTTPS management interfaces to the network. Check for open ports typically used by the application (such as 80, 443, or custom service ports).Affected if The management or configuration interface is accessible over the network without VPN or network segmentation restrictions
-
Test endpoint access without credentialsSend HTTP requests to known sensitive endpoints (such as /api/config, /api/admin, /settings, or maintenance endpoints) using a tool like curl or a browser, without providing any session cookies or authentication headers. Observe if the server returns valid JSON responses or configuration data instead of redirecting to a login page or returning 401/403 errors.Affected if Sensitive endpoints return actual application data, configuration parameters, or allow actions without requiring any authentication credentials
-
Check for missing session cookie requirementsCapture network traffic using a packet sniffer or browser developer tools while accessing the application. Examine whether sensitive endpoints reject requests that lack the session cookie or authentication token, or whether they accept and process requests with missing or blank cookie values.Affected if The application accepts and processes requests to sensitive endpoints without requiring a valid session cookie or authentication token in the request
You are affected if you have any of the listed product versions installed AND the sensitive endpoints are network-accessible AND they accept unauthenticated requests.
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
Implement proper authentication enforcement on all sensitive endpoints and apply network segmentation to restrict access to authorized users and systems only.
- Consultation10.0 h
- Implementation20.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 $13,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23233 — 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-23233 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