CVE-2002-1535
Overview
CVE-2002-1535 is a known-severity vulnerability affecting symantec enterprise_firewall. It was published on March 31, 2003.
Technical Description
Secure Webserver 1.1 in Raptor 6.5 and Symantec Enterprise Firewall 6.5.2 allows remote attackers to identify IP addresses of hosts on the internal network via a CONNECT request, which generates different error messages if the host is present.
Remediation
Check the references section for vendor advisories and patches from symantec. Update enterprise_firewall 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-2002-1535?
CVE-2002-1535 is a known-severity vulnerability affecting symantec enterprise_firewall. It was published on March 31, 2003.
How severe is CVE-2002-1535?
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-2002-1535?
Check the references section for vendor advisories and patches from symantec. Update enterprise_firewall 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-2002-1535?
CyberStrike's AI-powered security agents can automatically detect CVE-2002-1535 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.