Download
Security Advisory; NCSC-2026-0431 [1.0.0]
- Security Advisory
- NCSC-2026-0431 [1.0.0]
- Publicatie
- 16-10-2026 08:16 (Europe/Amsterdam)
- Prioriteit
- Normaal
- Betreft
- Kwetsbaarheden verholpen in IBM DataPower Gateway en onderliggende componenten
Kenmerken
- Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
- XML Injection (aka Blind XPath Injection)
- Improper Neutralization of CRLF Sequences ('CRLF Injection')
- Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
- Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
- Stack-based Buffer Overflow
- Heap-based Buffer Overflow
- Write-what-where Condition
- Buffer Underwrite ('Buffer Underflow')
- Out-of-bounds Read
- Buffer Over-read
- Improper Handling of Length Parameter Inconsistency
- Incorrect Calculation of Buffer Size
- Improper Null Termination
- Encoding Error
- Improper Handling of Case Sensitivity
- Incorrect Behavior Order: Early Validation
- Partial String Comparison
- Integer Overflow or Wraparound
- Integer Underflow (Wrap or Wraparound)
- Off-by-one Error
- Observable Timing Discrepancy
- Uncaught Exception
- Use of Hard-coded Password
- Incorrect Privilege Assignment
- Improper Handling of Insufficient Permissions or Privileges
- Improper Certificate Validation
- Improper Validation of Certificate with Host Mismatch
- Origin Validation Error
- Improper Verification of Cryptographic Signature
- Improper Validation of Integrity Check Value
- Improperly Implemented Security Check for Standard
- Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
- Signal Handler Race Condition
- Race Condition within a Thread
- Time-of-check Time-of-use (TOCTOU) Race Condition
- Detection of Error Condition Without Action
- Missing Release of Memory after Effective Lifetime
- Improper Resource Shutdown or Release
- Asymmetric Resource Consumption (Amplification)
- Inefficient Algorithmic Complexity
- Improper Resource Locking
- Double Free
- Use After Free
- Missing Handler
- Incomplete Cleanup
- Undefined Behavior for Input to API
- NULL Pointer Dereference
- Deserialization of Untrusted Data
- Unchecked Input for Loop Condition
- Improper Restriction of XML External Entity Reference
- Reachable Assertion
- Null Byte Interaction Error (Poison Null Byte)
- Uncontrolled Recursion
- Incorrect Behavior Order
- Reliance on Undefined, Unspecified, or Implementation-Defined Behavior
- Mismatched Memory Management Routines
- Release of Invalid Pointer or Reference
- Allocation of Resources Without Limits or Throttling
- Missing Release of Resource after Effective Lifetime
- Out-of-bounds Write
- Memory Allocation with Excessive Size Value
- Buffer Access with Incorrect Length Value
- Missing Synchronization
- Incorrect Synchronization
- Untrusted Pointer Dereference
- Access of Uninitialized Pointer
- Expired Pointer Dereference
- Deadlock
- Loop with Unreachable Exit Condition ('Infinite Loop')
- Inappropriate Encoding for Output Context
- Access of Resource Using Incompatible Type ('Type Confusion')
- Incorrect Authorization
- Use of Uninitialized Resource
- Missing Initialization of Resource
- Improper Update of Reference Count
- Improper Validation of Specified Quantity in Input
- Improper Validation of Specified Index, Position, or Offset in Input
- Improper Validation of Syntactic Correctness of Input
- Improper Validation of Specified Type of Input
- Improper Validation of Consistency within Input
- Inefficient Regular Expression Complexity
- Multiple Releases of Same Resource or Handle
Omschrijving
IBM heeft meerdere beveiligingsproblemen opgelost in DataPower Gateway versies 10.5 tot 11.0 en een veelvoud aan onderliggende subcomponenten.
De kwetsbaarheden betreffen een breed scala aan problemen zoals use-after-free bugs, race conditions, buffer overflows, null pointer dereferences, integer overflows, geheugenlekken, onjuiste validatie, en cryptografische fouten.
Een kwaadwillende kan de kwetsbaarheden misbruiken om aanvallen uit te voeren die remote code execution, denial of service, cross-site scripting, en bypass van autorisatie mogelijk maken, waarbij sommige aanvallen authenticatie vereisen en andere niet.
Naast de kwetsbaarheden in DataPower Gateway heeft IBM ook een veelvoud aan kwetsbaarheden verholpen in onderliggende subcomponenten. Voor deze onderliggende subcomponenten zijn eerder updates verschenen voor de individuele systemen. IBM heeft deze updates nu verwerkt in de eigen software stack van DataPower Gateway.
Oplossingen
IBM heeft patches beschikbaar gesteld voor de DataPower Gateway-productlijn. Zie bijgevoegde referenties voor meer informatie.
Referenties
- https://www.ibm.com/support/pages/node/7289776
- https://www.ibm.com/support/pages/node/7289778
- https://www.ibm.com/support/pages/node/7289779
- https://www.ibm.com/support/pages/node/7289780
- https://www.ibm.com/support/pages/node/7289783
- https://www.ibm.com/support/pages/node/7289785
- https://www.ibm.com/support/pages/node/7289789
- https://www.ibm.com/support/pages/node/7289790
- https://www.ibm.com/support/pages/node/7289798
CVE's
- CVE-2023-53781 - CVSS (v3) 7.8
- CVE-2025-14087 - CVSS (v3) 5.6
- CVE-2025-14512 - CVSS (v3) 6.5
- CVE-2025-21858 - CVSS (v4) 8.5
- CVE-2025-22105 - CVSS (v3) 5.5
- CVE-2025-37980 - CVSS (v3) 5.5
- CVE-2025-38015 - CVSS (v3) 7.0
- CVE-2025-38097 - CVSS (v3) 7.8
- CVE-2025-38180 - CVSS (v4) 8.5
- CVE-2025-38400 - CVSS (v3) 5.5
- CVE-2025-38405 - CVSS (v3) 7.5
- CVE-2025-38441 - CVSS (v3) 5.5
- CVE-2025-38470 - CVSS (v3) 7.8
- CVE-2025-38653 - CVSS (v3) 7.8
- CVE-2025-39766 - CVSS (v4) 4.8
- CVE-2025-39797 - CVSS (v3) 7.8
- CVE-2025-39866 - CVSS (v4) 7.3
- CVE-2025-40134 - CVSS (v3) 7.0
- CVE-2025-48431 - CVSS (v3) 7.5
- CVE-2025-5278 - CVSS (v3) 4.4
- CVE-2025-68183 - CVSS (v3) 7.8
- CVE-2025-68211 - CVSS (v3) 7.0
- CVE-2025-68214 - CVSS (v3) 5.5
- CVE-2025-68347 - CVSS (v3) 7.8
- CVE-2025-68366 - CVSS (v3) 7.1
- CVE-2025-68724 - CVSS (v3) 7.8
- CVE-2025-71066 - CVSS (v3) 9.8
- CVE-2025-71089 - CVSS (v4) 7.3
- CVE-2026-12143 - CVSS (v4) 8.7
- CVE-2026-13257 - CVSS (v3) 6.5
- CVE-2026-13258 - CVSS (v3) 5.4
- CVE-2026-13757 - CVSS (v3) 6.2
- CVE-2026-14269 - CVSS (v3) 9.8
- CVE-2026-14273 - CVSS (v3) 6.5
- CVE-2026-14496 - CVSS (v3) 8.2
- CVE-2026-14497 - CVSS (v3) 8.1
- CVE-2026-14502 - CVSS (v3) 9.8
- CVE-2026-14507 - CVSS (v3) 7.7
- CVE-2026-14508 - CVSS (v3) 6.5
- CVE-2026-14509 - CVSS (v3) 5.9
- CVE-2026-14888 - CVSS (v3) 8.1
- CVE-2026-14905 - CVSS (v3) 8.2
- CVE-2026-14988 - CVSS (v3) 6.5
- CVE-2026-14990 - CVSS (v3) 9.3
- CVE-2026-14991 - CVSS (v3) 9.8
- CVE-2026-14992 - CVSS (v3) 9.8
- CVE-2026-14999 - CVSS (v3) 7.4
- CVE-2026-15588 - CVSS (v3) 5.3
- CVE-2026-15762 - CVSS (v3) 9.8
- CVE-2026-15781 - CVSS (v3) 8.0
- CVE-2026-15784 - CVSS (v3) 8.1
- CVE-2026-15819 - CVSS (v3) 7.5
- CVE-2026-15822 - CVSS (v3) 7.5
- CVE-2026-15824 - CVSS (v3) 8.2
- CVE-2026-16111 - CVSS (v3) 7.5
- CVE-2026-16159 - CVSS (v3) 8.6
- CVE-2026-16161 - CVSS (v3) 7.5
- CVE-2026-16163 - CVSS (v3) 8.6
- CVE-2026-16164 - CVSS (v3) 7.5
- CVE-2026-16165 - CVSS (v3) 7.5
- CVE-2026-16167 - CVSS (v3) 7.5
- CVE-2026-16169 - CVSS (v3) 7.5
- CVE-2026-16170 - CVSS (v3) 7.5
- CVE-2026-16176 - CVSS (v3) 7.5
- CVE-2026-16177 - CVSS (v3) 5.3
- CVE-2026-16178 - CVSS (v3) 7.5
- CVE-2026-16179 - CVSS (v3) 7.5
- CVE-2026-16181 - CVSS (v3) 7.4
- CVE-2026-16182 - CVSS (v3) 5.9
- CVE-2026-16340 - CVSS (v3) 9.8
- CVE-2026-16439 - CVSS (v4) 5.8
- CVE-2026-16440 - CVSS (v4) 5.7
- CVE-2026-16441 - CVSS (v4) 6.9
- CVE-2026-2100 - CVSS (v3) 7.5
- CVE-2026-22979 - CVSS (v3) 5.5
- CVE-2026-22984 - CVSS (v4) 8.2
- CVE-2026-22990 - CVSS (v3) 7.5
- CVE-2026-23002 - CVSS (v3) 5.5
- CVE-2026-23060 - CVSS (v3) 7.0
- CVE-2026-23110 - CVSS (v3) 5.5
- CVE-2026-23204 - CVSS (v3) 7.3
- CVE-2026-23209 - CVSS (v4) 7.3
- CVE-2026-23216 - CVSS (v4) 9.2
- CVE-2026-23243 - CVSS (v3) 7.8
- CVE-2026-23270 - CVSS (v3) 7.8
- CVE-2026-23392 - CVSS (v4) 7.3
- CVE-2026-23455 - CVSS (v4) 8.7
- CVE-2026-2391 - CVSS (v4) 6.3
- CVE-2026-31411 - CVSS (v3) 7.1
- CVE-2026-31419 - CVSS (v4) 7.3
- CVE-2026-31488 - CVSS (v4) 7.3
- CVE-2026-31508 - CVSS (v3) 7.8
- CVE-2026-31532 - CVSS (v4) 7.3
- CVE-2026-31581 - CVSS (v4) 5.2
- CVE-2026-31607 - CVSS (v4) 8.7
- CVE-2026-31613 - CVSS (v4) 7.1
- CVE-2026-31669 - CVSS (v4) 7.3
- CVE-2026-31677 - CVSS (v3) 5.5
- CVE-2026-31684 - CVSS (v3) 7.1
- CVE-2026-31685 - CVSS (v4) 6.8
- CVE-2026-33845 - CVSS (v3) 9.1
- CVE-2026-33846 - CVSS (v3) 7.5
- CVE-2026-3832 - CVSS (v3) 3.7
- CVE-2026-3833 - CVSS (v3) 7.4
- CVE-2026-4046 - CVSS (v3) 7.5
- CVE-2026-41254 - CVSS (v3) 7.5
- CVE-2026-41602 - CVSS (v3) 7.5
- CVE-2026-41606 - CVSS (v3) 7.5
- CVE-2026-41607 - CVSS (v3) 9.1
- CVE-2026-42009 - CVSS (v3) 7.5
- CVE-2026-42010 - CVSS (v3) 9.8
- CVE-2026-42011 - CVSS (v3) 7.4
- CVE-2026-42012 - CVSS (v3) 7.1
- CVE-2026-42013 - CVSS (v3) 8.2
- CVE-2026-42014 - CVSS (v3) 6.6
- CVE-2026-42015 - CVSS (v3) 5.3
- CVE-2026-43027 - CVSS (v3) 7.8
- CVE-2026-43037 - CVSS (v4) 9.2
- CVE-2026-43038 - CVSS (v4) 9.3
- CVE-2026-43056 - CVSS (v3) 7.8
- CVE-2026-43074 - CVSS (v4) 7.3
- CVE-2026-43116 - CVSS (v4) 7.3
- CVE-2026-43125 - CVSS (v4) 9.2
- CVE-2026-43163 - CVSS (v3) 7.0
- CVE-2026-43190 - CVSS (v4) 6.3
- CVE-2026-43198 - CVSS (v4) 8.2
- CVE-2026-43260 - CVSS (v3) 7.8
- CVE-2026-43284 - CVSS (v3) 8.8
- CVE-2026-43303 - CVSS (v3) 7.8
- CVE-2026-43329 - CVSS (v4) 7.3
- CVE-2026-43499 - CVSS (v4) 8.5
- CVE-2026-43501 - CVSS (v4) 9.3
- CVE-2026-43868 - CVSS (v3) 7.5
- CVE-2026-43870 - CVSS (v3) 9.8
- CVE-2026-4437 - CVSS (v3) 7.5
- CVE-2026-4438 - CVSS (v3) 5.9
- CVE-2026-45852 - CVSS (v4) 7.3
- CVE-2026-46054 - CVSS (v3) 7.5
- CVE-2026-46086 - CVSS (v3) 7.0
- CVE-2026-46116 - CVSS (v3) 7.8
- CVE-2026-46173 - CVSS (v3) 7.8
- CVE-2026-46181 - CVSS (v3) 7.8
- CVE-2026-46242 - CVSS (v4) 7.3
- CVE-2026-46259 - CVSS (v4) 7.3
- CVE-2026-46300 - CVSS (v3) 7.8
- CVE-2026-46331 - CVSS (v4) 8.5
- CVE-2026-46333 - CVSS (v3) 7.8
- CVE-2026-46917 - CVSS (v3) 5.3
- CVE-2026-46968 - CVSS (v3) 5.9
- CVE-2026-47010 - CVSS (v3) 3.7
- CVE-2026-47021 - CVSS (v3) 5.3
- CVE-2026-47027 - CVSS (v3) 5.3
- CVE-2026-47059 - CVSS (v3) 3.7
- CVE-2026-47063 - CVSS (v3) 7.5
- CVE-2026-48144 - CVSS (v4) 9.1
- CVE-2026-48145 - CVSS (v4) 8.2
- CVE-2026-5260 - CVSS (v3) 8.2
- CVE-2026-52923 - CVSS (v3) 7.8
- CVE-2026-52991 - CVSS (v3) 9.8
- CVE-2026-53006 - CVSS (v4) 8.2
- CVE-2026-53009 - CVSS (v3) 9.8
- CVE-2026-53131 - CVSS (v4) 6.9
- CVE-2026-53189 - CVSS (v4) 2.0
- CVE-2026-53264 - CVSS (v4) 7.3
- CVE-2026-53266 - CVSS (v4) 7.3
- CVE-2026-5419 - CVSS (v3) 3.7
- CVE-2026-5450 - CVSS (v3) 9.8
- CVE-2026-55602 - CVSS (v4) 6.9
- CVE-2026-55603 - CVSS (v3) 7.5
- CVE-2026-55968 - CVSS (v4) 8.7
- CVE-2026-55970 - CVSS (v4) 6.9
- CVE-2026-58010 - CVSS (v3) 8.2
- CVE-2026-58011 - CVSS (v3) 7.5
- CVE-2026-58012 - CVSS (v3) 8.2
- CVE-2026-58013 - CVSS (v3) 8.2
- CVE-2026-58014 - CVSS (v3) 8.6
- CVE-2026-58015 - CVSS (v3) 7.5
- CVE-2026-58016 - CVSS (v3) 9.1
- CVE-2026-58662 - CVSS (v4) 8.7
- CVE-2026-59879 - CVSS (v4) 8.7
- CVE-2026-59880 - CVSS (v4) 8.7
- CVE-2026-60147 - CVSS (v3) 6.5
- CVE-2026-60589 - CVSS (v3) 3.7
- CVE-2026-61308 - CVSS (v3) 6.8
- CVE-2026-63913 - CVSS (v3) 8.2
- CVE-2026-63952 - CVSS (v3) 8.4
- CVE-2026-64017 - CVSS (v3) 9.8
- CVE-2026-64530 - CVSS (v3) 9.8
- CVE-2026-64560 - CVSS (v3) 7.8
- CVE-2026-70906 - CVSS (v3) 7.5
- CVE-2026-70907 - CVSS (v3) 5.3
- CVE-2026-74581 - CVSS (v3) 9.8
- CVE-2026-82417 - CVSS (v4) 6.3
- CVE-2026-82562 - CVSS (v4) 6.3
- CVE-2026-83605 - CVSS (v4) 8.7
- CVE-2026-83607 - CVSS (v4) 8.7
- CVE-2026-83608 - CVSS (v4) 8.7
- CVE-2026-83613 - CVSS (v4) 8.7
- CVE-2026-83614 - CVSS (v4) 8.7
- CVE-2026-83615 - CVSS (v4) 8.7
- CVE-2026-83616 - CVSS (v4) 8.7
- CVE-2026-83619 - CVSS (v4) 8.7
Producten
IBM
Disclaimer
The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this page to enhance access to its information and security advisories. The use of this security advisory is subject to the following terms and conditions: NCSC-NL makes every reasonable effort to ensure that the content of this page is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or continuous keeping up-to-date. The information contained in this security advisory is intended solely for the purpose of providing general information to professional users. No rights can be derived from the information provided therein. NCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of this security advisory. This includes damage resulting from the inaccuracy of incompleteness of the information contained in the advisory. This security advisory is subject to Dutch law. All disputes related to or arising from the use of this advisory will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings.