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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Portal Security: Problem with NOSQL And NOSCRIPTINGPortal Security: Problem with NOSQL And NOSCRIPTING
Previous
 
Next
New Post
7/14/2009 5:48 AM
 

Hello everybody,

I am working on DNN for our new project for the past 1 year. The DNN portal security has been applied to the Input textboxes(refernece: http://www.dotnetnuke.com/LinkClick.aspx?fileticket=QEzF0hGvrr4%3D&tabid=478&mid=857). Here is how the same is getting applied:



filteredText = portalSecurity.InputFilter(inputText,PortalSecurity.FilterFlag.NoScripting |PortalSecurity.FilterFlag.NoMarkup |PortalSecurity.FilterFlag.NoAngleBrackets |PortalSecurity.FilterFlag.NoSQL);

Here i have some questions :

1. NOSQl: This is working cool, but it is somehow not meeting our requirements: i) if i want to name a process step as "Create New Process", it strips off the CREATE word(since it is a SQL keyword), but not somehow considerable. Not only this, if i write something like "Creating New Process", it ends up being "ing New Process" which is definitely not considerable. Can you please help me out of this. I am in real trouble.Please suggest some alternative to handle SQL Injection.

2. NOSCRIPTING: This is somehow alllowing the <script> to go through as is, do i need to change something in web.config or similar places.

Please help me out. Thanks in Advance.

 
New Post
7/15/2009 10:35 AM
 

Hello,

please note that the filterflags are not all designed to work together e.g. it does not make sense to use the sql injection ones with the ones intended for output. In general

  •  If you're using dynamic sql (i.e. concatenating sql strings together) then you make use of NoSQL
  •  If however, you are accepting user input and planning on writing it to the screen/database then you have to decide what level of html you support.
    •  If you do not plan on supporting html at all (e.g. if you're reading from a textbox which contains a users name, there is no need to support html), then use NoMarkup (as it will encode the content).
    • If however you need to support html in user input (e.g. if you're allowing html in a forum post etc.), then you use NoScripting to strip dangerous cross-site scripting javascript.
  • you do not need to use the NoAngleBrackets filter - it was added as a request for a major military dotnetnuke user to pass a flawed security audit - it does not add any additional security benefits

If you feel that there is an issue in the filtering code, please email your code and text to security@dotnetnuke.com so we can evaluate it.

Cathal

 

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Portal Security: Problem with NOSQL And NOSCRIPTINGPortal Security: Problem with NOSQL And NOSCRIPTING


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