1. /
  2. Security Response/
  3. Security Updates Detail

Security Advisories Relating to Symantec Products - Symantec LiveUpdate Administrator Unauthenticated/Unauthorized Account Access Modification and SQL injections

SYM14-005

March 27, 2014

Revisions

 

None

 

Severity

 

CVSS2

Base Score

Impact

Exploitability

CVSS2 Vector

LUA Unauthenticated/Unauthorized Account Access Modification 7.9 - High

7.9

10

5.5

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

 

LUA Unauthenticated SQL Injections 6.9 - Medium

6.3

8.5

5.5

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

 


Overview

The management GUI for Symantec LiveUpdate Administrator does not properly protect the forgotten password functionality of the web interface.  An unauthorized individual with knowledge of the email address for an authorized LUA user can potentially force an arbitrary password reset leading to unauthorized access.

The management GUI for Symantec LiveUpdate Administrator does not sufficiently sanitize the inputs for the queries made against the backend database which could lead to unauthorized access to data stored in the database.

Affected Products

Product

Version

Build

Solution(s)

Symantec LiveUpdate Administrator

2.x

2.3.2 and prior

Upgrade to LUA 2.3.2.110

 

Products not affected

Product

Version

Build

Symantec LiveUpdate Administrator

1.x

All


Details

The Symantec LiveUpdate Administrator management web interface does provide proper protection for the login/password functionality.  An authorized but malicious network user or an unauthorized malicious individual who can gain access to the network environment could potentially force a password reset of an authorized LUA user.  The attacker would require knowledge of an authorized LUA user’s email address to attempt to force an arbitrary password reset.  If successful, this could allow full access to the administrator web interface.

The Symantec LiveUpdate Administrator management web interface does not sufficiently sanitize inputs to queries made against the database which could lead to unauthorized access to data stored in the database.  Successful exploitation could potentially expose sufficient information allowing access to other LiveUpdate Administrator servers on the network or the capability to force network or CPU denial –of-service of network clients by providing extraneous files for download to client systems.

In a normal, recommended installation, the Symantec LiveUpdate Administrator management web interface should not be accessible external to the network which should provide some mitigation against external but not internal attacks.  An external attacker would need to gain network access to launch this type of attack.  This would normally entail enticing an authorized network user to access a malicious link in a context such as a web link or in an email to initially compromise a client system on the network.

 

Symantec Response
Symantec product engineers verified these issues and have released updates to resolve them.
Customers should apply the available updates to Symantec LiveUpdate Administrator 2.3.2.  Symantec is not aware of exploitation of or adverse customer impact from these issues.

Update Information

Symantec LiveUpdate Administrator update version 2.3.2.110is currently available for upgrade as identified in Symantec Support knowledge base article TECH 134809, http://www.symantec.com/business/support/index?page=content&id=TECH134809

 

Best Practices
As part of normal best practices, Symantec strongly recommends the following:


  • Restrict access to administrative or management systems to authorized 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 potential exploit.
  • Keep all operating systems and applications current with vendor patches.
  • Follow a multi-layered approach to security. At a minimum, run both firewall and anti-malware applications 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 the detection of attacks or malicious activity related to the exploitation of latent vulnerabilities.

Credit
Symantec thanks Stefan Viehböck (discovery, analysis, coordination) from the SEC Consult Vulnerability Lab (https://www.sec-consult.com/) for reporting these issues and working with us as we addressed them.

References

BID: Security Focus, http://www.securityfocus.com, has assigned Bugtraq IDs (BIDs) 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. 

 

CVE

BID

Description

CVE-2014-1644

BID 66399

LUA Unauthorized Account Access Modification

CVE-2014-1645

BID 66400

LUA Unauthenticated SQL Injection

 

 

 

 

Symantec takes the security and proper functionality of our products very seriously. As founding members of the Organization for Internet Safety (OISafety), Symantec supports and follows responsible disclosure guidelines.
Please contact secure@symantec.com if you feel you have discovered a security issue in a Symantec product. A member of the Symantec Product Security team will contact you regarding your submission to coordinate any required response. Symantec strongly recommends using encrypted email for reporting vulnerability information to secure@symantec.com. The Symantec Product Security PGP key can be found at the location below.
Symantec has developed a Product Vulnerability Response document outlining the process we follow in addressing suspected vulnerabilities in our products. This document is available below.

Copyright (c) by Symantec Corp.

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Product Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com

Disclaimer

The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Product Security, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.
* Signature names may have been updated to comply with an updated IPS Signature naming convention. See http://www.symantec.com/business/support/index?page=content&id=TECH152794&key=54619&actp=LIST for more information.
Last modified on: March 27, 2014
Security Response Blog
The State of Spam