Symantec Security Information Manager Console Security Issues

SUMMARY

Symantec’s Security Information Manager (SSIM) management console is susceptible to multiple security issues. Successful exploitation could result in potential cookie stealing, session hijacking, unauthorized disclosure of sensitive application information and potential for unauthorized database manipulation.

AFFECTED PRODUCTS

Product

|

Version

|

Build

|

Solution

—|—|—|—

Symantec Security Information Manager Appliance

|

4.7.x

|

all

|

Update to SSIM 4.8.1

Symantec Security Information Manager Appliance

|

4.8.0

|

all

|

Update to SSIM 4.8.1

ISSUES

CVSS2

Base Score

|

Impact

|

Exploitability

|

CVSS2 Vector

—|—|—|—

Symantec Security Information Manager (SSIM) Java Console XSS - Medium

6.8

|

6.4

|

8.6

|

AV:N/AC:M/Au:N/C:P/I:P/A:P

Symantec Security Information Manager (SSIM) SQL Injection - Medium

4.7

|

6.4

|

4.1

|

AV:A/AC:L/Au:M/C:P/I:P/A:P

Symantec Security Information Manager (SSIM) Information Disclosure - Low

2.9

|

2.9

|

5.5

|

AV:A/AC:M/Au:N/C:P/I:N/A:N

CVE

|

BID

|

Description

—|—|—

CVE-2013-1613

|

BID 60796

|

SSIM Java Console SQL Injection

CVE-2013-1614

|

BID 60797

|

SSIM Java Console XSS

CVE-2013-1615

|

BID 60798

|

SSIM Java Console Information Disclosure

MITIGATION

Details

Symantec was notified of multiple security issues impacting the SSIM management console.

Cross-site scripting, both reflected and stored are present in some SSIM console interface pages. These result from insufficient validation/sanitation of client input and application output. Successfully targeting of these XSS instances would require malicious script be hosted on a network client system to attempt to target the SSIM console during a manual or scheduled network scan. This could be accomplished by a malicious authorized network user placing arbitrary script on a network client. Or, by enticing an authorized client user to follow a link or visit a web page hosting malicious script that could be downloaded to the client system. Successful exploitation could possibly result in stealing user cookies or potentially leveraged to hijack an authorized user session.

The SSIM console does not properly restrict queries to web-GUI APIs which could be manipulated to potentially disclose sensitive information to unauthorized network users. This information could possibly be leveraged in any follow-on attempts to further compromise the application or network.

The SSIM console does not sufficiently sanitize authorized client queries made against the database. A malicious user who has or can gain authorized access to a valid account could potentially inject arbitrary SQL database queries in attempts to further compromise the database.

Symantec Response

Symantec engineers verified these submitted issues as being identified during recent internal review. They have been addressed in Symantec Security Information Manager 4.8.1.

Symantec knows of no exploitation of or adverse customer impact from these issues.

Symantec Security Information Manager 4.8.1 is currently available through normal update channels.

Best Practices

As part of normal best practices, Symantec strongly recommends:

•     Restrict access to administration or management systems to privileged users.
  

•     Disable remote access if not required or restrict it to trusted/authorized systems only.
  

•     Where possible, limit exposure of application and web interfaces to trusted/internal networks only.
  

•     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 credits Hacktive Security Research and Development team for reporting these issues to us and coordinating with us as we resolved them.

REFERENCES

BID: Security Focus, http://www.securityfocus.com, has assigned a Bugtraq ID (BID) to these issues for inclusion in the Security Focus vulnerability database.

CVE: These issues are candidates for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.