IBM Tivoli Key Lifecycle Manager 3.0.1 and 4.0 uses a protection mechanism that relies on the existence or values of an input, but the inpu…

published 2020-07-29 6y ago modified 2026-06-17 4mo ago also EUVD-2020-25816

cvss: 6.5; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.2%; EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits: 0; none known

IBM Tivoli Key Lifecycle Manager 3.0.1 and 4.0 uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism. IBM X-Force ID: 184158.

Patch / fix

links 1

ibm.com/support/pages/node/6253781 advisory

Is CVE-2020-4569 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 Fencer

Exploit prediction

1.17% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	6.5	CVSS:3.0/S:U/UI:N/PR:N/AV:N/I:L/C:L/AC:L/A:N/RL:O/RC:C/E:U
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CNA	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
NVD	2.0	6.4	AV:N/AC:L/Au:N/C:P/I:P/A:N

Affected products

IBM Security Key Lifecycle Manager

References

ibm.com /support/pages/node/6253781
patch, vendor-advisory
exchange.xforce.ibmcloud.com /vulnerabilities/184158
vdb-entry, vendor-advisory

Sources

CVE List CVE-2020-4569
NVD CVE-2020-4569

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.