CICS TX Standard: Use of Inherently Dangerous Function
CVE-2025-1331 is a high-severity use of inherently dangerous function vulnerability in CICS TX Standard from IBM, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected CICS TX Standard versions: 11.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.28% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of CICS TX Standard you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on ibm.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| IBM | CICS TX Standard | 11.1 | Not stated |
| IBM | CICS TX Advanced | 10.1; 11.1 | Not stated |
| IBM | Cics Tx | 11.1.0.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (us.ibm.com).
Official description
IBM CICS TX Standard 11.1 and IBM CICS TX Advanced 10.1 and 11.1 could allow a local user to execute arbitrary code on the system due to the use of unsafe use of the gets function.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Inherently Dangerous Function
The product calls a function that can never be guaranteed to work safely, regardless of how it is used.
How developers prevent this class of flaw
- Identify a list of prohibited API functions and prohibit developers from using these functions, providing safer alternatives. In some cases, automatic code analysis tools or the compiler can be instructed to spot use of prohibited functions, such as the banned.h include file from Microsoft's SDL.
- Use grep or static analysis tools to spot usage of dangerous functions.
More Use of Inherently Dangerous Function vulnerabilities (CWE-242)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in CICS TX Standard
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Recent Use of Inherently Dangerous Function vulnerabilities
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.