-
Updated
Aug 15, 2021 - Shell
security-scanner
Here are 303 public repositories matching this topic...
-
Updated
Aug 15, 2021 - Go
-
Updated
Aug 13, 2021 - Ruby
-
Updated
Jul 29, 2021 - C#
Describe the bug
In the docs found here:
https://bandit.readthedocs.io/en/latest/plugins/index.html#complete-test-plugin-listing
B109 and B111 show a description instead of a plugin name. This looks inconsistent since all the other plugin names are listed. I believe this is a result of a recent change to remove these deprecated plugins.
To Reproduce
- Navigate to https://bandit
This hint has been around since 2018 and is documented on webhint.io (https://webhint.io/docs/user-guide/hints/hint-doctype/). However it's not enabled by default in any of webhint's configurations (likely an oversight).
We should turn this on by default and perform any necessary cleanup in the process (e.g. switching to get locations from webhint's location-aware DOM that was added after the
-
Updated
Jun 30, 2021 - Python
-
Updated
Jul 15, 2021 - C#
-
Updated
Aug 7, 2020
-
Updated
Aug 7, 2021
-
Updated
Jul 4, 2021 - Python
-
Updated
Jun 13, 2021 - Lua
-
Updated
Jul 28, 2021 - CSS
-
Updated
Jul 6, 2020 - Python
-
Updated
May 27, 2021 - Python
-
Updated
Aug 5, 2021 - Go
-
Updated
Jan 15, 2021 - C++
-
Updated
Aug 13, 2021 - Ruby
-
Updated
Aug 19, 2020
-
Updated
Aug 5, 2021 - Python
-
Updated
Feb 3, 2020 - Python
-
Updated
Apr 26, 2020 - Python
-
Updated
Jul 31, 2021 - Perl
-
Updated
Aug 1, 2021 - Rust
-
Updated
Nov 20, 2020
-
Updated
Jul 31, 2021 - Python
-
Updated
Feb 23, 2021 - Go
-
Updated
Jun 13, 2021 - Python
-
Updated
May 10, 2021
Improve this page
Add a description, image, and links to the security-scanner topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the security-scanner topic, visit your repo's landing page and select "manage topics."
Hi,
I am getting some XSS Reflected and persistent alerts generated when a .xls or .pdf file contains unsantised XSS injection strings. I do not want to add an alert filter because it is an .asp page that generates these files and so there could be another XSS vulnerability on the page.
I was wondering if the XSS rule could check the Content-Type header and the file identifying line (first