I previously made the changes necessary to deal with the Oracle Padding Vulnerability.  Once Microsoft made the actual patch avail, I updated my server via Windows Update.  I then reverted my web.config to the original settings prior to the temp workaround.   Since I reverted my web.config, I am now getting the following error in my logs:

 "A critical ASP.NET Oracle Padding vulnerability has been identified in your website. We recommend that you patch your site immediately. For more information on this issue and instructions on how to patch your site refer to http://www.dotnetnuke.com/aspnetpoet.aspx".  

Should this message still be appearing?  Does it mean that I am still vulnerable, or is it just not seeing the patch from MS?  Is there a test I can perform to ensure I am not still exposed?

Thanks in advance,

Kevin

ps - here is the complete error log:

AssemblyVersion: -1
PortalID: -1
PortalName: 
UserID: -1
UserName: 
ActiveTabID: -1
ActiveTabName: 
RawURL: 
AbsoluteURL: 
AbsoluteURLReferrer: 
UserAgent: 
DefaultDataProvider: 
ExceptionGUID: 
InnerException: A critical ASP.NET Oracle Padding vulnerability has been identified in your website. We recommend that you patch your site immediately. For more information on this issue and instructions on how to patch your site refer to http://www.dotnetnuke.com/aspnetpoet.aspx
FileName: 
FileLineNumber: -1
FileColumnNumber: -1
Method: 
StackTrace: 
Message: System.Security.SecurityException: A critical ASP.NET Oracle Padding vulnerability has been identified in your website. We recommend that you patch your site immediately. For more information on this issue and instructions on how to patch your site refer to http://www.dotnetnuke.com/aspnetpoet.aspx The Zone of the assembly that failed was: MyComputer
Source: 
Server Name: S1

Great!  Thanks for the quick response.

Kevin