CVE-2021-43552 json
Philips Patient Information Center iX (PIC iX) and Efficia CM Series Use of Hard-coded Cryptographic Key
published 2021-12-27 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-30481
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
The use of a hard-coded cryptographic key significantly increases the possibility encrypted data may be recovered from the Patient Information Center iX (PIC iX) Versions B.02, C.02, and C.03.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSMA-21-322-02 updated cvss 6.1
Philips Patient Information Center iX (PIC iX) and Efficia CM Series
-
Philips Efficia CM Series A.01 <= C.0x, 4.0 Philips Patient Information Center iX (PIC iX) B.02, C.02, C.03affected: vendor fix, mitigation “As an interim mitigation, Philips recommends the following actions outlined in the Philips Patient Monitoring System Security for Clinical Networks guide at InCenter.” incenter.medical.philips.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- Philips Patient Information Center iX (PIC iX)
Classification
- Weakness
-
- CWE-321 Use of Hard-coded Cryptographic Key
References
-
cisa.gov
/uscert/ics/advisories/icsma-21-322-02
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2021-43552
- NVD CVE-2021-43552
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.