48 matches found
CVE-2008-0976
CVE-2008-0976 affects Double-Take 5.0.0.2865 and earlier (distributed under HP StorageWorks Storage Mirroring and other names). The underlying issue is a NULL pointer dereference in a network daemon exploitable by malformed packets, with demonstrated packet types 0x2722 and 0x272a, leading to rem...
CVE-2008-0973
The CVE-2008-0973 entry describes a buffer overflow in Double-Take (HP StorageWorks Storage Mirroring) version 4.5.0.1629 and other 4.5.0.x releases. The vulnerability is exploitable by remote attackers via a packet containing a long string in the username field. The impact is listed as unknown/u...
CVE-2008-0973
Buffer overflow in Double-Take aka HP StorageWorks Storage Mirroring 4.5.0.1629, and other 4.5.0.x versions, allows remote attackers to have an unknown impact via a packet with a long string in the username field...
CVE-2008-0979
CVE-2008-0979 concerns a stack consumption vulnerability in Double-Take 5.0.0.2865 and earlier (also under HP StorageWorks Storage Mirroring and other names). The issue allows a remote attacker to cause a denial of service (daemon crash) by sending a certain packet that triggers recursive calling...
CVE-2008-0978
CVE-2008-0978 affects Double-Take 5.0.0.2865 and earlier (HP StorageWorks Storage Mirroring name and other names). A remote attacker can obtain sensitive information by sending a crafted packet of type 0x2728 (OS/path info), 0x274e (Ethernet adapters), 0x2726 (filesystem info), 0x274f (printer dr...
CVE-2008-0975
CVE-2008-0975 affects Double-Take (HP StorageWorks Storage Mirroring lineage) up to version 5.0.0.2865, where a remote attacker can cause CPU exhaustion by sending a -1 value in the vector size field. Core details indicate the issue is a remote DoS via malformed vector size; no remediation or exp...
Multiple vulnerabilities in Double-Take 5.0.0.2865
Luigi Auriemma Application: Double-Take http://www.doubletake.com Versions: = 5.0.0.2865 version 4.5.x tested with success too Platforms: Windows Bugs: A server termination through "vectorT too long" exception B NULL pointer crash C termination through memory allocation D informations disclosure ...