CVE-2004-2597
Overview
CVE-2004-2597 is a known-severity vulnerability affecting id_software quake_ii_server. It was published on December 31, 2004.
Technical Description
Quake II server before R1Q2, as used in multiple products, allows remote attackers to bypass IP-based access control rules via a userinfo string that already contains an "ip" key/value pair but is also long enough to cause a new key/value pair to be truncated, which interferes with the server's ability to find the client's IP address.
Remediation
Check the references section for vendor advisories and patches from id_software. Update quake_ii_server to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|
References
Frequently Asked Questions
What is CVE-2004-2597?
CVE-2004-2597 is a known-severity vulnerability affecting id_software quake_ii_server. It was published on December 31, 2004.
How severe is CVE-2004-2597?
CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.
How do I fix or remediate CVE-2004-2597?
Check the references section for vendor advisories and patches from id_software. Update quake_ii_server to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2004-2597?
CyberStrike's AI-powered security agents can automatically detect CVE-2004-2597 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.