Files
zot/.zap/rules.tsv
T
Andrei Aaron 46ee330b2a feat(zui): update to zui supporting social login (#1639)
Also ignore issues related to https://developer.mozilla.org/en-US/docs/Glossary/Fetch_metadata_request_header
It is not clear what the zap tool expectations are from the zot server, as these headers are supposed to be set by the zot client.

As a separate not ZUI sets these headers, but for some reason the scan expects them when scanning zot minimal without the UI

Signed-off-by: Andrei Aaron <aaaron@luxoft.com>
2023-07-21 12:50:41 -07:00

3.5 KiB

1# zap-baseline rule configuration file
2# Change WARN to IGNORE to ignore rule or FAIL to fail if rule matches
3# Only the rule identifiers are used - the names are just for info
4# You can add your own messages to each rule by appending them after a tab on each line.
510003WARN(Vulnerable JS Library (Powered by Retire.js))
610009WARN(In Page Banner Information Leak)
710010WARN(Cookie No HttpOnly Flag)
810011WARN(Cookie Without Secure Flag)
910015WARN(Re-examine Cache-control Directives)
1010017WARN(Cross-Domain JavaScript Source File Inclusion)
1110019WARN(Content-Type Header Missing)
1210020WARN(Anti-clickjacking Header)
1310021WARN(X-Content-Type-Options Header Missing)
1410023WARN(Information Disclosure - Debug Error Messages)
1510024WARN(Information Disclosure - Sensitive Information in URL)
1610025WARN(Information Disclosure - Sensitive Information in HTTP Referrer Header)
1710026WARN(HTTP Parameter Override)
1810027IGNORE(Information Disclosure - Suspicious Comments) The comments have been reviewed and will not help an attacker
1910028WARN(Open Redirect)
2010029WARN(Cookie Poisoning)
2110030WARN(User Controllable Charset)
2210031WARN(User Controllable HTML Element Attribute (Potential XSS))
2310032WARN(Viewstate)
2410033WARN(Directory Browsing)
2510034WARN(Heartbleed OpenSSL Vulnerability (Indicative))
2610035WARN(Strict-Transport-Security Header)
2710036WARN(HTTP Server Response Header)
2810038WARN(Content Security Policy (CSP) Header Not Set)
2910039WARN(X-Backend-Server Header Information Leak)
3010040WARN(Secure Pages Include Mixed Content)
3110041WARN(HTTP to HTTPS Insecure Transition in Form Post)
3210042WARN(HTTPS to HTTP Insecure Transition in Form Post)
3310043WARN(User Controllable JavaScript Event (XSS))
3410044WARN(Big Redirect Detected (Potential Sensitive Information Leak))
3510049IGNORE(Content Cacheability) We'd need to set the non-cacheble headers on content which could potentially be cached
3610050WARN(Retrieved from Cache)
3710052WARN(X-ChromeLogger-Data (XCOLD) Header Information Leak)
3810054WARN(Cookie without SameSite Attribute)
3910055IGNORE(CSP) We set CSP in both UI (with *) and backend (no *), unfortunately the UI needs to use * in case it is deployed separately
4010056WARN(X-Debug-Token Information Leak)
4110057WARN(Username Hash Found)
4210061WARN(X-AspNet-Version Response Header)
4310062WARN(PII Disclosure)
4410063WARN(Permissions Policy Header Not Set)
4510096IGNORE(Timestamp Disclosure) All existing timestamps are related to container images and are required
4610097WARN(Hash Disclosure)
4710098IGNORE(Cross-Domain Misconfiguration) Cannot know in advance what DN the users will configure for CORS headers
4810105IGNORE(Weak Authentication Method) Cannot package in advance a certificate which would be used for the user's domain, so we cannot use HTTPS
4910108WARN(Reverse Tabnabbing)
5010109IGNORE(Modern Web Application) The Ajax crawler is run using -j command line option
5110110WARN(Dangerous JS Functions)
5210202WARN(Absence of Anti-CSRF Tokens)
532WARN(Private IP Disclosure)
543WARN(Session ID in URL Rewrite)
5550001WARN(Script Passive Scan Rules)
5690001WARN(Insecure JSF ViewState)
5790002WARN(Java Serialization Object)
5890003WARN(Sub Resource Integrity Attribute Missing)
5990005IGNORE(Sec-Fetch-Dest Header is Missing)
6090011WARN(Charset Mismatch)
6190022WARN(Application Error Disclosure)
6290030WARN(WSDL File Detection)
6390033WARN(Loosely Scoped Cookie)