dbcve.org
Cloud Pak For SecurityApplication · Ibm

CVE-2025-25019

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-03
Fix available
A fix is available. Upgrade to after 1.11.2.0 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM QRadar Suite Software 1.10.12.0 through 1.11.2.0 and IBM Cloud Pak for Security 1.10.0.0 through 1.10.11.0 does not invalidate session after a logout which could allow a user to impersonate another user on the system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a session management vulnerability where the logout function does not properly invalidate the user session on the server side. When a user logs out, the session token remains valid, allowing an attacker who has obtained the session ID (through network interception, XSS, or other means) to continue impersonating the legitimate user even after logout.

MitigationImplement server-side session invalidation during logout by removing the session from the session store and/or marking it as terminated in the database. Additionally, consider implementing session timeout and regenerating session IDs upon login.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cloud Pak For SecurityApplication
Affected:>= 1.10.0.0, <= 1.10.11.0
Qradar SuiteApplication
Affected:>= 1.10.12.0, <= 1.11.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product and version
    Locate the IBM product version through the admin console or system command (for Cloud Pak check via 'cpctl version' or console UI; for QRadar check System > License and Usage or help > about)
    Affected if Product is IBM Cloud Pak For Security version 1.10.0.0 through 1.10.11.0, or IBM QRadar Suite version 1.10.12.0 through 1.11.2.0
  2. Confirm session-based authentication is active
    Access the security or authentication settings in the admin console and verify that user sessions are enabled (look for session timeout, session management, or authentication settings)
    Affected if User session management is enabled and users authenticate via session tokens
  3. Test session validity after logout
    Log in with a test user, capture the session identifier from cookies or headers, log out, then attempt an authenticated request using the original session token to verify if the server accepts it
    Affected if The original session token remains valid and server accepts requests after logout

You are affected if your installed product version is within the listed ranges AND session-based authentication is active, with the session token remaining valid after logout.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.11.2.0
Interim mitigation

Implement server-side session invalidation during logout by removing the session from the session store and/or marking it as terminated in the database. Additionally, consider implementing session timeout and regenerating session IDs upon login.

Recommended fix Moderate confidence

Upgrade to a release > 1.10.11.0 for Cloud Pak for Security, or > 1.11.2.0 for QRadar Suite (e.g., the next available IBM security patch or major/minor release)

  1. 1. Identify the specific IBM QRadar Suite or Cloud Pak for Security version currently installed
  2. 2. Review the IBM Cloud Pak for Security lifecycle and QRadar Suite lifecycle pages for available fixed releases beyond 1.10.11.0 and 1.11.2.0 respectively
  3. 3. Plan upgrade during a maintenance window to minimize business impact
  4. 4. Back up all critical configuration data, custom rules, and event data before initiating upgrade
  5. 5. Download the appropriate fixed release from IBM Fix Central or IBM Passport Advantage
  6. 6. Follow the IBM product-specific upgrade documentation for your deployment type (standalone, cluster, etc.)
  7. 7. After upgrade, verify that sessions are properly invalidated upon logout by testing with a test account
  8. 8. Confirm the fix by reviewing release notes for CVE-2025-25019
Caveat Review release notes for potential breaking changes between your current version and the target version; some configuration changes or data migration may be required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Pak For Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25019 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-25019 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data