Skip to content

ascanrules: Tidy up External Redirect Scan Rule #6458

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jul 29, 2025
Merged

ascanrules: Tidy up External Redirect Scan Rule #6458

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion addOns/ascanrules/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,8 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
- SQL Injection - SQLite
- SQL Injection - PostgreSQL
- The Remote OS Command Injection scan rule has been broken into two rules; one feedback based, and one time based (Issue 7341). This includes assigning the time based rule ID 90037.
- The External Redirect scan rule payload were slightly re-ordered to prioritize HTTPS variants.
- For Alerts raised by the SQL Injection scan rules the Attack field values are now simply the payload, not an assembled description.
- Maintenance changes.
Copy link
Member Author

@kingthorin kingthorin Jul 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's at the top of the list.


### Added
- Rules (as applicable) have been tagged in relation to HIPAA and PCI DSS.
Expand Down
Loading