Cics Tx Advanced
Monthly
HTTP request smuggling in IBM WebSphere Application Server and WebSphere Application Server Liberty - as bundled in IBM CICS TX Advanced per the affected CPE - lets remote attackers desynchronize request framing between a front-end intermediary and the WebSphere back end, enabling request tampering or response poisoning. Exploitation requires the server to sit behind a reverse proxy, load balancer, or CDN that parses Content-Length/Transfer-Encoding framing differently than the back end; no authentication or user interaction is needed (PR:N/UI:N), but attack complexity is high (AC:H) because the attacker must find and reliably trigger a specific parser discrepancy in the real deployed chain, and a directly exposed server with no divergent front-end parser is not smuggle-able. Impact is bounded to low confidentiality and integrity with no availability effect (CVSS 3.1 base 4.8); this is a genuine but modest-severity issue rather than a top priority, and no public exploit was identified at time of analysis.
Virtual host isolation bypass in IBM WebSphere Application Server and WebSphere Application Server Liberty, as bundled in IBM CICS TX Advanced 10.1, allows remote requests addressed to one configured virtual host to reach resources belonging to another virtual host on the same instance. The vendor assigns CVSS 3.1 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, CWE-284); our independent assessment keeps the same unauthenticated, low-confidentiality/low-integrity, no-availability profile but raises attack complexity to AC:H because the weakness is only meaningful when an instance is configured to serve multiple distinct virtual hosts, while a default single-virtual-host deployment offers little to bypass. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and a vendor patch is available per the IBM advisory.
HTTP request smuggling in IBM WebSphere Application Server Liberty - the runtime bundled with IBM CICS TX Advanced 10.1 - lets remote, unauthenticated attackers desynchronize HTTP message framing between an upstream HTTP parser and the Liberty backend, so a smuggled request can be processed as if it came from the trusted front-end, with low confidentiality and integrity impact on subsequent requests sharing the connection. Exploitation requires a multi-tier topology (reverse proxy, load balancer, or CDN in front of or behind Liberty) where the two parsers disagree on Content-Length/Transfer-Encoding or chunked framing, and is rated high complexity because the specific parsing gap must be discovered and precisely crafted while connection reuse must be achievable; no user interaction is required. Risk is moderate and consistent with the vendor CVSS of 4.8 (Medium); no public exploit identified at time of analysis, and patch is available from the vendor.
HTTP request smuggling (CWE-444) in IBM WebSphere Application Server 8.5, 9.0, and Liberty lets an authenticated, low-privileged remote attacker desynchronize HTTP request framing between WebSphere and an intermediary so that one user's request boundaries are misattributed on a shared connection. The issue only manifests when WebSphere sits behind or in front of a second HTTP parser (reverse proxy, load balancer, or CDN) that disagrees with WebSphere on Content-Length versus Transfer-Encoding chunked handling; a standalone WebSphere instance with no fronting or backend HTTP hop is not affected, and the 4.2 score reflects high attack complexity, partial confidentiality and integrity impact, and no availability or scope change. No public exploit code and no confirmed active exploitation were identified at time of analysis, and a vendor patch is available per IBM's advisory.
HTTP request smuggling in IBM WebSphere Application Server and WebSphere Application Server Liberty - as bundled in IBM CICS TX Advanced per the affected CPE - lets remote attackers desynchronize request framing between a front-end intermediary and the WebSphere back end, enabling request tampering or response poisoning. Exploitation requires the server to sit behind a reverse proxy, load balancer, or CDN that parses Content-Length/Transfer-Encoding framing differently than the back end; no authentication or user interaction is needed (PR:N/UI:N), but attack complexity is high (AC:H) because the attacker must find and reliably trigger a specific parser discrepancy in the real deployed chain, and a directly exposed server with no divergent front-end parser is not smuggle-able. Impact is bounded to low confidentiality and integrity with no availability effect (CVSS 3.1 base 4.8); this is a genuine but modest-severity issue rather than a top priority, and no public exploit was identified at time of analysis.
Virtual host isolation bypass in IBM WebSphere Application Server and WebSphere Application Server Liberty, as bundled in IBM CICS TX Advanced 10.1, allows remote requests addressed to one configured virtual host to reach resources belonging to another virtual host on the same instance. The vendor assigns CVSS 3.1 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, CWE-284); our independent assessment keeps the same unauthenticated, low-confidentiality/low-integrity, no-availability profile but raises attack complexity to AC:H because the weakness is only meaningful when an instance is configured to serve multiple distinct virtual hosts, while a default single-virtual-host deployment offers little to bypass. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and a vendor patch is available per the IBM advisory.
HTTP request smuggling in IBM WebSphere Application Server Liberty - the runtime bundled with IBM CICS TX Advanced 10.1 - lets remote, unauthenticated attackers desynchronize HTTP message framing between an upstream HTTP parser and the Liberty backend, so a smuggled request can be processed as if it came from the trusted front-end, with low confidentiality and integrity impact on subsequent requests sharing the connection. Exploitation requires a multi-tier topology (reverse proxy, load balancer, or CDN in front of or behind Liberty) where the two parsers disagree on Content-Length/Transfer-Encoding or chunked framing, and is rated high complexity because the specific parsing gap must be discovered and precisely crafted while connection reuse must be achievable; no user interaction is required. Risk is moderate and consistent with the vendor CVSS of 4.8 (Medium); no public exploit identified at time of analysis, and patch is available from the vendor.
HTTP request smuggling (CWE-444) in IBM WebSphere Application Server 8.5, 9.0, and Liberty lets an authenticated, low-privileged remote attacker desynchronize HTTP request framing between WebSphere and an intermediary so that one user's request boundaries are misattributed on a shared connection. The issue only manifests when WebSphere sits behind or in front of a second HTTP parser (reverse proxy, load balancer, or CDN) that disagrees with WebSphere on Content-Length versus Transfer-Encoding chunked handling; a standalone WebSphere instance with no fronting or backend HTTP hop is not affected, and the 4.2 score reflects high attack complexity, partial confidentiality and integrity impact, and no availability or scope change. No public exploit code and no confirmed active exploitation were identified at time of analysis, and a vendor patch is available per IBM's advisory.