You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The security header content checks currently only check for the existence of the header, which is next to useless. It'd be far better if they actually verified / checked the value/content of the header.
{
:type => "content",
:name => "X-Frame-Options Header",
:match_type => :content_headers,
:dynamic_result => lambda { |d|
return true if _first_header_match d, /^x-frame-options:.*/i;
false
},
:dynamic_hide => lambda { |d| false },
:dynamic_issue => lambda { |d| false },
:paths => ["#{url}"]
},```
but the header could be `X-Frame-Options: kill all humans` ..
in addition, many applications will not respond with a CORS header unless the client request contains an `Origin` header
via @bcoles
The text was updated successfully, but these errors were encountered:
The security header content checks currently only check for the existence of the header, which is next to useless. It'd be far better if they actually verified / checked the value/content of the header.
For example:
and
The text was updated successfully, but these errors were encountered: