CVE-2000-0305
Be Beo — CWE-399
EPSS 41.0%
- Published: 2000-05-19T04:00:00.000
- Last modified: 2025-04-03T01:03:51.193
- Vendors: Be
- Products: Beo
- CWE: CWE-399
Windows 95, Windows 98, Windows 2000, Windows NT 4.0, and Terminal Server systems allow a remote attacker to cause a denial of service by sending a large number of identical fragmented IP packets, aka jolt2 or the “IP Fragment Reassembly” vulnerability.
Related CVE by CWE
No related CWE found.
Top CVE for Vendor
- CVE-2000-0279 (no score)
- CVE-2000-0276 (no score)
- CVE-2000-0463 (no score)
- CVE-2000-0305 (no score)
Recently Exploited Similar Vulnerabilities
No recent KEV-listed items for this vendor/product.
How to fix CVE-2000-0305
CVE-2000-0305 is a unknown severity vulnerability affecting Be Beo.
Description: Windows 95, Windows 98, Windows 2000, Windows NT 4.0, and Terminal Server systems allow a remote attacker to cause a denial of service by sending a large number of identical fragmented IP packets, aka jolt2 or the “IP Fragment Reassembly” vulnerability. Related CVE by CWENo related CWE found.Top CVE for VendorCVE-2000-0279 (no score)CVE-2000-0276 (no score)CVE-2000-0463 […]
Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public
How to Fix:
- Check if you're running Beo
- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Description: Windows 95, Windows 98, Windows 2000, Windows NT 4.0, and Terminal Server systems allow a remote attacker to cause a denial of service by sending a large number of identical fragmented IP packets, aka jolt2 or the “IP Fragment Reassembly” vulnerability. Related CVE by CWENo related CWE found.Top CVE for VendorCVE-2000-0279 (no score)CVE-2000-0276 (no score)CVE-2000-0463 […]
Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public
How to Fix:
1 Identify affected systems
- Check if you're running Beo
2 Immediate actions
- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
3 Verification
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
4 Long-term prevention
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
CWE: CWE-399
Exploit Difficulty Assessment
HARD
Time to Exploit: > 4 hours
Skills Required: Advanced security expertise
Public Exploits: Rare or not public
Vulnerability Timeline
May 19, 2000
Vulnerability Published
CVE details first published to NVD database
Apr 03, 2025
Last Modified
CVE details were updated
Nov 03, 2025
Imported to Database
Added to this CVE tracking system
Detection Rules & IOCs
No specific detection rules generated for this vulnerability type.
- http://www.securityfocus.com/bid/1236 [Third Party Advisory, VDB Entry]
- http://www.securityfocus.com/templates/advisory.html?id=2240 [Third Party Advisory, VDB Entry]
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2000/ms00-029 []
- http://www.securityfocus.com/bid/1236 [Third Party Advisory, VDB Entry]
- http://www.securityfocus.com/templates/advisory.html?id=2240 [Third Party Advisory, VDB Entry]
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2000/ms00-029 []
No explicit mitigation/advisory links found in references.