Security readout for executives and security teams
Plain-English summary
This vulnerability affects Fresenius Kabi Vigilant Software Suite (Mastermed Dashboard) 2.0.1.3. If an attacker obtains the token-signing symmetric key, they can create trusted login tokens and impersonate other users. The business risk is unauthorized access to sensitive dashboard functions, but exploitation requires high privileges and possession of the key.
Executive priority
Treat as a moderate-priority medical technology security issue. It is not reported as actively exploited, but successful abuse could allow trusted-user impersonation and high confidentiality and integrity impact. Prioritize inventory, vendor guidance, and access restriction.
Technical view
Mastermed Dashboard issues JWT authentication tokens signed with a symmetric encryption key. The CVE describes CWE-327, use of a broken or risky cryptographic algorithm. An attacker who has the key can forge valid JWTs and impersonate arbitrary users. CVSS 3.1 is 5.9 with network access, high complexity, and high privileges required.
Likely exposure
Exposure appears limited to environments running Fresenius Kabi Vigilant Software Suite (Mastermed Dashboard), specifically version 2.0.1.3 per the CVE description. The bundle does not identify other affected versions, internet exposure prevalence, or default deployment patterns.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not marked as CISA KEV. Exploitation depends on an attacker obtaining the symmetric signing key, then using it to issue trusted JWTs. That prerequisite materially limits opportunistic exploitation.
Researcher notes
Evidence is narrow: the bundle identifies the JWT symmetric-key design weakness and impact, but does not include patch details, affected-version range beyond the description, or proof of exploitation. Avoid assuming broader Fresenius Kabi product impact without vendor confirmation.
Mitigation direction
- Check Fresenius Kabi and CISA guidance for vendor-approved remediation.
- Inventory Mastermed Dashboard deployments and confirm exact versions.
- Restrict dashboard access to trusted clinical or administrative networks.
- Protect, review, and rotate token-signing secrets if vendor guidance supports it.
- Monitor authentication logs for unusual user impersonation or privilege use.
Validation and detection
- Confirm whether Mastermed Dashboard 2.0.1.3 is deployed.
- Review JWT signing configuration and key handling controls.
- Verify access controls limit dashboard reachability to trusted users and networks.
- Check logs for anomalous token use or impossible user activity.
- Document remediation status against CISA advisory ICSMA-21-355-01.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-327: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-33846 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N0.75.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.9MediumVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/uscert/ics/advisories/icsma-21-355-01CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of a Broken or Risky Cryptographic Algorithm
Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.