-
-
Notifications
You must be signed in to change notification settings - Fork 762
pscanrules: Update CSPMissing for current guidance (Issue 7653) #4338
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
Conversation
kingthorin
left a comment
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.
I still need to look at the tests but here’s a quick first pass.
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
|
To address the DCO requirement you'll need to sign-off the commit(s): |
...c/main/javahelp/org/zaproxy/zap/extension/pscanrules/resources/help/contents/pscanrules.html
Outdated
Show resolved
Hide resolved
d5dfffa to
9f66f4a
Compare
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
.../java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRuleUnitTest.java
Show resolved
Hide resolved
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
|
The branch needs to be updated and the changelog moved to the Unreleased version. |
...c/main/javahelp/org/zaproxy/zap/extension/pscanrules/resources/help/contents/pscanrules.html
Outdated
Show resolved
Hide resolved
|
Couple of process questions, because I'm new on this project.
|
|
All the workflows completed successfully. The only remaining step is for a second approving review :) So for now it's kinda on us. |
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
...nrules/src/main/resources/org/zaproxy/zap/extension/pscanrules/resources/Messages.properties
Outdated
Show resolved
Hide resolved
kingthorin
left a comment
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
|
The scan rule doesnt return any examples. Edit: Reference 👉 zaproxy/zaproxy#6119 |
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Show resolved
Hide resolved
|
Needs to be rebased to properly update the changelog. |
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
|
You seem to have merged, not rebased. |
apparently so; I'll figure out how to get this reset and resubmit. |
|
We are happy to help. |
305c619 to
0530c81
Compare
Implementations that followed current guidance with respect to which headers to use would see alerts raised at Low threshold. Now, the alerts reflect the current guidance (ie, don't use the obsolete CSP headers). Signed-off-by: David Hall <[email protected]>
Signed-off-by: David Hall <[email protected]>
Signed-off-by: David Hall <[email protected]>
Signed-off-by: David Hall <[email protected]>
- Obsolete CSP header usage is always flagged, not just at LOW - General refactoring suggested by reviewers Signed-off-by: David Hall <[email protected]>
Signed-off-by: David Hall <[email protected]>
Signed-off-by: David Hall <[email protected]>
Signed-off-by: David Hall <[email protected]>
Signed-off-by: David Hall <[email protected]>
Signed-off-by: David Hall <[email protected]>
|
in my day job, we don't really use forks, so that is new to me. I've found that the best way to learn more about git is to git yourself outta trouble. Hopefully, I didn't hammer it up too badly -- I do see your recent commits in the history on my fork, so there is some reassurance. |
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRule.java
Outdated
Show resolved
Hide resolved
.../java/org/zaproxy/zap/extension/pscanrules/ContentSecurityPolicyMissingScanRuleUnitTest.java
Show resolved
Hide resolved
Signed-off-by: David Hall <[email protected]>
|
Thank you! |
|
Thank you both; this was an interesting experience |
|
@davidahall how would you like to be credited (e.g. name, handle)? |
|
by name, please -- David Hall
On Friday, March 10, 2023 at 01:33:42 PM EST, thc202 ***@***.***> wrote:
@davidahall how would you like to be credited (e.g. name, handle)?
https://www.zaproxy.org/docs/desktop/credits/#zap-extended-team
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
The alerts raised by the Content Security Policy Missing scan rule do not reflect the current guidance in the linked documents. The current guidance is that the X-Content-Security-Policy and X-WebKit-CSP headers are obsolete, and should not be used. However, at Low threshold, absence of these headers results in an alert being raised. I've updated the logic to more accurately reflect the OWASP guidance.
Fix zaproxy/zaproxy#7653.