ibm spectrum protect plus
productUScpe:2.3:a:ibm:spectrum_protect_plus:*:*:*:*:*:*:*:*
A product tracked in the threat graph; the vulnerabilities below are known to affect it.
by severity
5critical16high23medium0low
updated 2026-10-28
| ID | severity CVSS base severity and score (0–10). | EPSS FIRST.org probability this is exploited in the next 30 days, with its percentile rank among all CVEs. | exploitable On CISA's Known Exploited Vulnerabilities list, or a public exploit is on file. | patched Whether a fixed version is on file for an affecting range. | published | affected |
|---|
| CVE-2020-4241US | high8.8 | 66.3% (99th) | — | ✗no fix | 2020-03-31 | 10.1.0 → 10.1.5 |
| CVE-2020-4469US | critical9.8 | 13.4% (96th) | — | ✗no fix | 2020-06-15 | 10.1.0 → 10.1.5 |
| CVE-2020-4206US | high8.8 | 4.61% (92nd) | — | ✗no fix | 2020-03-31 | 10.1.0 → 10.1.5 |
| CVE-2020-4242US | high8.8 | 4.59% (92nd) | — | ✗no fix | 2020-03-31 | 10.1.0 → 10.1.5 |
| CVE-2020-4471US | medium6.5OT elevated | 2.65% (86th) | — | ✗no fix | 2020-06-15 | 10.1.0 → 10.1.5 |
| CVE-2020-4711US | medium6.5 | 2.61% (85th) | — | ✗no fix | 2020-09-15 | 10.1.0 → 10.1.6 |
| CVE-2020-4854US | critical9.8OT elevated | 2.43% (84th) | — | ✗no fix | 2020-11-23 | 10.1.0 → 10.1.6 |
| CVE-2020-5023US | high7.5 | 2.31% (83rd) | — | ✗no fix | 2021-02-10 | 10.1.0 → 10.1.7 |
| CVE-2020-4240US | medium6.5 | 1.97% (80th) | — | ✗no fix | 2020-03-31 | 10.1.0 → 10.1.5 |
| CVE-2020-4470US | high8.0 | 1.91% (80th) | — | ✗no fix | 2020-06-15 | 10.1.0 → 10.1.5 |
| CVE-2022-40608US | high7.5 | 1.84% (79th) | — | ✗no fix | 2022-09-19 | 10.1.6 → 10.1.11 |
| CVE-2020-4208US | critical9.8OT elevated | 1.80% (78th) | — | ✗no fix | 2020-03-31 | 10.1.0 → 10.1.5 |
| CVE-2020-4703US | high8.0 | 1.76% (78th) | — | ✗no fix | 2020-09-15 | 10.1.0 → 10.1.6 |
| CVE-2020-4214US | high7.5 | 1.63% (76th) | — | ✗no fix | 2020-03-31 | 10.1.0 → 10.1.5 |
| CVE-2020-4216US | critical9.8OT elevated | 1.57% (75th) | — | ✗no fix | 2020-06-15 | 10.1.0 → 10.1.5 |
| CVE-2020-4209US | medium5.4 | 1.36% (72nd) | — | ✗no fix | 2020-05-04 | 10.1.0 → 10.1.5 |
| CVE-2020-5019US | medium6.5 | 1.34% (71st) | — | ✓10.1.7 | 2021-01-08 | 10.1.0 → 10.1.7 |
| CVE-2020-4783US | medium5.9OT elevated | 1.21% (68th) | — | ✗no fix | 2020-11-23 | 10.1.0 → 10.1.6 |
| CVE-2020-4565US | medium5.9 | 1.15% (67th) | — | ✗no fix | 2020-06-26 | 10.1.0 → 10.1.5 |
| CVE-2020-5022US | medium5.3OT elevated | 1.01% (63rd) | — | ✓10.1.7 | 2021-01-08 | 10.1.0 → 10.1.7 |
| CVE-2022-22354US | high7.5 | 0.94% (61st) | — | ✓10.1.9.3 | 2022-03-14 | 10.1.0 → 10.1.9.3 |
| CVE-2020-4477US | medium6.5 | 0.94% (61st) | — | ✗no fix | 2020-06-15 | 10.1.0 → 10.1.5 |
| CVE-2020-5020US | medium6.1 | 0.90% (59th) | — | ✓10.1.7 | 2021-01-08 | 10.1.0 → 10.1.7 |
| CVE-2021-20432US | medium6.5OT elevated | 0.75% (55th) | — | ✗no fix | 2021-04-26 | 10.1.0 → 10.1.7 |
| CVE-2022-22396US | high7.5 | 0.72% (54th) | — | ✓10.1.10 | 2022-06-06 | 10.1.0 → 10.1.10 |
| CVE-2021-29694US | high7.5OT elevated | 0.71% (53rd) | — | ✗no fix | 2021-04-26 | 10.1.0 → 10.1.7 |
| CVE-2021-39063US | critical9.1 | 0.68% (52nd) | — | ✓10.1.9 | 2021-12-13 | 10.1.0 → 10.1.9 |
| CVE-2020-5018US | high7.5OT elevated | 0.68% (52nd) | — | ✓10.1.7 | 2021-01-08 | 10.1.0 → 10.1.7 |
| CVE-2023-47148US | high7.5OT elevated | 0.61% (49th) | — | ✓10.1.15.3 | 2024-02-02 | 10.1.0 → 10.1.15.3 |
| CVE-2022-40234US | medium5.9 | 0.61% (49th) | — | ✓10.1.12 | 2022-09-19 | < 10.1.12 |
| CVE-2020-4496US | medium5.9 | 0.59% (48th) | — | ✗no fix | 2021-12-13 | 10.1.0 → 10.1.8.1 |
| CVE-2021-39057US | high8.1 | 0.50% (43rd) | — | ✓10.1.9 | 2021-12-13 | 10.1.0 → 10.1.9 |
| CVE-2019-4357US | medium6.7 | 0.46% (40th) | — | ✗no fix | 2019-07-01 | 3 versions |
| CVE-2019-4703US | medium5.3 | 0.46% (39th) | — | ✗no fix | 2020-02-24 | 10.1.0 → 10.1.5 |
| CVE-2020-4497US | medium5.9OT elevated | 0.41% (35th) | — | ✓10.1.13 | 2022-12-14 | 10.1.0 → 10.1.13 |
| CVE-2019-4383US | medium6.7 | 0.40% (34th) | — | ✗no fix | 2019-07-01 | 3 versions |
| CVE-2018-1768US | high7.8 | 0.38% (32nd) | — | ✗no fix | 2018-09-26 | 2 versions |
| CVE-2019-4385US | medium6.5 | 0.33% (27th) | — | ✗no fix | 2019-06-19 | 10.1.2.219 → 10.1.2.303 |
| CVE-2021-3669US | medium5.5 | 0.30% (22nd) | — | ✗no fix | 2022-08-26 | 10.1.0 → 10.1.10.2 |
| CVE-2019-4652US | high7.1OT elevated | 0.27% (20th) | — | ✗no fix | 2019-11-12 | 10.1.0 → 10.1.4 |
| CVE-2021-20536US | medium6.2 | 0.27% (18th) | — | ✗no fix | 2021-04-26 | 2 versions |
| CVE-2020-5021US | medium4.4 | 0.25% (16th) | — | ✓10.1.7 | 2021-01-08 | 10.1.0 → 10.1.7 |
| CVE-2020-4631US | medium5.5 | 0.24% (16th) | — | ✗no fix | 2020-08-04 | 10.1.0 → 10.1.6 |
| CVE-2021-20490US | medium5.5OT elevated | 0.20% (10th) | — | ✗no fix | 2021-06-29 | 10.1.0 → 10.1.8 |