CVE-2022-34313

IBM CICS TX 11.1 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can...

CVE-2022-38705

IBM CICS TX 11.1 Standard and Advanced could allow a remote attacker to bypass security restrictions, caused by a reverse tabnabbing flaw. An attacker could exploit this vulnerability and redirect a victim to a phishing site. IBM X-Force ID: 234172...

CVE-2022-34312

IBM CICS TX 11.1 allows web pages to be stored locally which can be read by another user on the system. IBM X-Force ID: 229447...

IBM CICS TX 加密问题漏洞

IBM CICS TX is a comprehensive, single transaction runtime package from International Business Machines IBM. IBM CICS TX version 11.7 is vulnerable to an encryption issue that stems from the use of a weaker-than-expected encryption algorithm, which could be exploited by an attacker to decrypt...

Tx should revert when the call in _returnDust failed

Lines of code Vulnerability details Impact User may lose remaining ETH of the transaction Proof of Concept As the returned status of the call in returnDust is ignored, the tx will success even if the call failed, which means the caller does not get his ETH back. Tools Used n/a Recommended...

CVE-2022-33909: Time-of-check Time-of-use (TOCTOU) Race Condition

DMA transactions which are targeted at input buffers used for the HddPassword software SMI handler could cause SMRAM corruption through a TOCTOU attack. DMA transactions which are targeted at input buffers used for the software SMI handler used by the HddPassword driver could cause SMRAM corrupti...

PT-2022-34940 · Linux · Linux Kernel

Name of the Vulnerable Software and Affected Versions: Linux Kernel versions prior to v6.0.6 Description: The issue is related to a potential security vulnerability in the cifs ses add channel function, which may cause an xid leak. The actual impact and attack plausibility have not yet been prove...

PT-2022-34942 · Linux · Linux Kernel

Name of the Vulnerable Software and Affected Versions: Linux Kernel versions prior to v6.0.6 Description: The issue is related to a potential security problem in the cifs copy file range function, which may cause an xid leak. The actual impact and attack plausibility have not yet been proven...

PT-2022-22130 · Ibm · Ibm Cics Tx

Name of the Vulnerable Software and Affected Versions: IBM CICS TX version 11.1 Description: The issue is related to the use of weaker than expected cryptographic algorithms, which could allow an attacker to decrypt highly sensitive information. Recommendations: For IBM CICS TX version 11.1, upda...

CVE-2022-34325: Time-of-check Time-of-use (TOCTOU) Race Condition

DMA transactions which are targeted at input buffers used for the StorageSecurityCommandDxe software SMI handler could cause SMRAM corruption through a TOCTOU attack. DMA transactions which are targeted at input buffers used for the software SMI handler used by the StorageSecurityCommandDxe drive...

PT-2022-22124 · Ibm · Ibm Cics Tx

Name of the Vulnerable Software and Affected Versions: IBM CICS TX version 11.1 Description: The issue allows users to embed arbitrary JavaScript code in the Web UI, altering the intended functionality and potentially leading to credentials disclosure within a trusted session. Recommendations: Fo...

IBM CICS TX 安全漏洞

IBM CICS TX is a comprehensive, single transaction runtime package from International Business Machines IBM. A security vulnerability exists in IBM CICS TX version 11.1 that stems from not or incorrectly escaping Web script syntax in HTTP headers that can be used by Web browser components that ca...

_returnDust doesn't check the return value after call

Lines of code Vulnerability details Impact returnDust doesn't check that the call has been sucesfully. For example, if the buyer is a contract could fail during the reception but due to returnDust doesn't check the return value to revert the transaction in case of failure the tokens could be...

IBM CICS TX 信息泄露漏洞

IBM CICS TX is a comprehensive, single transaction runtime package from International Business Machines IBM. An information disclosure vulnerability exists in IBM CICS TX version 11.1 that stems from an insecure privilege setting that could disclose sensitive information to local users...

IBM CICS TX 跨站脚本漏洞

IBM CICS TX is a comprehensive, single transaction runtime package from International Business Machines IBM. A cross-site scripting vulnerability exists in IBM CICS TX version 11.1 that stems from vulnerability to cross-site scripting...

PT-2022-22125 · Ibm · Ibm Cics Tx

Name of the Vulnerable Software and Affected Versions: IBM CICS TX version 11.1 Description: The issue concerns the failure to properly neutralize web scripting syntax in HTTP headers, which can be processed by web browser components. Recommendations: For IBM CICS TX version 11.1, update to a...

IBM CICS TX 安全漏洞

IBM CICS TX is a comprehensive, single transaction runtime package from International Business Machines IBM. A security vulnerability exists in IBM CICS TX 11.1 Standard and Advanced, which stems from the fact that it allows a remote attacker to bypass security restrictions caused by a reverse ta...

IBM CICS TX 信息泄露漏洞

IBM CICS TX is a comprehensive, single transaction runtime package from International Business Machines IBM. An information disclosure vulnerability exists in IBM CICS TX version 11.7, which stems from the potential disclosure of sensitive information in HTTP response headers...

IBM CICS TX 安全漏洞

IBM CICS TX is a comprehensive, single transaction runtime package from International Business Machines IBM. IBM CICS TX version 11.1 is vulnerable to an information disclosure vulnerability that stems from not setting security properties on authorization tokens or session cookies. An attacker...

It is possible for a user's ETH to be trapped inside the contracts.

Lines of code Vulnerability details Impact It is possible that a user's ETH will be trapped inside the contracts. returnETHIfAnyoriginator; But in the implementation of the returnETHIfAny function, it will just silently return even the returning ETH transaction fails. As a result, even if the use...