dbcve.org
Txseries For MultiplatformsApplication · Ibm

CVE-2024-41742

HIGH · 7.5 CVSS v3.1 Published 2025-01-19
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 TXSeries for Multiplatforms 10.1 is vulnerable to a denial of service, caused by improper enforcement of the timeout on individual read operations. By conducting a slowloris-type attacks, a remote attacker could exploit this vulnerability to cause a denial of service.

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 TXSeries for Multiplatforms 10.1 lacks proper timeout enforcement on individual read operations, allowing attackers to send partial HTTP requests slowly and hold connections open indefinitely. This exhausts server resources by keeping many concurrent connections in a waiting state, similar to slowloris attacks.

MitigationConfigure appropriate read/socket timeouts at the CICS region or network level in IBM TXSeries to abort connections that stall during read operations, preventing resource exhaustion from slowloris-style attacks.

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
Txseries For MultiplatformsApplication
Affected:= 10.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Verify IBM TXSeries for Multiplatforms version
    Run 'lsitab -a | grep cics' or check TXSeries installation directory for version file, or use 'cicslssr -V' command to confirm installed version is exactly 10.1
    Affected if Installed version equals 10.1
  2. Identify active CICS regions with HTTP listeners
    Check /var/cics_regions/ for region directories, then inspect each region's configuration files (cicstcb.ini or region .properties) for EnableHTTP=YES or similar HTTP listener settings
    Affected if Any CICS region has HTTP listener enabled and exposed to network
  3. Check read/socket timeout configuration
    Examine CICS region environment files or TCP/IP stack settings for SO_RCVTIMEO or CICS-specific timeout parameters. Look in /var/cics_regions/<region>/ configuration for 'ReadTimeout', 'SocketTimeout', or 'ClientReadTimeout' settings
    Affected if No read timeout is configured, or timeout is set to 0/unlimited, on the CICS region or its associated TCP listener
  4. Audit current connection states
    Use 'netstat -an | grep <http_port>' or 'ss -an | grep <http_port>' to inspect established and time-wait connections on ports used by CICS regions
    Affected if Large number of connections in ESTABLISHED or TIME-WAIT state with little activity, indicating connection hoarding
  5. Review network-level timeout settings
    Check /etc/sysctl.conf for TCP keepalive settings, and any load balancer or reverse proxy configuration in front of TXSeries for timeout values
    Affected if No network-level timeout or keepalive is enforced on traffic destined to CICS HTTP ports

Environment is affected if IBM TXSeries for Multiplatforms version 10.1 is installed with HTTP listeners enabled and no read/socket timeouts are configured at the CICS region or network level.

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

Configure appropriate read/socket timeouts at the CICS region or network level in IBM TXSeries to abort connections that stall during read operations, preventing resource exhaustion from slowloris-style attacks.

Recommended fix Moderate confidence

IBM TXSeries for Multiplatforms latest fix pack (contact IBM support or visit IBM Fix Central for version 10.1.x)

  1. 1. Identify the current IBM TXSeries for Multiplatforms version using 'lsmq -v' or checking installation directory
  2. 2. Contact IBM support or visit IBM Fix Central to obtain the latest security patches for TXSeries 10.1
  3. 3. Apply the IBM security patch following the standard TXSeries maintenance procedures
  4. 4. Verify the patch was applied successfully by checking the version again
  5. 5. Test that the application functions normally after patching
  6. 6. Implement network-level rate limiting or web application firewall rules as an additional mitigation until the patch is applied
Caveat Check IBM documentation for any migration notes between fix packs; test in non-production environment first

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

Fix this in Txseries For Multiplatforms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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 locally
dbcve dependency scanner

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