{"vuid":"VU#329230","idnumber":"329230","name":"Multiple Symantec security appliances fail to properly filter port 53/udp traffic","keywords":["Symantec Firewall/VPN","Gateway Security","port 53/udp"],"overview":"A vulnerability exists in multiple Symantec security appliances that could allow a remote attacker to bypass the firewall using a source port of 53/udp.","clean_desc":"Symantec's Firewall/VPN appliances and Gateway Security models include a number of services such as tftpd, snmpd, and isakmp. Access to these services from the WAN interface can be restricted through the use of the packet filtering feature of the device. The packet filtering feature contains a vulnerability that could allow a remote attacker to successfully connect to one of these services by specifying a source port of 53/udp. Affected Products: Symantec Firewall/VPN Appliance 100 (firmware builds prior to build 1.63)\nSymantec Firewall/VPN Appliance 200/200R (firmware builds prior to build 1.63)\nSymantec Gateway Security 320 (firmware builds prior to build 622)\nSymantec Gateway Security 360/360R (firmware builds prior to build 622)","impact":"A remote, unauthenticated attacker may be able to establish connections to services in violation of security policies. As a result, an attacker could send packets to these services that are configured to be unreachable from the WAN interface. An attacker could also leverage this flaw to exploit a vulnerability in one of these services. For instance, there is a vulnerability in the Firewall/VPN and Gateway Security appliances that allows a remote attacker to read and modify any SNMP object present on an affected device (VU#173910).","resolution":"Upgrade Firmware\nAccording to the Symantec Advisory, product specific firmware and hotfixes are available via the Symantec Enterprise Support site. http://www.symantec.com/techsupp/","workarounds":"","sysaffected":"","thanks":"This vulnerability was reported by Symantec. Symantec credits Mike Sues and the Rigel Kent Security & Advisory Services for discovering the vulnerability.","author":"This document was written by Damon Morda.","public":["http://www.sarc.com/avcenter/security/Content/2004.09.22.html","http://www.rigelksecurity.com/Services/Svcs_sec_advis.html","http://secunia.com/advisories/12635/","http://www.securityfocus.com/bid/11237","http://www.securitytracker.com/alerts/2004/Sep/1011389.html","http://www.securitytracker.com/alerts/2004/Sep/1011388.html"],"cveids":[""],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2004-09-23T13:24:55Z","publicdate":"2004-09-22T00:00:00Z","datefirstpublished":"2004-10-20T14:36:43Z","dateupdated":"2004-10-20T14:36:49Z","revision":14,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"15","cam_exploitation":"0","cam_internetinfrastructure":"7","cam_population":"7","cam_impact":"7","cam_easeofexploitation":"15","cam_attackeraccessrequired":"20","cam_scorecurrent":"6.06375","cam_scorecurrentwidelyknown":"7.441875","cam_scorecurrentwidelyknownexploited":"12.954375","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":6.06375,"vulnote":null}