IBM Tivoli Key Lifecycle Manager 2.6 and 2.7 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• ibm security key lifecycle manager2.6.0
• ibm security key lifecycle manager2.6.0.1
• ibm security key lifecycle manager2.6.0.2
• ibm security key lifecycle manager2.6.0.3
• ibm security key lifecycle manager2.7.0
• ibm security key lifecycle manager2.7.0.1
• ibm security key lifecycle manager2.7.0.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.

• IBM Security Key Lifecycle Manager

  • 2.6, 2.7affected

Other highest-scoring records for the same primary product.

• CVE-2020-4567IBM Tivoli Key Lifecycle Manager 3.0.1 and 4.0 uses an inadequate account lockout setting that could allow a remote attacker to brute force
  40Plan
• CVE-2017-1670IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 is vulnerable to SQL injection.
  40Plan
• CVE-2016-6093IBM Tivoli Key Lifecycle Manager does not require that users should have strong passwords by default, which makes it easier for attackers to
  40Plan
• CVE-2023-25684IBM Security Key Lifecycle Manager SQL injection
  39Monitor
• CVE-2016-6095IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 uses an inadequate account lockout setting that could allow a remote attacker to brute force ac
  39Monitor
• CVE-2018-1742IBM 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 f
  37Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1app.use(session({ cookie: { httpOnly: true } }));2app.post("/account/address", updateAddress);

1app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));2app.post("/account/address", csrfProtection, updateAddress);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.