In Eclipse OpenJ9, prior to the 0.12.0 release, the jio_snprintf() and jio_vsnprintf() native methods ignored the length parameter. This affects existing APIs that called the functions to exceed the allocated buffer. This functions were not directly callable by non-native user code.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
| Link | Tags |
|---|---|
| https://access.redhat.com/errata/RHSA-2019:0474 | third party advisory vendor advisory |
| https://bugs.eclipse.org/bugs/show_bug.cgi?id=543659 | issue tracking exploit vendor advisory |
| https://access.redhat.com/errata/RHSA-2019:0469 | third party advisory vendor advisory |
| https://access.redhat.com/errata/RHSA-2019:0473 | third party advisory vendor advisory |
| https://access.redhat.com/errata/RHSA-2019:0472 | third party advisory vendor advisory |
| https://access.redhat.com/errata/RHSA-2019:0640 | third party advisory vendor advisory |
| https://access.redhat.com/errata/RHSA-2019:1238 | vendor advisory |