CVE-2002-1507
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 · uneditedUnreal Tournament 2003 (ut2003) clients and servers allow remote attackers to cause a denial of service via malformed messages containing a small number of characters to UDP ports 7778 or 10777.
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 confidenceUnreal Tournament 2003 contains a denial-of-service vulnerability where malformed UDP packets sent to ports 7778 or 10777 cause the server or client to crash. The vulnerability stems from insufficient input validation when processing network messages.
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 data= 2003CVSS 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.
-
Confirm Unreal Tournament 2003 Server installationCheck if Unreal Tournament Server files exist on the system. Look for the UT2003 installation directory (commonly in Program Files or a game servers folder) and verify the presence of the server executable (ucc.exe or similar).Affected if Unreal Tournament 2003 server software is installed on the system.
-
Verify the installed version is UT2003Locate version information in the server installation. Check the version metadata of the ucc.exe binary or any version.txt/readme files in the UT2003 directory. Compare the version to the affected release (2003).Affected if The installed version is specifically Unreal Tournament 2003 (not a later version like UT2004 or later).
-
Identify if the server is currently runningCheck for running processes related to UT2003 server. On Windows, use Task Manager or 'tasklist' command. On Linux, use 'ps' or check for running ucc server processes. Also verify if ports 7778 or 10777 are in use via 'netstat' or similar network tools.Affected if The UT2003 server process is actively running and listening on network ports.
-
Determine network exposure of vulnerable portsUse network scanning tools (such as netstat, nmap, or equivalent) to confirm whether ports 7778 and 10777 are bound to accessible network interfaces. Check if these ports are listening on 0.0.0.0 (all interfaces) rather than only localhost.Affected if The vulnerable ports 7778 or 10777 are exposed to network traffic, especially untrusted networks.
The environment is affected if Unreal Tournament 2003 server is installed, the specific version is 2003, the server is running, and ports 7778 or 10777 are network-accessible.
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 dataImplement network-level controls to filter or block malformed UDP packets to ports 7778 and 10777 from untrusted sources. Since UT2003 is end-of-life and likely unpatched, consider network segmentation or migration to supported game server software.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1507 — 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-2002-1507 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