Unscored severity · published Apr 2, 2003
CVE-2003-0106
The HTTP proxy for Symantec Enterprise Firewall (SEF) 7.0 allows proxy users to bypass pattern matching for blocked URLs via requests that are URL-encoded with escapes, Unicode,…
–
CVSS
1.4%
EPSS
No
On KEV
Description
The HTTP proxy for Symantec Enterprise Firewall (SEF) 7.0 allows proxy users to bypass pattern matching for blocked URLs via requests that are URL-encoded with escapes, Unicode, or UTF-8.
Exploitation
Is it being used?
Exploit prediction (EPSS)1.4% · higher than 72% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
EF
Enterprise Firewall · Symantec
7.0 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2003-0106
CVE.org
https://www.cve.org/CVERecord?id=CVE-2003-0106
archives.neohapsis.com
http://archives.neohapsis.com/archives/vulnwatch/2003-q1/0152.html
marc.info
http://marc.info/?l=bugtraq&m=104869513822233&w=2
marc.info
http://marc.info/?l=ntbugtraq&m=104868285106289&w=2
Patch
http://service1.symantec.com/SUPPORT/ent-gate.nsf/docid/2003032507434754
Vendor Advisory
http://www.securityfocus.com/bid/7196
More from Enterprise Firewall
–
CVE-2007-4422
The login interface in Symantec Enterprise Firewall 6.x, when a VPN with pre-shared key (PSK) authentication is enabled, generates different responses depending on whether or not…
–
CVE-2006-2341
The HTTP proxy in Symantec Gateway Security 5000 Series 2.0.1 and 3.0, and Enterprise Firewall 8.0, when NAT is being used, allows remote attackers to determine internal IP…
–
CVE-2005-3768
Buffer overflow in the Internet Key Exchange version 1 (IKEv1) implementation in Symantec Dynamic VPN Services, as used in Enterprise Firewall, Gateway Security, and Firewall /VPN…
–
CVE-2005-0817
Unknown vulnerability in the DNSd proxy, as used in Symantec Gateway Security 5400 2.x and 5300 1.x, Enterprise Firewall 7.0.x and 8.x, and VelociRaptor 1100/1200/1300 1.5, allows…
–
CVE-2004-1029
The Sun Java Plugin capability in Java 2 Runtime Environment (JRE) 1.4.2_01, 1.4.2_04, and possibly earlier versions, does not properly restrict access between Javascript and Java…