Hacking Target - Administration and Configuration

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

Home All Forums

2/3/2016 3:23 PM

Ax. Wx.

Joined: 10/19/2005

Posts: 57

Hacking Target

Hello All,

I was wondering if any of you had seen this in your installation. I found some domains in my PortalAlias table that I did not put there. I am looking through my logs and I am finding a GET to Default.aspx at the time of the INSERT and the HTTP response is 302, but I do not see any content there that indicates that an INSERT was done or SQL passed to the site. In any case, i am a little baffled because Users must be approved after registration and I do not see administrative logins that would allow them to write to PortalAlias from the DNN UI. I was thinking of making PortalAlias ReadOnly until I can figure out where these entries came from. Has anyone experienced this out in the wild? i am using 7.4.0 with the InstallWizard.aspx renamed
thanks,
~aw

2/4/2016 2:45 AM

Michael Tobisch

https://www.dnnwerk.at
Joined: 6/27/2005

Posts: 2083

Re: Hacking Target

There is a setting called "Auto Add Site Alias" (Under Portal Settings :: Advanced Settings :: Site Aliases). Please check if this is on or off, and turn it off when its on. Does this still happen?

On the other hand: How do your standard aliases look like, and how do the aliases look that have been added?

Happy DNNing!
Michael

Michael Tobisch
DNN★MVP

2/4/2016 11:10 AM

Ax. Wx.

Joined: 10/19/2005

Posts: 57

Re: Hacking Target

I actually have a constraint on the table right now, but I did have that setting checked. It is unchecked now. What is the purpose of this setting? How could it be invoked without user authentication? AS far as the aliases added there were alot, some were raw IPs and others were specific domains...known ones like yahoo for example. It made me wonder if the DNN web application responded with a useful header in the 302 that allowed for anonymizing the source IP on their way to one of these URLs.

Thanks for pointing me at that setting, though I really wonder what its utility is that makes it a default out of the box.

~aw

2/8/2016 3:24 AM

Michael Tobisch

https://www.dnnwerk.at
Joined: 6/27/2005

Posts: 2083

Re: Hacking Target

Here is a Wiki entry about the Portal Alias: http://www.dnnsoftware.com/wiki/porta...

Maybe this is also interesting for you: https://www.youtube.com/watch?v=VMNyB...

Basically: The Auto Add Portal Alias function adds any new, valid site alias requested to the site aliases - this is not depending on the fact if a user is anonymous or not, or if he is a normal user, an administrator or a superuser. This happens in the background. Any domain name bound to the underlying IIS website can be used to request the website when this setting is on.

You should also check the host header settings in your IIS and set only the appropriate host headers.

Happy DNNing!
Michael

Michael Tobisch
DNN★MVP

2/11/2016 1:00 PM

Ax. Wx.

Joined: 10/19/2005

Posts: 57

Re: Hacking Target

I am still baffled as to how this could happen without such host headers being sent. All of these domains and IP addresses are completely unknown to my IIS installation. Again this seems to be a way to get a response from the DNN web application that can be leveraged in some way that I am not sure about. Also, it means there is some way to create Portal Aliases "remotely" that I have yet to identify. Unnerving...

Page 1 of 3

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:

No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
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.
Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
No Flaming or Trolling.
No Profanity, Racism, or Prejudice.
Site Moderators have the final word on approving / removing a thread or post or comment.
English language posting only, please.

Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

DNN Corp. (DotNetNuke)