The Treck TCP/IP stack before 6.0.1.66 improperly handles an IPv4/ICMPv4 Length Parameter Inconsistency, which might allow remote attackers to trigger an information leak.
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://www.kb.cert.org/vuls/id/257161/ | us government resource third party advisory mitigation |
| https://www.treck.com | product vendor advisory |
| https://jsof-tech.com/vulnerability-disclosure-policy/ | third party advisory |
| https://www.kb.cert.org/vuls/id/257161 | third party advisory |
| https://www.jsof-tech.com/ripple20/ | third party advisory exploit |
| https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-treck-ip-stack-JyBQ5GyC | third party advisory vendor advisory |
| http://www.arubanetworks.com/assets/alert/ARUBA-PSA-2020-006.txt | |
| https://security.netapp.com/advisory/ntap-20200625-0006/ | |
| https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=hpesbhf04012en_us | |
| https://www.dell.com/support/article/de-de/sln321836/dell-response-to-the-ripple20-vulnerabilities |