|
Microsoft Commerce Server Registry Permissions and Authentication Bypass
|
|
Secunia Advisory:
|
SA9176
|
|
|
Release Date:
|
2003-07-04
|
|
Last Update:
|
2006-03-21
|
|
Popularity:
|
7,021 views
|
|
|
Critical:
|
Moderately critical
|
|
Impact:
|
Security Bypass
Exposure of sensitive information
|
|
Where:
|
From remote
|
|
Solution Status:
|
Partial Fix
|
|
| Software: | Microsoft Commerce Server 2002
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
A vulnerability and a security issue have been reported in Microsoft Commerce Server, which can be exploited by malicious users to gain knowledge of sensitive information and by malicious people to bypass certain security restrictions.
1) The password for the SQL Server backend is stored encoded in the registry in the key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Commerce Server" if authentication has been configured to SQL Server authentication. However, this registry key has weak permissions allowing any user to read the encoded password.
By decoding the password, a malicious user could gain knowledge of the administrative SQL Server password.
The vulnerability has been reported in version 2002. Other versions may also be affected.
2) An error in the sample files within the "AuthFiles" directory can be exploited to bypass authentication and logon as a valid user without knowing the password.
Successful exploitation requires knowledge of a valid user name.
The security issue has been reported in version 2002. Prior versions may also be affected.
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
