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 ...Thwarting Registration exploitsThwarting Registration exploits
Previous
 
Next
New Post
1/17/2015 6:12 PM
 

Thanks Joe

I am on Version 7.3.4.  But I am still getting spam registrations.

I have created a new registration page and added it to all my sites requiring registration, changing the registration page spec to the name of my custom page.

I have added the web.config denyQueryStringSequences for ctl=register and for register

I have added the dotnetnuke.config blockrequests filter:

        <rule servervar="HTTP_URL" values="(?<=\?)ctl=register|(?<!\?)/register" operator="Regex" action="NotFound" location="" />
But I still get redirected to the new registration page when I request domain.com/register or domain.com/ctl=register

Can anyone think what I'm doing wrong?

 >>>>Edit <<<<

I changed the blockrequests filter to URL in stead of HTTP_URL and now the URL /register is rejected, but the /register.aspx still gets redirected to the custom page.

The custom page is named 'New Account' so register does not appear in the name anywhere.

?????

 
New Post
1/18/2015 8:39 AM
 

I believe that Bruce Chapman is working on an updated article which goes over spam registration in detail.  The specific issue I was talking about earlier is the generation of an error when someone navigates to a non-existent user profile page.  Nothing in 7.3.4 will prevent registration bots, but we have resolved issues with error generation when we should be serving up 404 pages instead.


Joe Brinkman
DNN Corp.
 
New Post
1/20/2015 12:31 AM
 

Thanks Joe

As I said, I am using 7.3.4, but those errors are still clogging up my error log.

I have tried putting the rawurl or parts thereof in the DNN site filters and in the denysequencestring section of web.config.

E.G. - General exception

(note: I have deleted user 5066)

 

AssemblyVersion:7.3.4

PortalID:10

PortalName:Martinborough Fair

UserID:-1

UserName:

ActiveTabID:324

ActiveTabName:User Profile

RawURL:/User-Profile/userId/5066

AbsoluteURL:/Default.aspx

AbsoluteURLReferrer:

UserAgent:Mozilla/5.0 (Windows NT 6.3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36

DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID:e36b9622-4d67-41ad-b143-62c9141c34a3

InnerException:Not Found

FileName:

FileLineNumber:0

FileColumnNumber:0

Method:DotNetNuke.Modules.Admin.Users.ViewProfile.OnInit

StackTrace:

Message:

System.Web.HttpException (0x80004005): Not Found
   at DotNetNuke.Modules.Admin.Users.ViewProfile.OnInit(EventArgs e)
   at System.Web.UI.Control.InitRecursive(Control namingContainer)
   at System.Web.UI.Control.AddedControl(Control control, Int32 index)
   at DotNetNuke.UI.Modules.ModuleHost.InjectModuleContent(Control content)
   at System.Web.UI.Control.EnsureChildControls()
   at DotNetNuke.UI.Containers.Container.get_ModuleControl()
   at DotNetNuke.UI.Containers.Container.ProcessModule()
   at DotNetNuke.UI.Skins.Pane.InjectModule(ModuleInfo module)

Source:

Server Name: micro143

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Thwarting Registration exploitsThwarting Registration exploits


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