CVE-2020-4854 json
IBM Spectrum Protect Plus 10.1.0 thorugh 10.1.6 contains hard-coded credentials, such as a password or cryptographic key, which it uses for…
published 5y ago modified 4mo ago also EUVD-2020-26101
- cvss
- 9.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
IBM Spectrum Protect Plus 10.1.0 thorugh 10.1.6 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. IBM X-Force ID: 190454.
Patch / fix
- ibm.com/support/pages/node/6367823 advisory
Is CVE-2020-4854 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.43% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- tenable.com https://www.tenable.com/security/research/tra-2020-66 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 9.8 | CVSS:3.0/UI:N/PR:N/S:U/I:H/A:H/C:H/AC:L/AV:N/RC:C/RL:O/E:U |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- IBM Spectrum Protect Plus
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
ibm.com
/support/pages/node/6367823
patch, vendor-advisory
-
tenable.com
/security/research/tra-2020-66
exploit, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/190454
vdb-entry, vendor-advisory
Sources
- CVE List CVE-2020-4854
- NVD CVE-2020-4854
Fencer Intel 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.