dbcve.org
Cics TxApplication · Ibm

CVE-2022-31767

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-24
Fix available
A fix is available. Upgrade to 11.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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 CICS TX Standard and Advanced 11.1 could allow a remote attacker to execute arbitrary commands on the system by sending a specially crafted request. IBM X-Force ID: 227980.

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 confidence

IBM CICS TX Standard and Advanced 11.1 contains a command injection vulnerability allowing remote attackers to execute arbitrary commands on the system via specially crafted requests. The lack of input validation in the request handling enables an attacker to inject OS-level commands without authentication.

MitigationApply IBM CICS TX 11.1 patches or upgrade to a patched version as specified in IBM's security bulletin. Restrict network access to CICS TX interfaces until the patch can be applied.

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
Cics TxApplication
Affected:< 11.1= 11.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 IBM CICS TX installation and version
    Locate the IBM CICS TX installation directory and check for version information files, typically found in the product's installation root or bin directory, or use the product's built-in version query command if available.
    Affected if The installed version is 11.1 or any version lower than 11.1.
  2. Verify network-accessible CICS TX interfaces
    Review the CICS TX network configuration to determine if HTTP, HTTPS, or other request-handling interfaces are enabled and bound to network-accessible IP addresses.
    Affected if Network request handling interfaces (HTTP/HTTPS) are enabled and exposed to network traffic.
  3. Check for unauthenticated request endpoints
    Examine the CICS TX configuration files that control request handling to see if authentication is enforced on incoming requests.
    Affected if The request handling component allows unauthenticated access to its interfaces.
  4. Inspect system exposure
    Review firewall rules, network ACLs, or host-based access controls surrounding the CICS TX system to determine if it can be reached by untrusted network sources.
    Affected if The CICS TX system is reachable from untrusted or public networks without proper network segmentation.

A user is affected if they are running IBM CICS TX version 11.1 or earlier with network-accessible request handling interfaces that do not require 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 11.1 or later
Fixed in 11.1
Interim mitigation

Apply IBM CICS TX 11.1 patches or upgrade to a patched version as specified in IBM's security bulletin. Restrict network access to CICS TX interfaces until the patch can be applied.

Recommended fix Moderate confidence

Any CICS TX release greater than 11.1 (e.g., 11.2 or later) - contact IBM for specific fixed version

  1. 1. Identify the current IBM CICS TX version by checking the installation or consulting system documentation
  2. 2. If running version 11.1 or any version below 11.1, plan for an upgrade to a fixed release
  3. 3. Contact IBM Support or access the IBM Fix Central portal to obtain the latest fixed release for CICS TX
  4. 4. Review IBM's upgrade documentation and release notes for CICS TX before proceeding
  5. 5. Schedule a maintenance window and perform a full backup of the current system
  6. 6. Follow IBM's recommended upgrade procedure to install the fixed release
  7. 7. After upgrade, verify the CICS TX version matches the fixed release
  8. 8. Test critical CICS TX functions to ensure the system operates normally post-upgrade
Caveat Review IBM's release notes for the target version for any compatibility considerations or configuration changes required

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

Fix this in Cics Tx Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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