LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38977: IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 does not set the secure attribute on authorizatio...

IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic. IBM X-Force ID: 212782.

LowCVSS 3.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity IBM Key Lifecycle Manager issue where session cookies or authorization tokens may be sent over unencrypted HTTP. If a user is induced to access an insecure link and traffic can be observed, an attacker may capture cookie values.

Executive priority

Treat this as routine patching unless the product is exposed to untrusted networks or insecure HTTP is allowed. It affects key-management infrastructure, so remediation should be tracked even though severity is low.

Technical view

IBM Tivoli/Security Key Lifecycle Manager versions 3.0, 3.0.1, 4.0, and 4.1 omit the Secure attribute on authorization tokens or session cookies. CVSS 3.0 score is 3.1, with network attack vector, user interaction required, high attack complexity, and low confidentiality impact.

Likely exposure

Exposure is limited to organizations running the listed IBM Key Lifecycle Manager versions or maintenance levels. Risk increases where users can reach the service over HTTP or where network traffic can be observed.

Exploitation context

The provided sources do not report active exploitation, and CISA KEV is false. The described attack requires user interaction and the ability to observe insecure traffic, which lowers practical urgency.

Researcher notes

Evidence is strongest for cookie flag misconfiguration and affected IBM versions. The source bundle does not provide exploit-in-the-wild evidence, detailed fixed versions, or alternate mitigations beyond IBM’s advisory context.

Mitigation direction

  • Review IBM advisory for the exact supported fix or upgrade path.
  • Apply IBM-recommended updates for affected Key Lifecycle Manager versions.
  • Restrict management access to trusted networks while remediation is pending.
  • Enforce HTTPS-only access where operationally possible.
  • Check vendor guidance before making configuration-only assumptions.

Validation and detection

  • Inventory IBM Key Lifecycle Manager deployments and exact maintenance levels.
  • Confirm whether affected versions 3.0, 3.0.1, 4.0, or 4.1 are present.
  • Inspect application cookies for the Secure attribute in normal login flows.
  • Verify users cannot access the service through insecure HTTP paths.
  • Confirm remediation status against IBM’s advisory, not version assumptions.
Prepared
Confidence
high
Sources
4

Public sources used

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-2021-38977 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
Low
CVSS
3.1 (3.0)
Known Exploited
No
Published

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

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
3.1CVSS 3.0LowCVSS:3.0/AV:N/C:L/UI:R/AC:H/PR:N/S:U/I:N/A:N/RC:C/RL:O/E:U1.61.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

3.1Low
CVSS 3.0 vector shape for CVE-2021-38977Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMSecurity Key Lifecycle Manager3.0, 3.0.1, 4.0, 3.0.0.4, 3.0.1.5, 4.0.0.3, 4.1, 4.1.0.1, 4.1.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.