CVE-1999-1284: NukeNabber allows remote attackers to cause a denial of service by connecting to the NukeNabber port
NukeNabber allows remote attackers to cause a denial of service by connecting to the NukeNabber port (1080) without sending any data, which causes the CPU usage to rise to 100% from the report.exe program that is executed upon the connection.
AI Analysis
Technical Summary
CVE-1999-1284 is a denial of service (DoS) vulnerability affecting the NukeNabber software, a product from puppets_place. The vulnerability arises because NukeNabber listens on port 1080 and executes a program called report.exe upon each incoming connection. An attacker can exploit this by simply establishing a connection to the NukeNabber port without sending any data. This causes report.exe to consume 100% CPU resources, effectively leading to a denial of service condition. The vulnerability does not require authentication or any user interaction, and it can be triggered remotely over the network. The CVSS score of 5.0 (medium severity) reflects that the attack vector is network-based, with low attack complexity, no authentication required, and impacts availability only, without affecting confidentiality or integrity. No patches or mitigations are currently available, and there are no known exploits in the wild. Given the age of the vulnerability (published in 1998), it is likely that NukeNabber is an outdated or legacy application, but if still in use, it poses a risk of service disruption due to resource exhaustion caused by simple connection attempts.
Potential Impact
For European organizations, the primary impact of this vulnerability is service unavailability caused by CPU resource exhaustion on systems running NukeNabber. This could disrupt business operations, especially if NukeNabber is part of critical infrastructure or services. Although the vulnerability does not compromise data confidentiality or integrity, denial of service can lead to operational downtime, loss of productivity, and potential reputational damage. Organizations relying on legacy systems or niche applications like NukeNabber may be particularly vulnerable. Additionally, if NukeNabber is exposed to the internet or accessible from untrusted networks, attackers could remotely trigger the DoS condition, potentially affecting multiple systems simultaneously. The lack of patches means organizations must rely on other mitigation strategies to reduce risk.
Mitigation Recommendations
Since no patch is available, European organizations should implement specific mitigations to reduce exposure. First, restrict network access to the NukeNabber port (1080) using firewalls or network segmentation, allowing only trusted hosts to connect. Second, monitor network traffic and system CPU usage for unusual spikes that may indicate exploitation attempts. Third, consider disabling or uninstalling NukeNabber if it is not essential, especially given its age and lack of vendor support. If the application must remain in use, running it in a controlled environment with resource limits (e.g., CPU quotas or containerization) can help contain the impact of DoS attempts. Finally, implement intrusion detection or prevention systems (IDS/IPS) with rules to detect and block suspicious connection patterns targeting port 1080.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy
CVE-1999-1284: NukeNabber allows remote attackers to cause a denial of service by connecting to the NukeNabber port
Description
NukeNabber allows remote attackers to cause a denial of service by connecting to the NukeNabber port (1080) without sending any data, which causes the CPU usage to rise to 100% from the report.exe program that is executed upon the connection.
AI-Powered Analysis
Technical Analysis
CVE-1999-1284 is a denial of service (DoS) vulnerability affecting the NukeNabber software, a product from puppets_place. The vulnerability arises because NukeNabber listens on port 1080 and executes a program called report.exe upon each incoming connection. An attacker can exploit this by simply establishing a connection to the NukeNabber port without sending any data. This causes report.exe to consume 100% CPU resources, effectively leading to a denial of service condition. The vulnerability does not require authentication or any user interaction, and it can be triggered remotely over the network. The CVSS score of 5.0 (medium severity) reflects that the attack vector is network-based, with low attack complexity, no authentication required, and impacts availability only, without affecting confidentiality or integrity. No patches or mitigations are currently available, and there are no known exploits in the wild. Given the age of the vulnerability (published in 1998), it is likely that NukeNabber is an outdated or legacy application, but if still in use, it poses a risk of service disruption due to resource exhaustion caused by simple connection attempts.
Potential Impact
For European organizations, the primary impact of this vulnerability is service unavailability caused by CPU resource exhaustion on systems running NukeNabber. This could disrupt business operations, especially if NukeNabber is part of critical infrastructure or services. Although the vulnerability does not compromise data confidentiality or integrity, denial of service can lead to operational downtime, loss of productivity, and potential reputational damage. Organizations relying on legacy systems or niche applications like NukeNabber may be particularly vulnerable. Additionally, if NukeNabber is exposed to the internet or accessible from untrusted networks, attackers could remotely trigger the DoS condition, potentially affecting multiple systems simultaneously. The lack of patches means organizations must rely on other mitigation strategies to reduce risk.
Mitigation Recommendations
Since no patch is available, European organizations should implement specific mitigations to reduce exposure. First, restrict network access to the NukeNabber port (1080) using firewalls or network segmentation, allowing only trusted hosts to connect. Second, monitor network traffic and system CPU usage for unusual spikes that may indicate exploitation attempts. Third, consider disabling or uninstalling NukeNabber if it is not essential, especially given its age and lack of vendor support. If the application must remain in use, running it in a controlled environment with resource limits (e.g., CPU quotas or containerization) can help contain the impact of DoS attempts. Finally, implement intrusion detection or prevention systems (IDS/IPS) with rules to detect and block suspicious connection patterns targeting port 1080.
Affected Countries
Threat ID: 682ca32bb6fd31d6ed7deb1c
Added to database: 5/20/2025, 3:43:39 PM
Last enriched: 7/1/2025, 9:27:15 PM
Last updated: 2/7/2026, 6:23:47 AM
Views: 31
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-15267: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in boldthemes Bold Page Builder
MediumCVE-2025-13463: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in boldthemes Bold Page Builder
MediumCVE-2025-12803: CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in boldthemes Bold Page Builder
MediumCVE-2025-12159: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in boldthemes Bold Page Builder
MediumCVE-2026-2075: Improper Access Controls in yeqifu warehouse
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.