Show filters
77 Total Results
Displaying 51-60 of 77
Sort by:
Attacker Value
Unknown

CVE-2004-0894

Disclosure Date: January 10, 2005 (last updated February 22, 2025)
LSASS (Local Security Authority Subsystem Service) of Windows 2000 Server and Windows Server 2003 does not properly validate connection information, which allows local users to gain privileges via a specially-designed program.
0
Attacker Value
Unknown

CVE-2004-1080

Disclosure Date: January 10, 2005 (last updated February 22, 2025)
The WINS service (wins.exe) on Microsoft Windows NT Server 4.0, Windows 2000 Server, and Windows Server 2003 allows remote attackers to write to arbitrary memory locations and possibly execute arbitrary code via a modified memory pointer in a WINS replication packet to TCP port 42, aka the "Association Context Vulnerability."
0
Attacker Value
Unknown

CVE-2004-0893

Disclosure Date: January 10, 2005 (last updated February 22, 2025)
The Local Procedure Call (LPC) interface of the Windows Kernel for Windows NT 4.0, Windows 2000, Windows XP, and Windows Server 2003 does not properly validate the lengths of messages sent to the LPC port, which allows local users to gain privileges, aka "Windows Kernel Vulnerability."
0
Attacker Value
Unknown

CVE-2004-0571

Disclosure Date: January 10, 2005 (last updated February 22, 2025)
Microsoft Word for Windows 6.0 Converter does not properly validate certain data lengths, which allows remote attackers to execute arbitrary code via a .wri, .rtf, and .doc file sent by email or malicious web site, aka "Table Conversion Vulnerability," a different vulnerability than CVE-2004-0901.
0
Attacker Value
Unknown

CVE-2004-0901

Disclosure Date: January 10, 2005 (last updated February 22, 2025)
Microsoft Word for Windows 6.0 Converter (MSWRD632.WPC), as used in WordPad, does not properly validate certain data lengths, which allows remote attackers to execute arbitrary code via a .wri, .rtf, and .doc file sent by email or malicious web site, aka "Font Conversion Vulnerability," a different vulnerability than CVE-2004-0571.
0
Attacker Value
Unknown

CVE-2004-0568

Disclosure Date: January 10, 2005 (last updated February 22, 2025)
HyperTerminal application for Windows NT 4.0, Windows 2000, Windows XP, and Windows Server 2003 does not properly validate the length of a value that is saved in a session file, which allows remote attackers to execute arbitrary code via a malicious HyperTerminal session file (.ht), web site, or Telnet URL contained in an e-mail message, triggering a buffer overflow.
0
Attacker Value
Unknown

CVE-2004-0567

Disclosure Date: December 31, 2004 (last updated February 22, 2025)
The Windows Internet Naming Service (WINS) in Windows NT Server 4.0 SP 6a, NT Terminal Server 4.0 SP 6, Windows 2000 Server SP3 and SP4, and Windows Server 2003 does not properly validate the computer name value in a WINS packet, which allows remote attackers to execute arbitrary code or cause a denial of service (server crash), which results in an "unchecked buffer" and possibly triggers a buffer overflow, aka the "Name Validation Vulnerability."
0
Attacker Value
Unknown

CVE-2004-1306

Disclosure Date: December 31, 2004 (last updated February 22, 2025)
Heap-based buffer overflow in winhlp32.exe in Windows NT, Windows 2000 through SP4, Windows XP through SP2, and Windows 2003 allows remote attackers to execute arbitrary code via a crafted .hlp file.
0
Attacker Value
Unknown

CVE-2004-1361

Disclosure Date: December 23, 2004 (last updated February 22, 2025)
Integer underflow in winhlp32.exe in Windows NT, Windows 2000 through SP4, Windows XP through SP2, and Windows 2003 allows remote attackers to execute arbitrary code via a malformed .hlp file, which leads to a heap-based buffer overflow.
0
Attacker Value
Unknown

CVE-2004-1305

Disclosure Date: December 23, 2004 (last updated February 22, 2025)
The Windows Animated Cursor (ANI) capability in Windows NT, Windows 2000 through SP4, Windows XP through SP1, and Windows 2003 allow remote attackers to cause a denial of service via (1) the frame number set to zero, which causes an invalid memory address to be used and leads to a kernel crash, or (2) the rate number set to zero, which leads to resource exhaustion and hang.
0