Symantec Intel Alert Management System Multiple Code Execution Issues

SUMMARY

Symantec was notified of multiple instances of failure to properly handle user input in the Third Party Intel Alert Management System (AMS2) which could result in arbitrary code execution.

AFFECTED PRODUCTS

Product

|

Version

|

Solution

—|—|—

Symantec AntiVirus Corporate Edition Server

|

10.x

|

Upgrade to SAVCE 10.1 MR10

Symantec System Center

|

10.x

|

Upgrade to SSC from SAVCE 10.1 MR10

Symantec Quarantine Server

|

3.6

|

Upgrade to Quarantine Server from SEP 11.0 MR3 or later

Symantec Quarantine Server

|

3.5

|

Upgrade to Quarantine Server from SAVCE 10.1 MR10

ISSUES

Severity

High

CVSS2 Base Score: 7.9
Impact 10.0 Exploitability 5.5

CVSS 2 Base Vector: AV:A/AC:M/Au:N/C:C/I:C/A:C

Exploit Publicly Available: proof of concept

MITIGATION

Details

The Intel Alert Management System (AMS2) is used in Symantec AntiVirus Corporate Edition Server (SAVCE), Symantec System Center (SSC), and Symantec Quarantine Server. AMS2 listens on TCP Port 38292 and allows SAVCE Administrators to send messages(i.e. email) if a user-specified event occurs.

Symantec was notified of multiple vulnerabilities in AMS2. It is possible to send specially-crafted packets to the targeted server, causing a buffer overflow or allowing arbitrary commands to run, potentially executing arbitrary code. The successful exploitation of these vulnerabilities could result in a possible compromise of the affected products.

AMS2 has not been included in a default install of SAVCE Server or SSC since version 10.0. AMS2 was included in the default install of Quarantine Server prior to SEP 11.0 MR3.

Symantec Response

Symantec engineers verified these issues and released an update to address them. Symantec customers should update to the latest maintenance release available through normal update procedures.

Symantec knows of no exploitation of or adverse customer impact from this issue.

Mitigations

Symantec recommends upgrading any vulnerable versions of SAVCE Server or Symantec System Center to SAVCE 10.1 MR10. Vulnerable versions of Quarantine Server 3.5 should be upgraded to SAVCE 10.1 MR10. Vulnerable versions of Quarantine Server 3.6 should be upgraded to SEP 11.0 MR3 or later. SEP users running a version of Quarantine Server from SEP 11.x later than MR2 are not vulnerable. Reporting has replaced AMS2 as the recommended method of alerting. Symantec recommends that customers who are still using AMS2 switch to Reporting to manage alerts in their environments.

If the customer is unable to switch to Reporting immediately or upgrade to a non-vulnerable version then Symantec recommends that the customer either disable AMS2 as a temporary mitigation or completely uninstall AMS2.

As an additional mitigation, Symantec recommends blocking port 38292 in the corporate environment. This will effectively disable the alert service from sending or receiving messages.

Best Practices

As part of normal best practices, Symantec strongly recommends:

• Restrict access to administration or management systems to privileged users.
• Restrict remote access, if required, to trusted/authorized systems only.
• Run under the principle of least privilege where possible to limit the impact of exploit by threats.
• Keep all operating systems and applications updated with the latest vendor patches.
• Follow a multi-layered approach to security. Run both firewall and anti-malware applications, at a minimum, to provide multiple points of detection and protection to both inbound and outbound threats.
• Deploy network and host-based intrusion detection systems to monitor network traffic for signs of anomalous or suspicious activity. This may aid in detection of attacks or malicious activity related to exploitation of latent vulnerabilities.

ACKNOWLEDGEMENTS

Symantec would like to thank the finders of these issues:

Junaid Bohio of Vulnerability Research Team, Telus Security Labs
An anonymous finder through Tippingpoint's Zero Day Initiative(ZDI)
Nahuel Riva of Core Security Technologies

REFERENCES

BID: SecurityFocus (http://www.securityfocus.com) has assigned Bugtraq ID(BID) 45936 to these vulnerabilities.

CVE: These issues are candidates for the Common Vulnerabilities and Exposures (CVE) list (http://cve.mitre.org), which standardizes names for security problems. CVE-2010-0110 has been assigned to these vulnerabilities