Products

Solutions

Resources

Partners

Community

Blog

About

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...Administration ...Administration ...Security Scans report high level errors for internal ip address in content-location Security Scans report high level errors for internal ip address in content-location
Previous
 
Next
New Post
8/4/2008 4:29 PM
 

We are a portal provider for non-profits online giving.  As such we come under PCI rules and periodically are scanned for security vulnerabilities.   The scans are showing "IP address is revealed in the content-location field in the TCP header" and the suggested fix is to use Microsoft KB 834141.  However that breaks dnn.

How do we fix this?

thanks,
scott

 
New Post
8/4/2008 4:55 PM
 

Hello,

I wasn't aware of this issue, and I definately don't think it's very common as the patch is a few years old and this is only the second time I've seen a report of problems. I did a bit of searching and it seems that a number of machines running SSL or with outlook web access had problems with this patch (or wide code that uses request.issecureconnection ). You could try searching for that term in the code and setting breakpoints on it and seeing if that is your issue.

During the time searching the only note I found of someone resolving the issue without backing the patch out was the following (bottom of the page posts)http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_23461181.html

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/7/2008 11:40 AM
 

Thanks for the pointer but that resolves back to the same suggestion to set the hostname in IIS.  The problem is that breaks the dnn aliasing.  The big time issue we're faced with here is that  If we can't pass the security scans then we have to find a different solution than dnn.  I'd rather stay with dnn but I need a pointer on where to patch this.  Since it's in the host headers going back I'm really at a loss.

 
New Post
8/7/2008 12:10 PM
 

What is your issue with IIS Host headers and DNN Portal Aliases?


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Security Scans report high level errors for internal ip address in content-location Security Scans report high level errors for internal ip address in content-location


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