CVE-2021-33846
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 Vigilant Software Suite (Mastermed Dashboard) version 2.0.1.3 issues authentication tokens to authenticated users that are signed with a symmetric encryption key. An attacker in possession of the key can issue valid JWTs and impersonate arbitrary 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 Mastermed Dashboard in Fresenius Kabi Vigilant Software Suite v2.0.1.3 issues JWT authentication tokens signed with a symmetric encryption key. Because the signing key is exposed to attackers, they can craft valid JWTs and impersonate arbitrary users, achieving full authentication bypass.
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
- 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 installed software versionLocate the Fresenius Kabi software installation and check its version number (typically visible in the application UI, About section, or installed programs list)Affected if The version matches any of the affected products: Agilia Partner Maintenance Software <= 3.3.0, Vigilant Centerium = 1.0, Vigilant Insight = 1.0, Vigilant Mastermed = 1.0, Agilia Connect Firmware <= d25, or Link+ Agilia Firmware < 3.0 or = 3.0
-
Confirm JWT authentication is in useInspect application logs, network traffic, or configuration to verify that JWT (JSON Web Token) is being used for user authenticationAffected if JWT tokens are being issued for session management and the system uses a symmetric signing key
-
Locate the JWT signing keySearch configuration files, property files, or application source code for JWT-related settings such as 'jwt.secret', 'signing.key', or similar symmetric key parametersAffected if A symmetric signing key (rather than asymmetric RSA/ECDSA) is found hardcoded or stored in an accessible configuration file
-
Verify key exposureExamine whether the signing key is stored in a location readable by unauthorized users, embedded in client-side code, or transmitted over unencrypted channelsAffected if The symmetric key is stored in plaintext, embedded in the application, or accessible without proper access controls
You are affected if you run any of the listed product versions and the application uses JWT authentication with an exposed symmetric signing key that can be retrieved by an attacker.
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
Rotate the exposed symmetric signing key immediately and migrate to asymmetric JWT signing (RSA/ECDSA) with secure key management. Implement additional token validation controls and audit logs to detect token forgery attempts.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33846 — 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-33846 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