Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: A potentially dangerous Request.Path value was detected from the client (:) #6090

Closed
2 tasks done
mannesandeep opened this issue Jul 2, 2024 · 3 comments
Closed
2 tasks done

Comments

@mannesandeep
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

Added an Iframe to the page in HTML Editor, while loading the iframe DotNetNuke is logging the error "A potentially Dangerous Request.Path value was detected from the client.
Tried removing the ":" under requestPathInvalidCharacters. But no luck

Steps to reproduce?

  1. Login as Admin to the website
  2. create a page and add an HTML Editor
  3. Add Iframe code in the Editor and save
  4. While loading the iframe the error is logged in the system.

Current Behavior

No response

Expected Behavior

It should read the iframe Origin url

Relevant log output

2024-07-01 06:43:14, 390 [Thread:43][FATAL] DotNetNuke.Web.Common.Internal.DotNetNukeHttpApplication - System.Web.HttpException (0x80004005) : A potentially dangerous Request.Path value was detected from the client (:).
at system.web.httprequest.ValidateInputIfRequiredByconfig()
at system.web.httpapplication.PipelineStepManager.ValidateHelper (httpcontext context)

Anything else?

No response

Affected Versions

9.13.3 (latest release)

What browsers are you seeing the problem on?

Chrome

Code of Conduct

  • I agree to follow this project's Code of Conduct
@mitchelsellers
Copy link
Contributor

What exact content are you placing? I know many that add frame content in without issue.

Is the error after the content is saved or when trying to save?

@mannesandeep
Copy link
Author

The issue is appearing at the time of iframe loading.

@valadas
Copy link
Contributor

valadas commented Jul 16, 2024

I am sorry but we can't really be of any help unless we are able to make it happen, we need the actual iframe code that can make this fail.

If you can add an example for us to completely be able to reproduce a failing scenario, I'll be happy to re-open this issue.

@valadas valadas closed this as completed Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants