SecurityTracker.com
    Home    |    View Topics    |    Search    |    Contact Us    |   

SecurityTracker
Archives


 


Category:   Application (Generic)  >   VMware Vendors:   VMware
VMware May Fail to Set Safe SSL Key File Permissions
SecurityTracker Alert ID:  1016536
SecurityTracker URL:  http://securitytracker.com/id/1016536
CVE Reference:   CVE-2006-3589   (Links to External Site)
Date:  Jul 19 2006
Impact:   Disclosure of authentication information
Vendor Confirmed:  Yes  

Description:   A vulnerability was reported in VMware. A local user may be able to read the SSL key file used for administrative connections.

The 'vmware config.pl' configuration program may fail to set safe file permissions on the generated SSL Key files used for encrypting remote administrative connections. A local user may be able to read the key file.

The following products are affected:

VMware Player for Linux
VMware Workstation for Linux
VMware Server for Linux
VMware Infrastructure 3

The VMware Player for Windows, VMware Workstation for Windows, and VMware Server for Windows are not affected.

VMware credits Nick Breese and security-assessment.com with reporting this vulnerability.

Impact:   A local user may be able to obtain the SSL key file used for protecting administrative connections.
Solution:   No solution was available at the time of this entry. The vendor is working on a fix.

The vendor has described the following workaround [quoted]:

Manually change the permissions on the key and certificate to its intended values. The following commands would be appropriate on a default installation:

# chmod 400 /etc/vmware/ssl/rui.key
# chmod 444 /etc/vmware/ssl/rui.crt

The VMware advisory is available at:

http://kb.vmware.com/kb/2467205

Vendor URL:  kb.vmware.com/kb/2467205 (Links to External Site)
Cause:   Access control error
Underlying OS:  Linux (Any)

Message History:   None.


 Source Message Contents

Subject:  [Full-disclosure] VMSA-2006-0003 VMware possible incorrect

This is a multi-part message in MIME format.
--------------080508030205090404080209
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


- -------------------------------------------------------------------
                   VMware Security Advisory

Advisory ID:       VMSA-2006-0003
Synopsis:          VMware possible incorrect permissions on SSL key files
			VMware Player for Linux
			VMware Workstation for Linux
			VMware Server for Linux
			VMware ESX Server 2.x
			VMware Infrastructure 3

			NOT VULNERABLE: VMware Player for Windows
			NOT VULNERABLE: VMware Workstation for Windows
			NOT VULNERABLE: VMware Server for Windows
VMTN Knowledge Base URL: http://kb.vmware.com/kb/2467205
Issue date:        2006-07-18
Updated on:        2006-07-18
CVE Name:          CVE-2006-3589
- -------------------------------------------------------------------

1. Summary:

file permissions on the generated SSL Key files which is used for 
encrypting traffic for remote administrative connections.

VMware has given this issue a Priority 3 severity rating.

2. Relevant release:

VMware Player for Linux
VMware Workstation for Linux
VMware Server for Linux
VMware Infrastructure 3

NOT VULNERABLE: VMware Player for Windows
NOT VULNERABLE: VMware Workstation for Windows
NOT VULNERABLE: VMware Server for Windows

3. Problem description:

The script vmware-config.pl sets permissions on the key and
certificate files to safe values. However this script does not use
the safe_chmod() subroutine which reports errors on failure.
Instead, the native Perl chmod() function is used, without any
return code checking.

Because the safe_chmod() subroutine is not used and no return code
checks are performed, the user is not alerted if the chmod() fails.
Depending on the umask being used at the time this could leave the
key file readable to any local user on the system.

4. Solution:

VMware is working on a fix, and there is a workaround.  Manually
change the permissions on the key and certificate to its intended
values. The following commands would be appropriate on a default
installation:

# chmod 400 /etc/vmware/ssl/rui.key
# chmod 444 /etc/vmware/ssl/rui.crt

The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2006-3589 to this issue.

5. References:

http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3589

6. Acknowledgments

VMware would like to thank Nick Breese and security-assessment.com.

7. Contact:

http://www.vmware.com/security

Copyright 2006 VMware Inc. All rights reserved.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)

iD8DBQFErFC+LsZLrftG15MRAmm8AKCj6Li52ztaGuPO78GyqXWaQSLTRgCaAnj3
3Wg2D5U/S9SkrzDSTR9OsWI=
=wppd
-----END PGP SIGNATURE-----


--------------080508030205090404080209
Content-Type: text/plain;
 name="VMSA-2006-0003.txt.asc"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline;
 filename="VMSA-2006-0003.txt.asc"

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


- -------------------------------------------------------------------
                   VMware Security Advisory

Advisory ID:       VMSA-2006-0003
Synopsis:          VMware possible incorrect permissions on SSL key files
			VMware Player for Linux
			VMware Workstation for Linux
			VMware Server for Linux
			VMware ESX Server 2.x
			VMware Infrastructure 3

			NOT VULNERABLE: VMware Player for Windows
			NOT VULNERABLE: VMware Workstation for Windows
			NOT VULNERABLE: VMware Server for Windows
VMTN Knowledge Base URL: http://kb.vmware.com/kb/2467205
Issue date:        2006-07-18
Updated on:        2006-07-18
CVE Name:          CVE-2006-3589
- -------------------------------------------------------------------

1. Summary:


VMware has given this issue a Priority 3 severity rating.

2. Relevant release:

VMware Player for Linux
VMware Workstation for Linux
VMware Server for Linux
VMware Infrastructure 3

NOT VULNERABLE: VMware Player for Windows
NOT VULNERABLE: VMware Workstation for Windows
NOT VULNERABLE: VMware Server for Windows

3. Problem description:

The script vmware-config.pl sets permissions on the key and 
certificate files to safe values. However this script does not use 
the safe_chmod() subroutine which reports errors on failure. 
Instead, the native Perl chmod() function is used, without any 
return code checking.
 
Because the safe_chmod() subroutine is not used and no return code 
checks are performed, the user is not alerted if the chmod() fails. 
Depending on the umask being used at the time this could leave the 
key file readable to any local user on the system. 

4. Solution:

VMware is working on a fix, and there is a workaround.  Manually 
change the permissions on the key and certificate to its intended 
values. The following commands would be appropriate on a default 
installation:

# chmod 400 /etc/vmware/ssl/rui.key
# chmod 444 /etc/vmware/ssl/rui.crt 

The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2006-3589 to this issue.  

5. References:

http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3589

6. Acknowledgments

VMware would like to thank Nick Breese and security-assessment.com.

7. Contact:

http://www.vmware.com/security

Copyright 2006 VMware Inc. All rights reserved.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)

iD8DBQFErFC+LsZLrftG15MRAmm8AKCj6Li52ztaGuPO78GyqXWaQSLTRgCaAnj3
3Wg2D5U/S9SkrzDSTR9OsWI=
=wppd
-----END PGP SIGNATURE-----

--------------080508030205090404080209
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
--------------080508030205090404080209--

 
 


Go to the Top of This SecurityTracker Archive Page





Home   |    View Topics   |    Search   |    Contact Us

This web site uses cookies for web analytics. Learn More

Copyright 2019, SecurityGlobal.net LLC