CVE-2021-23207
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 attacker with physical access to the host can extract the secrets from the registry and create valid JWT tokens for the Fresenius Kabi Vigilant MasterMed version 2.0.1.3 application and impersonate arbitrary users. An attacker could manipulate RabbitMQ queues and messages by impersonating users.
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 Vigilant MasterMed version 2.0.1.3 application stores authentication secrets insecurely in the Windows registry. An attacker with physical access to the host can extract these secrets from the registry, use them to forge valid JWT tokens, and thereby impersonate arbitrary users within the application. This JWT-based authentication also protects RabbitMQ message queues, allowing the attacker to manipulate queues and messages.
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<= d25<= 3.3.0= 1.0= 1.0= 1.0< 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed Fresenius Kabi product and versionCheck the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Fresenius Kabi (or HKEY_CURRENT_USER\SOFTWARE\Fresenius Kabi) for installed product names and versions, or inspect Add/Remove Programs for Fresenius Kabi softwareAffected if The installed product and version match any of the affected ranges: Agilia Connect <= d25, Agilia Partner Maintenance Software <= 3.3.0, Vigilant Centerium = 1.0, Vigilant Insight = 1.0, Vigilant Mastermed = 1.0, or Link+ Agilia Firmware < 3.0 or = 3.0
-
Locate authentication secret registry keysExamine the Windows registry for keys under the Fresenius Kabi product paths (commonly under HKEY_LOCAL_MACHINE\SOFTWARE\Fresenius Kabi\[ProductName\] or similar application data paths) that contain JWT signing keys, API tokens, or authentication credentials stored as plain text or weakly protected valuesAffected if Registry keys containing JWT secrets, API keys, or authentication tokens are present in the Fresenius Kabi software registry location and are stored without strong protection (not using DPAPI, HSM, or proper encryption)
-
Verify RabbitMQ integration is in useCheck if RabbitMQ services are running and accessible, and verify the Fresenius Kabi application is configured to authenticate to RabbitMQ using JWT tokens by examining application configuration files or registry settings related to message queue connectionsAffected if RabbitMQ is configured and the application uses JWT-based authentication to connect to message queues, as the stolen registry secrets can forge tokens to manipulate these queues
A user is affected if they have any of the listed Fresenius Kabi products installed with a matching version AND the Windows registry contains unprotected authentication secrets that can be extracted to forge JWT tokens.
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
Secrets must be removed from insecure registry storage and migrated to a proper secrets management solution (e.g., Windows DPAPI-protected storage, HashiCorp Vault, or hardware security module). All compromised secrets should be rotated immediately after remediation.
- Consultation8.0 h
- Implementation24.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 $14,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23207 — 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-23207 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