-
-
Notifications
You must be signed in to change notification settings - Fork 724
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
Provide example alerts in Cookie scan rules #2532
Provide example alerts in Cookie scan rules #2532
Conversation
It does, but there's a new way to provide the alert data, more details in zaproxy/zaproxy#6119 (this could be changed to do that if you want). |
To address the DCO requirement you'll need to sign-off the commit(s): |
Also needs a spotlessApply: |
...ns/pscanrules/src/main/java/org/zaproxy/zap/extension/pscanrules/CookieHttpOnlyScanRule.java
Outdated
Show resolved
Hide resolved
Thanks @kingthorin and @thc202 for the hints, sorry saw that too late 🐒 Will update PR asap |
The CWE id was already managed for these Alerts/ScanRules and within ZAP they were already presented to the user. However, when visiting the alert detail pages online (https://www.zaproxy.org/docs/alerts/), CWE (and WASC) links were not generated correctly. The reason is, that the id values were set inline to the alert. For the script which generates the detail pages however, the getter methods for the ids have to be added publicly to the class. Note: if this solves the issue, I'll vote for another follow up issue to add this change to the PluginPassiveScanner parent class, so that the docs will be generated consistently over all Passive Scan Rules. Fixes zaproxy/zaproxy#6140. Signed-off-by: Martin Spielmann <[email protected]>
06e2f7e
to
e8cf83b
Compare
Signed-off-by: Martin Spielmann <[email protected]>
No worries. Every project/contribution is a new adventure 😀 |
Regarding the comment:
After reading through, I think it would indeed be cleaner to go for the new |
I'm fine with it being here. You can always squash this. |
To comply with zaproxy/zaproxy#6140, the affected ScanRules have been provided with a getExampeAlerts method. It allows maintenance scripts to generate documentation pages in a common way. Signed-off-by: Martin Spielmann <[email protected]>
Ok ready :) |
...ns/pscanrules/src/main/java/org/zaproxy/zap/extension/pscanrules/CookieHttpOnlyScanRule.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor thing, and it’s an existing issue
...ns/pscanrules/src/main/java/org/zaproxy/zap/extension/pscanrules/CookieHttpOnlyScanRule.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Martin Spielmann <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Thank you! |
The CWE id was already managed for these Alerts/ScanRules and within ZAP they were already presented to the user.
However, when visiting the alert detail pages online (https://www.zaproxy.org/docs/alerts/), CWE (and WASC) links were not generated correctly.
The reason is, that the id values were set inline to the alert.
For the script which generates the detail pages however, the getter methods for the ids have to be added publicly to the class.
Note: if this solves the issue, I'll vote for another follow up issue to add this change to the PluginPassiveScanner parent class,
so that the docs will be generated consistently over all Passive Scan Rules.
Fixes zaproxy/zaproxy#6140.