The WDB target agent debug service in Wind River VxWorks 6.x, 5.x, and earlier, as used on the Rockwell Automation 1756-ENBT series A with firmware 3.2.6 and 3.6.1 and other products, allows remote attackers to read or modify arbitrary memory locations, perform function calls, or manage tasks via requests to UDP port 17185, a related issue to CVE-2005-3804. Wind River VxWorks before 5.5.1, 6.5.x through 6.7.x before 6.7.1.1, 6.8.x before 6.8.3, 6.9.x before 6.9.4.4, and 7.x before 7 ipnet_coreip 1.2.2.0, as used on Schneider Electric SAGE RTU devices before J2 and other devices, does not properly generate TCP initial sequence number (ISN) values, which makes it easier for remote attackers to spoof TCP sessions by predicting an ISN value.
#ADOBE ROBOHELP SERVER 9.0 CODE#
Integer overflow in the _authenticate function in svc_auth.c in Wind River VxWorks 5.5 through 6.9.4.1, when the Remote Procedure Call (RPC) protocol is enabled, allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a username and password. It may allow remote attackers to cause a denial of service (crash) or possibly execute arbitrary code. When RPC is enabled in Wind River VxWorks 6.9 prior to 6.9.1, a specially crafted RPC request can trigger an integer overflow leading to an out-of-bounds memory copy. This is a IPNET security vulnerability: TCP Urgent Pointer = 0 that leads to an integer underflow. Wind River VxWorks has a Buffer Overflow in the TCP component (issue 1 of 4). There is an IPNET security vulnerability: Stack overflow in the parsing of IPv4 packets’ IP options. Wind River VxWorks 6.9 and vx7 has a Buffer Overflow in the IPv4 component. There is an IPNET security vulnerability: Heap overflow in DHCP Offer/ACK parsing inside ipdhcpc. Wind River VxWorks 6.6 through 6.9 has a Buffer Overflow in the DHCP client component. This is a IPNET security vulnerability: DoS of TCP connection via malformed TCP options. Wind River VxWorks 6.6 through vx7 has Session Fixation in the TCP component. There is an IPNET security vulnerability: DoS via NULL dereference in IGMP parsing. Wind River VxWorks 6.6, 6.7, 6.8, 6.9 and vx7 has an array index error in the IGMPv3 client component. This is an IPNET security vulnerability: TCP Urgent Pointer state confusion caused by a malformed TCP AO option. 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 during connect() to a remote host. Wind River VxWorks 6.7 though 6.9 and vx7 has a Buffer Overflow in the TCP component (issue 3 of 4). There is an IPNET security vulnerability: TCP Urgent Pointer state confusion due to race condition. Wind River VxWorks 6.9.4 and vx7 has a Buffer Overflow in the TCP component (issue 4 of 4). There is an IPNET security vulnerability: IGMP Information leak via IGMPv3 specific membership report. Wind River VxWorks 6.5, 6.6, 6.7, 6.8, 6.9.3 and 6.9.4 has a Memory Leak in the IGMPv3 client component.
HttpRpmFs in WebCLI in Wind River VxWorks 5.5 through 7 SR0640 has no check for an escape from the web root. As a result, the actual memory allocated is smaller than the buffer size specified by the arguments, leading to memory corruption. In Wind River VxWorks, memory allocator has a possible overflow in calculating the memory block's size to be allocated by calloc(). NOTE: This vulnerability only affects products that are no longer supported by the maintainer. ** UNSUPPORTED WHEN ASSIGNED ** A DNS client stack-based buffer overflow in ipdnsc_decode_name() affects Wind River VxWorks 6.5 through 7. A specially crafted packet may lead to buffer over-read on IKE. There is a possible heap overflow in dhcp client.Īn issue was discovered in Wind River VxWorks 7 before 21.03. There is a possible stack overflow in dhcp server.Īn issue was discovered in Wind River VxWorks before 6.5. As a result, the actual memory allocated is smaller than the buffer size specified by the arguments, leading to memory corruption.Īn issue was discovered in Wind River VxWorks through 6.8. The memory allocator has a possible integer overflow in calculating a memory block's size to be allocated by calloc(). In the IKE component, a specifically crafted packet may lead to reading beyond the end of a buffer, or a double free.Īn issue was discovered in Wind River VxWorks 7. An issue was discovered in VxWorks 6.9 through 7.
0 kommentar(er)
