CVE-1999-1066
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedQuake 1 server responds to an initial UDP game connection request with a large amount of traffic, which allows remote attackers to use the server as an amplifier in a "Smurf" style attack on another host, by spoofing the connection request.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Quake 1 game server responds to initial UDP connection requests with a disproportionately large volume of outgoing traffic. Remote attackers can exploit this by spoofing the source IP address in their request, causing the Quake server to flood the victim with amplified traffic—a classic reflection/amplification attack enabling distributed denial-of-service (DDoS).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Quake 1 server processesScan running processes on the system for Quake-related executables (e.g., quake, qserver, quake1srv) or examine listening network services.Affected if A Quake 1 server process is running and listening for incoming connections.
-
Check for open UDP ports associated with QuakeUse netstat, ss, or similar tools to enumerate open UDP ports. Common Quake server ports include 26000-26002, 27000-27002, but verify against actual listening services.Affected if The system has UDP ports open that are bound to a Quake server process.
-
Verify UDP service responseSend a valid Quake protocol UDP packet to the suspected server port and observe if a response is generated. This confirms the service is actively responding to queries.Affected if The server responds to initial UDP connection requests with traffic larger than the query (amplification factor).
-
Assess network exposureReview firewall rules, NAT configurations, and router settings to determine if the Quake server UDP port is reachable from external networks.Affected if The Quake server UDP port is exposed to the internet without source IP validation or ingress filtering.
The environment is affected if a Quake 1 server is running, accepting UDP connections, and is network-accessible to potential attackers who could spoof source IPs to reflect amplified traffic toward victims.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable or decommission any legacy Quake 1 servers still in operation; if retention is required, implement strict UDP source IP validation, ingress filtering, or rate limiting at the network perimeter to prevent spoofed request amplification.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1066 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-1999-1066 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data