CVE-2018-1742

CVE-2018-1742 is a medium-severity vulnerability in Ibm Security Key Lifecycle Manager with a CVSS 3.x base score of 5.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-798.

Key facts

Description

IBM Tivoli Key Lifecycle Manager 2.6, 2.7, and 3.0 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: 148421.

Frequently asked questions

What is CVE-2018-1742?
IBM Tivoli Key Lifecycle Manager 2.6, 2.7, and 3.0 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: 148421.
How severe is CVE-2018-1742?
CVE-2018-1742 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over local access with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2018-1742 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-1742?
CVE-2018-1742 affects Ibm Security Key Lifecycle Manager. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-1742?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2018-1742 published?
CVE-2018-1742 was published on 2018-10-08 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Ibm Security Key Lifecycle Manager

All CVEs affecting Ibm Security Key Lifecycle Manager →

Other CWE-798 (Use of Hard-coded Credentials) vulnerabilities

Browse all CWE-798 (Use of Hard-coded Credentials) vulnerabilities →