Advertisement

07.28.2008 at 02:34PM PDT, ID: 23602276
[x]
Attachment Details

Security scan returns "IP address revealed in content-location header" using DotNetNuke (DNN)

[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

7.8
We are using DotNetNuke (DNN) and a security scan shows the vulnerability "IP address is revealed in the content-location field in the TCP header" and the fix is to use Microsoft KB 834141.  The problem is that the Microsoft fix has you configure IIS to use the FQDN or a set host name instead of the internal IP address.  Unfortunately, after you perform this fix and set a host name for the return it apparently takes effect before DNN can read the portal alias from the original URL request and therefore breaks DNN (large number of portals, so host headers aren't an option).

Does anyone have an alternative method for handling a GET request with a blank host header that doesn't break the DNN portal parsing methodology or a way to patch this security vulnerability for DNN?
Answered By: auctionpay
Expert Since: 12/28/2006
Accepted Solutions: 1
auctionpay has been an Expert for 2 years, during which he has posted 10 comments and answered 1 question. auctionpay is just one of 982 experts in the Networking Security Vulnerabilities Zone. 1 expert collaborated on this answer, which was graded an "A" by the asker.
 
 
20081119-EE-VQP-47 / EE_QW_2_20070628