CVE-2003-1430
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 · uneditedDirectory traversal vulnerability in Unreal Tournament Server 436 and earlier allows remote attackers to access known files via a ".." (dot dot) in an unreal:// URL.
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 Unreal Tournament Server versions 436 and earlier contains a directory traversal vulnerability that allows remote attackers to access arbitrary files on the host system by using '..' (dot-dot) sequences within unreal:// URLs. This enables reading files outside the intended server document root.
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= 226f= 433= 436CVSS 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.
-
Verify Unreal Tournament Server is runningCheck for running Unreal Tournament Server processes using task manager (Windows) or commands like 'ps aux | grep -i unreal' (Linux)Affected if The server process is active and listening on network ports
-
Determine the installed server versionCheck server version by examining server logs, startup banner, or querying the running server. The version string typically appears in server console output or log files (often in the server's 'Logs' directory or displayed at startup)Affected if The version is 226f, 433, 436, or any version earlier than these
-
Confirm network exposure of the serverCheck if the server is bound to a network interface and listening on ports (default game port 7777, query port 7778). Use 'netstat -an' or 'ss -tlnp' to list listening portsAffected if The server is accessible over the network on any port
-
Verify the directory traversal is exploitableNo special configuration required - the vulnerability exists inherently in versions 436 and earlier. The flaw is triggered by sending specially crafted unreal:// URLs containing '../' sequences to the serverAffected if The server version falls within the affected range (226f, 433, 436, or earlier) and the server is network-accessible
A user is affected if Unreal Tournament Server version 436 or earlier is running and exposed to network requests, allowing remote attackers to access files outside the server document root via directory traversal sequences.
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 dataUpgrade to a patched version of Unreal Tournament Server newer than version 436, or implement input validation/sanitization on the server to reject URL requests containing directory traversal sequences like '..'.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-1430 — 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-2003-1430 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