Modify SQL Server built-in stored procedures

server| stored procedures SQL Server is estimated to be installed, or otherwise, with a number of dangerous stored procedures built into it. Can read the registry information, can write registry information, read disk sharing information and so on ... You see here, in the mind may be thinking, my site has other code, and not like the Query Analyzer can directly output the results. Give you this permission, also can't how, still can't see the information. It would be a big mistake if you think so. Hint, if the attacker has permission to create TABLE, then creates a temporary table, and then inserts the information into the table, then select it, and then compare with the number, let SQL Server error, then the result is all out ... So we have to report a better way to kill, do not miss the attitude of repair.
　　
First, list the dangerous built-in stored procedures:
　　
xp_cmdshell
　　
Xp_regaddmultistring
　　
Xp_regdeletekey
　　
Xp_regdeletevalue
　　
Xp_regenumkeys
　　
Xp_regenumvalues
　　
Xp_regread
　　
Xp_regremovemultistring
　　
Xp_regwrite
　　
ActiveX Automatic scripting:
　　
sp_OACreate
　　
sp_OADestroy
　　
sp_OAMethod
　　
sp_OAGetProperty
　　
sp_OASetProperty
　　
sp_OAGetErrorInfo
　　
sp_OAStop
　　
All of the above are in our ban, such as xp_cmdshell shielding method:
　　
Sp_dropextendedproc ' xp_cmdshell '
　　
If necessary, then use
　　
Sp_addextendedproc ' xp_cmdshell ', ' Xpsql70.dll '
　　
for recovery. If you don't know which. dll file xp_cmdshell is using, you can use the
　　
Sp_helpextendedproc Xp_cmdshel
　　
To see which dynamic join Library the xp_cmdshell is using. In addition, after the xp_cmdshell is blocked, we still need to do is to make the Xpsql70.dll file