Products

Solutions

Resources

Partners

Community

About

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 ...SM PCI Scan: Backup Files DisclosureSM PCI Scan: Backup Files Disclosure
Previous
 
Next
New Post
7/27/2017 9:20 AM
 
Hello, everyone

We had performed security checks by security metrics PCI scan. Currently it is fails with an issue below:

Title
Backup Files Disclosure

Synopsis
It is possible to retrieve file backups from the remote web server.

Impact
By appending various suffixes (ie: .old, .bak, ~, etc...) to the names of various files on the remote host, it seems possible to retrieve their contents, which may result in disclosure of sensitive information. See also : http://projects.webappsec.org/Predictable-Resource-Location

Resolution
Ensure the files do not contain any sensitive information, such as credentials to connect to a database, and delete or protect those files that should not be accessible.

Data Received
It is possible to read the following backup files : - File : /Home/ctl/SendPassword~ URL : https://mysite.com/Home/ctl/SendPassword~
...(and a long list of other same urls)...


Does anybody have any thoughts, how this should be resolved? We are on DNN9, Windows Server 2012 R2.

Thank you!
 
New Post
7/27/2017 3:15 PM
 
DNN usually does not create backup files, but a 3rd party software might.
please check your IIS website folder, whether there is a folder /Home/ containing .ascx, .aspx or other code files. This folder is not a default dnn folder.
otherwise, it might just be a false positive, as /ctl/ is a virtual path for controls to be displayed on any page by DNN, and not a backup.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/31/2017 10:46 AM
 

Hello, Sebastian!

Thank you for you reply. I had reviewed a root of my IIS folder and there is no Home folder. But I have a Home page in DNN. We are not using third party modules except own developed and standard modules from DNN like HTML, etc. 

Am I correctly understand, that in this case an issue from SM can be omitted? Or may be it is possible to resolve it via url rewriting?

http://www.dnnsoftware.com/wiki/url-rewriting

It is possible to throw 404 error, when requested URL was not found, because right now, when I try to request, let's say, https://mysite.com/Page/SubPage~ DNN redirects me to https://mysite.com/Page

 

Thank you,

Dennis

 
New Post
7/31/2017 1:27 PM
 
Dennis,
it sounds to me that this issue can be omitted, there are multiple URLs for the send password control by design, maybe you can exclude it from search indexing.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/31/2017 2:27 PM
 

Sesbastian,

Frankly speaking, log from Security Metrics contains URLs for all pages from my site with (~) at the end, not only for password. The question is, is it possible to disallow DNN to rewrite unknown URLs? In other words, allow known URLs and throw 404 for URLs with (~) at the end.

 

Thank you!

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...SM PCI Scan: Backup Files DisclosureSM PCI Scan: Backup Files Disclosure


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