{"vuid":"VU#118388","idnumber":"118388","name":"Symantec Scan Engine fails to properly perform authentication","keywords":["Symantec","Scan Engine","authentication bypass","web-based user login","antivirus","java"],"overview":"Symantec Scan Engine administrative web interface fails to properly authenticate users, which may allow a remote attacker to gain administrative access to the software.","clean_desc":"The Symantec Scan Engine provides a programming interface to Symantec content scanning and virus detection services. The Symantec Scan Engine includes an administrative interface that is enabled and listening on port 8004/tcp by default. The web interface to Symantec Scan Engine uses a client-side Java applet to perform authentication. No authentication is performed on the server side.","impact":"A remote, unauthenticated attacker may be able to gain access to the Symantec Scan Engine software. At the time of publication of this document, exploit code to remotely change the administrator password is available.","resolution":"Apply an update\nApply an update to Symantec Scan Engine, as specified in the Symantec document SYM06-008.","workarounds":"Restrict access You may wish to block access to the vulnerable software from outside your network perimeter, specifically by blocking access to the administrative port (8004/tcp by default). This will limit your exposure to attacks. However, blocking at the network perimeter would still allow attackers within the perimeter of your network to exploit the vulnerability. The use of host-based firewalls in addition to network-based firewalls can help restrict access to specific hosts within the network. It is important to understand your network's configuration and service requirements before deciding what changes are appropriate.","sysaffected":"","thanks":"This vulnerability was disclosed by Symantec, who in turn credit Rapid7 with reporting the issue.","author":"This document was written by Will Dormann.","public":["http://www.symantec.com/avcenter/security/Content/2006.04.21.html","http://secunia.com/advisories/19734/","  http://www.rapid7.com/advisories/R7-0021.html"],"cveids":["CVE-2006-0230"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2006-04-24T17:10:37Z","publicdate":"2006-04-21T00:00:00Z","datefirstpublished":"2006-05-01T21:49:56Z","dateupdated":"2006-05-01T21:53:30Z","revision":6,"vrda_d1_directreport":"0","vrda_d1_population":"3","vrda_d1_impact":"3","cam_widelyknown":"20","cam_exploitation":"10","cam_internetinfrastructure":"10","cam_population":"10","cam_impact":"16","cam_easeofexploitation":"20","cam_attackeraccessrequired":"15","cam_scorecurrent":"36","cam_scorecurrentwidelyknown":"36","cam_scorecurrentwidelyknownexploited":"45","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":27.0,"vulnote":null}