dbcve.org
Security Verify Information QueueApplication · Ibm

CVE-2024-47120

MEDIUM · 6.8 CVSS v3.1 Published 2025-09-10
Fix available
A fix is available. Upgrade to 10.0.11 or later.
See remediation →
70/100
Remediation priority · Elevated
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 Security Verify Information Queue 10.0.5, 10.0.6, 10.0.7, and 10.0.8 could allow a privileged user to escalate their privileges and attack surface on the host due to the containers running with unnecessary privileges.

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 Security Verify Information Queue versions 10.0.5 through 10.0.8 run in Docker containers with excessive privileges (potentially privileged mode or unnecessary Linux capabilities). A privileged user with container access can exploit this misconfiguration to escape container isolation and escalate privileges on the underlying host system.

MitigationRedeploy containers with least-privilege security contexts: run as non-root user, drop all unnecessary capabilities, avoid privileged mode, use read-only root filesystems where possible, and apply appropriate pod security standards.

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
Security Verify Information QueueApplication
Affected:>= 10.0.5, < 10.0.11

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

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

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 running IBM Security Verify Information Queue container
    Run 'docker ps -a --filter "name=verify-information-queue"' or 'kubectl get pods -A | grep -i verify' to find the container
    Affected if No container found means not affected; if container exists, continue to version check
  2. Check installed container version
    Run 'docker inspect <container_id> --format "{{.Config.Image}}"' or 'kubectl get pod <pod_name> -o jsonpath="{.spec.containers[*].image}"' to get the image version tag
    Affected if Version is 10.0.5 through 10.0.8 (or image tag contains 10.0.5-10.0.8 range) indicates potentially affected version
  3. Check if container runs in privileged mode
    Run 'docker inspect <container_id> --format "{{.HostConfig.Privileged}}"' or check pod spec: 'kubectl get pod <pod_name> -o jsonpath="{.spec.containers[*].securityContext.privileged}"'
    Affected if Returns 'true' indicates the container is running in privileged mode and is affected by this vulnerability
  4. Check granted Linux capabilities
    Run 'docker inspect <container_id> --format "{{.HostConfig.CapAdd}}"' or check pod spec: 'kubectl get pod <pod_name> -o jsonpath="{.spec.containers[*].securityContext.capabilities.add}"'
    Affected if Output includes CAP_SYS_ADMIN, CAP_NET_ADMIN, or other elevated capabilities indicates excessive privileges; compare against least-privilege requirements
  5. Check container user execution context
    Run 'docker exec <container_id> id' or check pod spec: 'kubectl get pod <pod_name> -o jsonpath="{.spec.securityContext.runAsUser}"'
    Affected if Container runs as root (uid 0) or runAsUser is 0 or not set indicates elevated privilege context

If the container version is 10.0.5-10.0.8 AND it runs in privileged mode OR with elevated capabilities OR as root, the environment is affected by this container escape vulnerability.

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 10.0.11 or later
Fixed in 10.0.11
Interim mitigation

Redeploy containers with least-privilege security contexts: run as non-root user, drop all unnecessary capabilities, avoid privileged mode, use read-only root filesystems where possible, and apply appropriate pod security standards.

Recommended fix Moderate confidence

IBM Security Verify Information Queue 10.0.11 or later

  1. Back up the current IBM Security Verify Information Queue installation and configuration data
  2. Review IBM's official upgrade documentation for Security Verify Information Queue
  3. Upgrade IBM Security Verify Information Queue from the current affected version (10.0.5-10.0.10) to version 10.0.11 or later
  4. After upgrade, verify the container runtime configuration no longer includes unnecessary privileges
  5. Confirm the upgrade was successful by checking the product version and running basic functionality tests

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

Fix this in Security Verify Information Queue Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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