← Back

Communications Eagle

communications_eagle

Vendor: Oracle • 4 CVEs

CVEs (4)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
2Oracle
Windriver
2Communications Eagle
Vxworks
Nov 21, 2024
May 12, 2021
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
An issue was discovered in Wind River VxWorks 7. The memory allocator has a possible integer overflow in calculating a memory block's size to be allocated by calloc(). As a result, the actual memory allocated is smaller...Show more
An issue was discovered in Wind River VxWorks 7. The memory allocator has a possible integer overflow in calculating a memory block's size to be allocated by calloc(). As a result, the actual memory allocated is smaller than the buffer size specified by the arguments, leading to memory corruption.Show less
2Oracle
Windriver
2Communications Eagle
Vxworks
Nov 21, 2024
Feb 3, 2021
N/A· v4
7.3 HIGH· v3
7.5 HIGH· v2
In Wind River VxWorks, memory allocator has a possible overflow in calculating the memory block's size to be allocated by calloc(). As a result, the actual memory allocated is smaller than the buffer size specified by th...Show more
In Wind River VxWorks, memory allocator has a possible overflow in calculating the memory block's size to be allocated by calloc(). As a result, the actual memory allocated is smaller than the buffer size specified by the arguments, leading to memory corruption.Show less
6Belden
NetappOracle+3 more
13Communications Eagle
E Series Santricity Os ControllerGarrettcom Magnum Dx940e Firmware+10 more
Nov 21, 2024
Aug 9, 2019
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
Wind River VxWorks 6.7 though 6.9 and vx7 has a Buffer Overflow in the TCP component (issue 3 of 4). This is an IPNET security vulnerability: TCP Urgent Pointer state confusion during connect() to a remote host.
6Belden
NetappOracle+3 more
13Communications Eagle
E Series Santricity Os ControllerGarrettcom Magnum Dx940e Firmware+10 more
Nov 21, 2024
Aug 9, 2019
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
Wind River VxWorks 6.9 and vx7 has a Buffer Overflow in the TCP component (issue 2 of 4). This is an IPNET security vulnerability: TCP Urgent Pointer state confusion caused by a malformed TCP AO option.