dbcve.org
Mq OperatorApplication · Ibm

CVE-2025-1333

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-01
Fix available
A fix is available. Upgrade to after 3.2.10 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 MQ Container when used with the IBM MQ Operator LTS 2.0.0 through 2.0.29, MQ Operator CD 3.0.0, 3.0.1, 3.1.0 through 3.1.3, 3.3.0, 3.4.0, 3.4.1, 3.5.0, 3.5.1, and MQ Operator SC2 3.2.0 through 3.2.10 and configured with Cloud Pak for Integration Keycloak could disclose sensitive information to a privileged user.

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

IBM MQ Container deployed with IBM MQ Operator versions 2.0.0-2.0.29 (LTS), 3.0.0-3.5.1 (CD), and 3.2.0-3.2.10 (SC2) when integrated with Cloud Pak for Integration Keycloak may allow a privileged user to access sensitive information due to improper access control in the Keycloak authentication flow.

MitigationUpdate IBM MQ Operator to the latest version that addresses this vulnerability. Review Keycloak role mappings and ensure proper access controls are configured for MQ resources.

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
Mq OperatorApplication
Affected:>= 2.0.0, <= 2.0.29>= 2.2.0, <= 2.2.2>= 2.3.0, <= 2.3.3>= 2.4.0, <= 2.4.8>= 3.1.0, <= 3.1.3>= 3.2.0, <= 3.2.10= 3.0.0= 3.0.1= 3.3.0= 3.4.0= 3.4.1= 3.5.0
Supplied Mq Advanced Container ImagesApplication
Affected:= 9.2.0.1= 9.2.0.2= 9.2.0.4= 9.2.0.5= 9.2.0.6= 9.2.3.0= 9.2.4.0= 9.2.5.0= 9.3.0.0= 9.3.0.1= 9.3.0.3= 9.3.0.4

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify IBM MQ Operator version
    Run 'oc get operandrequest -A -o jsonpath={.items[*].metadata.namespace}' to find namespaces with MQ deployments, then check operator version with 'oc get deployment -n <namespace> ibm-mq-operator' or check CSV with 'oc get csv -n <namespace>'
    Affected if Operator version falls within ranges: 2.0.0-2.0.29, 2.2.0-2.2.2, 2.3.0-2.3.3, 2.4.0-2.4.8, 3.1.0-3.1.3, 3.2.0-3.2.10, or exact versions 3.0.0, 3.0.1, 3.3.0, 3.4.0, 3.4.1, 3.5.0
  2. Identify MQ container image version
    Query the MQ queue manager pod image: 'oc get pod -n <mq-namespace> -l app.kubernetes.io/instance=<qmgr-name> -o jsonpath={.items[*].spec.containers[*].image}'
    Affected if Image tag matches: 9.2.0.1, 9.2.0.2, 9.2.0.4, 9.2.0.5, 9.2.0.6, 9.2.3.0, 9.2.4.0, 9.2.5.0, 9.3.0.0, 9.3.0.1, 9.3.0.3, or 9.3.0.4
  3. Verify Keycloak integration configuration
    Check for Cloud Pak for Integration Keycloak integration by examining MQ QueueManager CR or auth configuration: 'oc get queuemanager <qmgr-name> -n <namespace> -o yaml' and look for authEndpoint, oidcConfig, or Keycloak-related settings under spec
    Affected if Keycloak/OIDC authentication is configured for MQ with Cloud Pak for Integration (authEndpoint points to CP4I Keycloak)
  4. Check for privileged user access patterns
    Review Keycloak token claims and role mappings for MQ users: examine JWT tokens or query Keycloak API for user realm roles and client roles assigned to MQ resources
    Affected if Users with elevated privileges in Keycloak can access MQ resources they should not have access to due to improper role validation

Environment is affected if IBM MQ Operator version is within the vulnerable ranges AND MQ container images match the listed versions AND Keycloak integration from Cloud Pak for Integration is configured for MQ authentication.

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 3.2.10
Interim mitigation

Update IBM MQ Operator to the latest version that addresses this vulnerability. Review Keycloak role mappings and ensure proper access controls are configured for MQ resources.

Recommended fix High confidence

MQ Operator: 2.0.30, 2.2.3, 2.3.4, 2.4.9 (or later LTS); MQ Advanced Container Images: 9.2.0.6 or later

  1. 1. Identify the current IBM MQ Operator version in use by running: kubectl get deployment -n <namespace> ibm-mq-operator -o jsonpath='{.spec.template.spec.containers[0].image}'
  2. 2. Identify the current MQ Advanced Container Image version: kubectl get qmgr -n <namespace> -o jsonpath='{.items[0].spec.image}'
  3. 3. For MQ Operator LTS 2.0.x: Upgrade to version 2.0.30 or later
  4. 4. For MQ Operator LTS 2.2.x: Upgrade to version 2.2.3 or later
  5. 5. For MQ Operator LTS 2.3.x: Upgrade to version 2.3.4 or later
  6. 6. For MQ Operator LTS 2.4.x: Upgrade to version 2.4.9 or later
  7. 7. If using MQ Operator CD or SC2 releases, upgrade to a version beyond those listed in the advisory (CD 3.5.2+ or SC2 3.2.11+)
  8. 8. For MQ Advanced Container Images: Upgrade to version 9.2.0.6 or later
Caveat Ensure compatibility of your custom configurations with the new operator version before upgrading in production; review IBM MQ migration guides for any configuration changes required

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

Fix this in Mq Operator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1333 — 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-1333 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