LiveActive security incident?Get immediate response
CVE Record

CVE-2019-4565: IBM Security Key Lifecycle Manager 3.0 and 3.0.1 does not require that users should have strong passwords b...

IBM Security Key Lifecycle Manager 3.0 and 3.0.1 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force ID: 166626.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

IBM Security Key Lifecycle Manager 3.0 and 3.0.1 did not require strong user passwords by default. That can make account compromise easier, which is concerning because this product manages security keys. The issue is medium severity, but exposure should be treated seriously where the product protects sensitive encryption workflows.

Executive priority

Prioritize remediation where SKLM protects business-critical encryption keys or is reachable beyond a tightly controlled admin network. This is not a confirmed exploited emergency, but weak account controls around key management can create outsized confidentiality risk.

Technical view

CVE-2019-4565 affects IBM Security Key Lifecycle Manager 3.0 and 3.0.1. The weakness is a default password policy that does not enforce strong passwords. CVSS 3.0 score is 5.9: network attack vector, high attack complexity, no privileges or user interaction, and high confidentiality impact only.

Likely exposure

Exposure is limited to IBM Security Key Lifecycle Manager 3.0 and 3.0.1 deployments. Risk is higher where administrative access is reachable over networks and accounts remain governed by weak default password requirements. The supplied sources do not identify other affected versions.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The issue can support account compromise if weak passwords are present, but the CVSS vector rates attack complexity as high and exploit maturity as unproven.

Researcher notes

The public record is narrow: affected versions, weak default password policy, IBM X-Force ID 166626, and CVSS details. No CWE, exploit details, or named patch level are included in the supplied bundle, so validation should stay focused on version and password-policy state.

Mitigation direction

  • Check IBM’s security bulletin for the official fix or configuration guidance.
  • Identify and upgrade or remediate affected 3.0 and 3.0.1 deployments.
  • Enforce strong password requirements for all SKLM user accounts.
  • Review privileged SKLM accounts for weak, reused, or default passwords.
  • Restrict SKLM administrative access to trusted management networks.

Validation and detection

  • Inventory IBM Security Key Lifecycle Manager versions in production and recovery environments.
  • Confirm whether any deployment is version 3.0 or 3.0.1.
  • Review SKLM password policy settings against organizational requirements.
  • Check user accounts for weak or noncompliant password posture.
  • Review authentication logs for suspicious failed or successful access.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-4565 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/A:N/S:U/PR:N/UI:N/I:N/AC:H/C:H/AV:N/E:U/RC:C/RL:O

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.0MediumCVSS:3.0/A:N/S:U/PR:N/UI:N/I:N/AC:H/C:H/AV:N/E:U/RC:C/RL:O2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.9Medium
CVSS 3.0 vector shape for CVE-2019-4565Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/A:N/S:U/PR:N/UI:N/I:N/AC:H/C:H/AV:N/E:U/RC:C/RL:O

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMSecurity Key Lifecycle Manager3.0, 3.0.1Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.