-----BEGIN PGP SIGNED MESSAGE-----
AUSCERT External Security Bulletin Redistribution
Symantec LiveUpdate Administrator 2.3 Insecure File Permissions
19 June 2012
AusCERT Security Bulletin Summary
Product: Symantec LiveUpdate Administrator
Operating System: Windows
Impact/Access: Administrator Compromise -- Existing Account
CVE Names: CVE-2012-0304
Comment: Note: there is proof of concept code available for this vulnerability.
There is also some reports that the update does not fully resolve the
issue. Symantec engineers are currently investigating this and will
provide a new update if necessary.
- --------------------------BEGIN INCLUDED TEXT--------------------
Security Advisories Relating to Symantec Products - Symantec LiveUpdate
Administrator 2.3 Insecure File Permissions
June 15, 2012
Insecure File Permissions Local Elevation of Privilege - Medium
CVSS2 Impact Exploitability CVSS2 Vector
6.89 10 3.9 AV:L/AC:M/Au:N/C:C/I:C/A:C
Exploit Publicly Available: Yes, Proof of Concept
Symantec LiveUpdate Administrator 2.3 and prior install some files with
insecure file permissions during a default installation. These files allow full
control permission to everyone which could result in arbitrary command
execution with elevated privileges on the system.
Product Version Solution
Administrator Windows version 2.3 and prior Update to Symantec LiveUpdate
Administrator Windows version
Symantec Live Update 2.3.1
Symantec was notified of insecure file permissions following a default
installation of Symantec LiveUpdate Administrator. Permissions on the
installed files allow full control to 'Everyone'. An authorized but
non-privileged user or an unauthorized user with access to an account on the
local system hosting Symantec LiveUpdate Administrator could potentially
leverage these improper permissions to read arbitrary system files with
elevated privileges. There is also a potential for the unauthorized local user
to successfully overwrite arbitrary files or create scripts that execute with
SYSTEM privileges. Successful exploitation could result in an unauthorized
local user executing arbitrary commands with privileged access on the system.
Symantec engineers confirmed the issue and addressed it in Symantec LiveUpdate
Administrator 2.3.1. Symantec LiveUpdate Administrator 2.3.1 is available to
customers through normal support channels. Symantec recommends customers who
have not yet upgraded to the latest release of Symantec LiveUpdate
Administrator do so as soon as possible.
NOTE: There are public reports suggesting that Symantec LiveUpdate
Administrator 2.3.1 does NOT fully address all of the permissions issue.
Symantec engineers are reviewing this currently and will release an update to
LiveUpdate Administrator 2.3.1 as needed.
Symantec is not aware of any adverse customer impact from this issue.
As part of normal best practices, Symantec strongly recommends:
* Restrict access to administration or management systems to privileged users.
* Disable remote access or restrict it to trusted/authorized systems only.
* Keep all operating systems and applications updated with the latest vendor
* 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
Symantec credits Tenable Network Security, http://www.tenable.com/ for
reporting this issue.
BID: Security Focus, http://www.securityfocus.com, has assigned a Bugtraq ID
(BID) 53903 to this issue for inclusion in the Security Focus vulnerability
CVE: This issue is a candidate for inclusion in the CVE list
(http://cve.mitre.org), which standardizes names for security problems. The CVE
ID CVE-2012-0304 has been assigned to this issue.
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 email@example.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 firstname.lastname@example.org. 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.
Symantec Vulnerability Response Policy
Symantec Product Vulnerability Management PGP Key
Copyright (c) 2012 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 email@example.com
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 firstname.lastname@example.org
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
* 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: June 15, 2012
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to email@example.com
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
Australian Computer Emergency Response Team
The University of Queensland
Internet Email: firstname.lastname@example.org
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----