CVE-1999-0345
Jolt ICMP attack causes a denial of service in Windows 95 and Windows NT systems.
All CVEs associated with "Microsoft Windows". Page 122/122 • 14532 CVEs.
Subscribe CVEs: RSS for “Microsoft Windows” · RSS (High+Critical only)
A curated feed of “Microsoft Windows”-related CVEs appears below. We currently track 14532 CVEs for this tag (all time). In the last 365 days, 1692 were published. Average CVSS is 7.3 (all time; 7.2 over 365d), and 66% are rated High/Critical (all time). Top CWEs (last 365 days): CWE-416 - Use After Free, CWE-122 - Heap-based Buffer Overflow, CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition').
In our taxonomy this topic maps to a MODERATE impact class. Issues here typically affect operating system packages or kernels. Plan reboots or service restarts and coordinate rollouts across fleets. Use the filters below to sort by CVSS, risk and CWE. Each detail page highlights vendor advisories and mitigation tips.
CVEs tagged with this topic. Filters apply to the whole list (loaded from JSON).
Jolt ICMP attack causes a denial of service in Windows 95 and Windows NT systems.
A Windows NT 4.0 user can gain administrative rights by forcing NtOpenProcessToken to succeed regardless of the user's permissions, aka GetAdmin.
A Windows NT local user or administrator account has a guessable password.
A Windows NT local user or administrator account has a default, null, blank, or missing password.
A Windows NT user has inappropriate rights or privileges, e.g. Act as System, Add Workstation, Backup, Change System Time, Create Pagefile, Create Permanent Object, Create Token Name, Debug, Generate…
A Windows NT account policy for passwords has inappropriate, security-critical settings, e.g. for password length, password age, or uniqueness.
The registry in Windows NT can be accessed remotely by users who are not administrators.
.reg files are associated with the Windows NT registry editor (regedit), making the registry susceptible to Trojan Horse attacks.
A Windows NT system's user audit policy does not log an event success or failure, e.g. for Logon and Logoff, File and Object Access, Use of User Rights, User and Group Management, Security Policy Cha…
A Windows NT system's file audit policy does not log an event success or failure for security-critical files or directories.
A Windows NT account policy has inappropriate, security-critical settings for lockout, e.g. lockout duration, lockout after bad logon attempts, etc.
Guessable magic cookies in X Windows allows remote attackers to execute commands, e.g. through xterm.