IBM Cloud Pak for Business Automation 25.0.0 through 25.0.0 Interim Fix 002, 24.0.1 through 24.0.1 Interim Fix 005, and 24.0.0 through 24.0.0 Interim Fix 007 could allow an authenticated user to cause a denial of service or corrupt existing data due to the improper validation of input length.
Weakness
The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Cloud_pak_for_business_automation | Ibm | 24.0.0 (including) | 24.0.0 (including) |
| Cloud_pak_for_business_automation | Ibm | 24.0.0-interim_fix_001 (including) | 24.0.0-interim_fix_001 (including) |
| Cloud_pak_for_business_automation | Ibm | 24.0.0-interim_fix_002 (including) | 24.0.0-interim_fix_002 (including) |
| Cloud_pak_for_business_automation | Ibm | 24.0.1 (including) | 24.0.1 (including) |
| Cloud_pak_for_business_automation | Ibm | 24.0.1-interim_fix_001 (including) | 24.0.1-interim_fix_001 (including) |
| Cloud_pak_for_business_automation | Ibm | 24.0.1-interim_fix_002 (including) | 24.0.1-interim_fix_002 (including) |
| Cloud_pak_for_business_automation | Ibm | 24.0.1-interim_fix_004 (including) | 24.0.1-interim_fix_004 (including) |
| Cloud_pak_for_business_automation | Ibm | 24.0.1-interim_fix_005 (including) | 24.0.1-interim_fix_005 (including) |
| Cloud_pak_for_business_automation | Ibm | 25.0.0 (including) | 25.0.0 (including) |
| Cloud_pak_for_business_automation | Ibm | 25.0.0-interim_fix_001 (including) | 25.0.0-interim_fix_001 (including) |
| Cloud_pak_for_business_automation | Ibm | 25.0.0-interim_fix_002 (including) | 25.0.0-interim_fix_002 (including) |
Extended Description
Specified quantities include size, length, frequency, price, rate, number of operations, time, and others. Code may rely on specified quantities to allocate resources, perform calculations, control iteration, etc.
Potential Mitigations
- Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.