CVE-2024-22355
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 · uneditedIBM QRadar Suite Products 1.10.12.0 through 1.10.18.0 and IBM Cloud Pak for Security 1.10.0.0 through 1.10.11.0 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: 280781.
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 · high confidenceIBM QRadar Suite Products and IBM Cloud Pak for Security do not enforce strong password requirements by default, allowing users to set weak passwords that are more susceptible to brute force, dictionary, or credential stuffing attacks. This default configuration deficiency could enable attackers to more easily compromise user accounts.
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>= 1.10.0.0, <= 1.10.11.0>= 1.10.12.0, <= 1.10.18.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed product and versionAccess the IBM QRadar or Cloud Pak for Security administration console. Navigate to System Configuration or About section to find the exact version number (for Cloud Pak: oc get cp4s <instance-name> -n <namespace> --no-headers 2>/dev/null or check the operator version; for QRadar: System > Advanced > System License and Version info)Affected if Version falls within IBM Cloud Pak for Security 1.10.0.0-1.10.11.0 or IBM QRadar Suite 1.10.12.0-1.10.18.0 AND strong password policies remain disabled (default state)
-
Verify password policy configuration statusIn the admin console, navigate to User Management or Security Settings. Locate the Password Policy section. Check if password strength enforcement is explicitly enabled and set to enforceAffected if Password policy enforcement shows as disabled, not configured, or set to optional/low strength requirements
-
Check minimum password length settingIn Password Policy settings, examine the minimum length configuration (typically found under Password Requirements or Password Rules). Default weak configurations allow short passwords (e.g., fewer than 8-12 characters)Affected if Minimum length is set below 12 characters or is set to the default weak value without complexity requirements
-
Verify password complexity requirementsIn Password Policy settings, check if requirements for uppercase, lowercase, numbers, and special characters are enabled and enforcedAffected if Complexity requirements are disabled, set to optional, or not enforced in the policy configuration
-
Confirm account lockout thresholdIn Security or User Management settings, locate Account Lockout or Failed Login Attempts configuration. Check if a lockout threshold is configuredAffected if Account lockout is disabled, set to unlimited attempts, or threshold is set too high (e.g., >10 attempts) allowing brute force attacks
You are affected if your IBM Cloud Pak for Security version is 1.10.0.0-1.10.11.0 or QRadar Suite version is 1.10.12.0-1.10.18.0 AND strong password policies (minimum length, complexity, account lockout) are not explicitly enabled and enforced in the administration settings.
Generated from the published advisory. Verify against your own configuration.
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 · scopedEnable and enforce strong password policies including minimum length, complexity requirements, and account lockout thresholds in IBM QRadar Suite and Cloud Pak for Security administration settings.
QRadar Suite: upgrade to 1.10.19.0 or later; Cloud Pak for Security: upgrade to 1.10.12.0 or later
- 1. Determine which IBM product is affected in your environment (QRadar Suite or Cloud Pak for Security)
- 2. Identify your current installed version using the IBM software inventory or console
- 3. For QRadar Suite users: Plan upgrade to version 1.10.19.0 or later (the first release after the affected range)
- 4. For Cloud Pak for Security users: Plan upgrade to version 1.10.12.0 or later (the first release after the affected range)
- 5. Review IBM's official support portal for the specific security patch or maintenance release that addresses CVE-2024-22355
- 6. Before upgrading, backup all critical data and configuration
- 7. Schedule maintenance window as upgrades may require downtime
- 8. Perform upgrade following IBM's documented upgrade procedure for your specific product
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22355 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-22355 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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