How severe is CVE-2020-4573?

CVE-2020-4573 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2020-4573 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-4573?

CVE-2020-4573 primarily affects Ibm Security Key Lifecycle Manager. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2020-4573?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2020-4573 published?

CVE-2020-4573 was published on 2020-07-29 and last updated on 2026-06-17.

CVE-2020-4573

CVE-2020-4573 is a medium-severity vulnerability in Ibm Security Key Lifecycle Manager with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 5.3)
CVSS v2: 5.0
EPSS exploit prediction: 1% (67th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Ibm Security Key Lifecycle Manager
Published: 2020-07-29
Last modified: 2026-06-17

Description

IBM Tivoli Key Lifecycle Manager 3.0.1 and 4.0 could disclose sensitive information due to responding to unauthenticated HTTP requests. IBM X-Force ID: 184180.

Frequently asked questions

What is CVE-2020-4573?: IBM Tivoli Key Lifecycle Manager 3.0.1 and 4.0 could disclose sensitive information due to responding to unauthenticated HTTP requests. IBM X-Force ID: 184180.
How severe is CVE-2020-4573?: CVE-2020-4573 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2020-4573 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-4573?: CVE-2020-4573 primarily affects Ibm Security Key Lifecycle Manager. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2020-4573?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2020-4573 published?: CVE-2020-4573 was published on 2020-07-29 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:ibm:security_key_lifecycle_manager:3.0.1:*:*:*:*:*:*:*
cpe:2.3:a:ibm:security_key_lifecycle_manager:4.0:*:*:*:*:*:*:*

More vulnerabilities in Ibm Security Key Lifecycle Manager

CVE-2020-4567 — Critical (CVSS 9.8): IBM Tivoli Key Lifecycle Manager 3.0.1 and 4.0 uses an inadequate account lockout setting that could allow a remote…
CVE-2017-1670 — Critical (CVSS 9.8): IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 is vulnerable to SQL injection. A remote attacker could send…
CVE-2016-6093 — Critical (CVSS 9.8): IBM Tivoli Key Lifecycle Manager does not require that users should have strong passwords by default, which makes it…
CVE-2016-6095 — Critical (CVSS 9.8): IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 uses an inadequate account lockout setting that could allow a remote…
CVE-2017-1672 — High (CVSS 8.8): IBM Tivoli Key Lifecycle Manager 2.6 and 2.7 is vulnerable to cross-site request forgery which could allow an attacker…
CVE-2016-6103 — High (CVSS 8.8): IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 is vulnerable to cross-site request forgery which could allow an attacker…

All CVEs affecting Ibm Security Key Lifecycle Manager →