dbcve.org
Cics Transaction GatewayApplication · Ibm

CVE-2023-50310

HIGH · 7.5 CVSS v3.1 Published 2024-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Transaction Gateway for Multiplatforms 9.2 and 9.3 transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

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 CICS Transaction Gateway for Multiplatforms versions 9.2 and 9.3 stores or transmits authentication credentials using an insecure method susceptible to interception or retrieval. This indicates credentials may be stored in plaintext, use weak encryption, or be transmitted over unencrypted channels.

MitigationImplement strong encryption (e.g., AES-256) for stored credentials and enforce TLS/SSL for all credential transmission. Replace any weak or custom encryption with industry-standard secure credential handling mechanisms.

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 Transaction GatewayApplication
Affected:= 9.2= 9.3

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
None
Availability
None

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

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

  1. Identify IBM CICS Transaction Gateway installed version
    Run the CTG version command (ctgversion) or check the installation directory for version information
    Affected if Installed version is 9.2 or 9.3
  2. Locate credential storage configuration
    Search configuration files (such as ctg.ini, gateway properties, or user registry files) for credential storage settings and encryption parameters
    Affected if Credentials are stored in plaintext, use weak encryption algorithms, or lack proper encryption configuration
  3. Check credential transmission protocol settings
    Examine network and connection configuration for how credentials are transmitted between components
    Affected if Credential transmission occurs over unencrypted channels or uses weak transport security
  4. Review encryption algorithm configuration
    Inspect security configuration files for defined encryption algorithms used for credential protection
    Affected if No encryption is specified, weak algorithms (such as DES, 3DES, or proprietary methods) are in use, or AES-256 is not configured

Environment is affected if IBM CICS Transaction Gateway version is 9.2 or 9.3 and credentials are stored or transmitted using insecure methods including plaintext, weak encryption, or unencrypted channels

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strong encryption (e.g., AES-256) for stored credentials and enforce TLS/SSL for all credential transmission. Replace any weak or custom encryption with industry-standard secure credential handling mechanisms.

Recommended fix Moderate confidence

IBM CICS Transaction Gateway for Multiplatforms - obtain the fixed release version from IBM security bulletin (typically a later fix pack or version beyond 9.3)

  1. Check IBM's official security bulletin for CVE-2023-50310 at www.ibm.com for the specific APAR (Authorized Program Analysis Report) number and interim fix details.
  2. Apply the IBM interim fix (PTF) or upgrade to a fixed release version as specified in the IBM security bulletin.
  3. Verify the fix by reviewing the CICS Transaction Gateway configuration to ensure credentials are now protected using secure methods (e.g., encryption, secure storage).
Caveat Review IBM's fix documentation for any configuration changes required or potential compatibility considerations with your existing setup

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

Fix this in Cics Transaction Gateway Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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