Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...DNN 5.5.1 upgrade does not comply with MS security patch recommendationsDNN 5.5.1 upgrade does not comply with MS security patch recommendations
Previous
 
Next
New Post
9/22/2010 8:56 PM
 
CT

Joined: 10/2/2006
Posts: 92
In my hands on my systems, the DNN upgrade from 5.5.0 to 5.5.1 does not comply with Microsoft's recent security patch recommendations.

I experienced the same problem on an upgrade on a dev installation and on a production installation both going from 5.5.0 to 5.5.1. Both upgrades executed smoothly without any report of any problems - all green "success". Both installations continued to operate smoothly without any apparent problems.

However, both upgrades rewrote the customErrors mode attribute as mode="RemoteOnly". Unfortunately, Scott Gu's blog post at

http://weblogs.asp.net/scottgu/archive/2010/09/18/important-asp-net-security-vulnerability.aspx

makes clear that mode="RemoteOnly" is NOT sufficient. He states explicitly:

"Important: It is not enough to simply turn on CustomErrors or have it set to RemoteOnly. You also need to make sure that all errors are configured to return the same error page.  This requires you to explicitly set the “defaultRedirect” attribute on the <customErrors> section and ensure that no per-status codes are set."

Of course, the solution is simple. Just manually edit your web.config file and change the mode so that it reads mode="On". 
CT
 
New Post
9/23/2010 5:53 AM
 
Sebastian Leupold


Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

www.dnnwerk.de
Joined: 3/8/2004
Posts: 46212
CT, the difference of ON and remoteOnly is what happens when viewed from localhost (where a possible intruder should not have access to - otherwise you are already in trouble ;) The more important part of the fix is the defaultRedirect, which needs to get applied and redirect to a single error page for all types of errors.
Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/23/2010 6:10 AM
 
Jan Olsmar


www.olsmar.com/
Joined: 9/19/2005
Posts: 1354
Why is not the "small sleep delay" included?
ScottGU recommend this in the blog.
 
New Post
9/23/2010 11:25 AM
 
CT

Joined: 10/2/2006
Posts: 92
Sebastian,

I have been aware of the difference between Off, RemoteOnly and On for many years.

This is a matter of what text the DNN upgrade has re-written to the web.config file itself which can of course be examined in any text editor after the upgrade to see what the upgrade did to the file.

This is a matter of whether the DNN upgrade complies with what Scott Guthrie and Microsoft have recommended, and in general, the appearance of whether or not DNN complies with such recommendations.

If DNN wishes to argue that Scott Guthrie and Microsoft's recommendations are wrong or unnecessary, then perhaps DNN should take that discussion up with them but not me since I am neither Scott Guthrie nor Microsoft. But it does not alter the appearance that DNN failed to comply with the Microsoft recommendations in a publicized situation where Scott Gu explicitly stated that "RemoteOnly" was NOT sufficient.
CT
 
New Post
9/23/2010 12:00 PM
 
Alex Shirley


Joined: 1/30/2006
Posts: 5038
Jan Olsmar wrote:
Why is not the "small sleep delay" included?
ScottGU recommend this in the blog.

Check errorpage.aspx.vb in 5.5.1 for "small delay".

 

CT wrote:
In my hands on my systems, the DNN upgrade from 5.5.0 to 5.5.1 does not comply with Microsoft's recent security patch recommendations.

I experienced the same problem on an upgrade on a dev installation and on a production installation both going from 5.5.0 to 5.5.1. Both upgrades executed smoothly without any report of any problems - all green "success". Both installations continued to operate smoothly without any apparent problems.

However, both upgrades rewrote the customErrors mode attribute as mode="RemoteOnly". Unfortunately, Scott Gu's blog post at

http://weblogs.asp.net/scottgu/archive/2010/09/18/important-asp-net-security-vulnerability.aspx

makes clear that mode="RemoteOnly" is NOT sufficient. He states explicitly:

"Important: It is not enough to simply turn on CustomErrors or have it set to RemoteOnly. You also need to make sure that all errors are configured to return the same error page.  This requires you to explicitly set the “defaultRedirect” attribute on the section and ensure that no per-status codes are set."

Of course, the solution is simple. Just manually edit your web.config file and change the mode so that it reads mode="On". 

So 5.5.1 upgrade and install sets web.config to ....

<customErrors mode="RemoteOnly" redirectMode="ResponseRewrite" defaultRedirect="~/errorpage.aspx" />

So I'm not seeing the issue.

Alex Shirley
 
 Page 1 of 4
1234Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...DNN 5.5.1 upgrade does not comply with MS security patch recommendationsDNN 5.5.1 upgrade does not comply with MS security patch recommendations


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out