• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

MsSQL WebAdmin Permissions - serious

ryanz

Basic Pleskian
Hi,

When we log into the MsSQL database using the WebAdmin (either ASP.NET or myLittleAdmin) we can see and access all databases on the SQL server. These include the System DB's and the User DB's.

The concern is that anyone can fiddle with the System DB's.

How do we correct this?

Plesk 9.0
Windows 2008 Server
MsSQL Server 2005
 
Hi Ryan,

Here's a similar issue I have experienced few days ago. I restored a customer database backup on a shared MSSQL 2005 server which came with an active 'guest' user with dbo privileges. Outcome was, anyone on that shared server could view and access that database alongwith their's, via WebAdmin! Might pay to check if db 'guest' users are active.
 
Yes, there is a guest user with connect permissions but I can't change this.
The error message is:

Revoke failed for Database 'master'. (Microsoft.SqlServer.Smo)

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)


So I removed that user but it was recreated when sql server restarted.
These are links I found:
http://www.mssqltips.com/tip.asp?tip=1172
http://msdn.microsoft.com/en-us/library/ms190928.aspx
 
Back
Top