Crash Test - analyse passive du laboratoire local
Crash Test - analyse passive du laboratoire local
| Risk Level | Number of Alerts |
|---|---|
|
High
|
0
|
|
Medium
|
2
|
|
Low
|
3
|
|
Informational
|
1
|
|
False Positives:
|
0
|
| Level | Reason | Site | Description | Statistic |
|---|---|---|---|---|
|
Low
|
Warning
|
ZAP errors logged - see the zap.log file for details
|
2
|
|
|
Low
|
Warning
|
ZAP warnings logged - see the zap.log file for details
|
2
|
|
|
Info
|
Informational
|
http://127.0.0.1:8080
|
Percentage of responses with status code 2xx
|
100 %
|
|
Info
|
Informational
|
http://127.0.0.1:8080
|
Percentage of endpoints with content type text/html
|
75 %
|
|
Info
|
Informational
|
http://127.0.0.1:8080
|
Percentage of endpoints with content type text/plain
|
25 %
|
|
Info
|
Informational
|
http://127.0.0.1:8080
|
Percentage of endpoints with method GET
|
100 %
|
|
Info
|
Informational
|
http://127.0.0.1:8080
|
Count of total endpoints
|
4
|
For each step: result (Pass/Fail) - risk (of highest alert(s) for the step, if any).
| Name | Risk Level | Number of Instances |
|---|---|---|
| Content Security Policy (CSP) Header Not Set | Medium | 3 |
| Missing Anti-clickjacking Header | Medium | 3 |
| Cookie No HttpOnly Flag | Low | 3 |
| Cookie without SameSite Attribute | Low | 3 |
| X-Content-Type-Options Header Missing | Low | 4 |
| Session Management Response Identified | Informational | 3 |
|
Medium |
Content Security Policy (CSP) Header Not Set |
|---|---|
| Description |
Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.
|
| URL | http://127.0.0.1:8080/ |
| Node Name | http://127.0.0.1:8080/ |
| Method | GET |
| Parameter | |
| Attack | |
| Evidence | |
| Other Info | |
| URL | http://127.0.0.1:8080/about |
| Node Name | http://127.0.0.1:8080/about |
| Method | GET |
| Parameter | |
| Attack | |
| Evidence | |
| Other Info | |
| URL | http://127.0.0.1:8080/search?q=bonjour |
| Node Name | http://127.0.0.1:8080/search (q) |
| Method | GET |
| Parameter | |
| Attack | |
| Evidence | |
| Other Info | |
| Instances | 3 |
| Solution |
Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.
|
| Reference |
https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP
https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html https://www.w3.org/TR/CSP/ https://w3c.github.io/webappsec-csp/ https://web.dev/articles/csp https://caniuse.com/#feat=contentsecuritypolicy https://content-security-policy.com/ |
| CWE Id | 693 |
| WASC Id | 15 |
| Plugin Id | 10038 |
|
Medium |
Missing Anti-clickjacking Header |
|---|---|
| Description |
The response does not protect against 'ClickJacking' attacks. It should include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options.
|
| URL | http://127.0.0.1:8080/ |
| Node Name | http://127.0.0.1:8080/ |
| Method | GET |
| Parameter | x-frame-options |
| Attack | |
| Evidence | |
| Other Info | |
| URL | http://127.0.0.1:8080/about |
| Node Name | http://127.0.0.1:8080/about |
| Method | GET |
| Parameter | x-frame-options |
| Attack | |
| Evidence | |
| Other Info | |
| URL | http://127.0.0.1:8080/search?q=bonjour |
| Node Name | http://127.0.0.1:8080/search (q) |
| Method | GET |
| Parameter | x-frame-options |
| Attack | |
| Evidence | |
| Other Info | |
| Instances | 3 |
| Solution |
Modern Web browsers support the Content-Security-Policy and X-Frame-Options HTTP headers. Ensure one of them is set on all web pages returned by your site/app.
If you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. Alternatively consider implementing Content Security Policy's "frame-ancestors" directive.
|
| Reference | https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options |
| CWE Id | 1021 |
| WASC Id | 15 |
| Plugin Id | 10020 |
|
Low |
Cookie No HttpOnly Flag |
|---|---|
| Description |
A cookie has been set without the HttpOnly flag, which means that the cookie can be accessed by JavaScript. If a malicious script can be run on this page then the cookie will be accessible and can be transmitted to another site. If this is a session cookie then session hijacking may be possible.
|
| URL | http://127.0.0.1:8080/ |
| Node Name | http://127.0.0.1:8080/ |
| Method | GET |
| Parameter | lab_demo |
| Attack | |
| Evidence | Set-Cookie: lab_demo |
| Other Info | |
| URL | http://127.0.0.1:8080/about |
| Node Name | http://127.0.0.1:8080/about |
| Method | GET |
| Parameter | lab_demo |
| Attack | |
| Evidence | Set-Cookie: lab_demo |
| Other Info | |
| URL | http://127.0.0.1:8080/search?q=bonjour |
| Node Name | http://127.0.0.1:8080/search (q) |
| Method | GET |
| Parameter | lab_demo |
| Attack | |
| Evidence | Set-Cookie: lab_demo |
| Other Info | |
| Instances | 3 |
| Solution |
Ensure that the HttpOnly flag is set for all cookies.
|
| Reference | https://owasp.org/www-community/HttpOnly |
| CWE Id | 1004 |
| WASC Id | 13 |
| Plugin Id | 10010 |
|
Low |
Cookie without SameSite Attribute |
|---|---|
| Description |
A cookie has been set without the SameSite attribute, which means that the cookie can be sent as a result of a 'cross-site' request. The SameSite attribute is an effective counter measure to cross-site request forgery, cross-site script inclusion, and timing attacks.
|
| URL | http://127.0.0.1:8080/ |
| Node Name | http://127.0.0.1:8080/ |
| Method | GET |
| Parameter | lab_demo |
| Attack | |
| Evidence | Set-Cookie: lab_demo |
| Other Info | |
| URL | http://127.0.0.1:8080/about |
| Node Name | http://127.0.0.1:8080/about |
| Method | GET |
| Parameter | lab_demo |
| Attack | |
| Evidence | Set-Cookie: lab_demo |
| Other Info | |
| URL | http://127.0.0.1:8080/search?q=bonjour |
| Node Name | http://127.0.0.1:8080/search (q) |
| Method | GET |
| Parameter | lab_demo |
| Attack | |
| Evidence | Set-Cookie: lab_demo |
| Other Info | |
| Instances | 3 |
| Solution |
Ensure that the SameSite attribute is set to either 'lax' or ideally 'strict' for all cookies.
|
| Reference | https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-same-site |
| CWE Id | 1275 |
| WASC Id | 13 |
| Plugin Id | 10054 |
|
Low |
X-Content-Type-Options Header Missing |
|---|---|
| Description |
The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.
|
| URL | http://127.0.0.1:8080/ |
| Node Name | http://127.0.0.1:8080/ |
| Method | GET |
| Parameter | x-content-type-options |
| Attack | |
| Evidence | |
| Other Info | This issue still applies to error type pages (401, 403, 500, etc.) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type. At "High" threshold this scan rule will not alert on client or server error responses. |
| URL | http://127.0.0.1:8080/about |
| Node Name | http://127.0.0.1:8080/about |
| Method | GET |
| Parameter | x-content-type-options |
| Attack | |
| Evidence | |
| Other Info | This issue still applies to error type pages (401, 403, 500, etc.) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type. At "High" threshold this scan rule will not alert on client or server error responses. |
| URL | http://127.0.0.1:8080/robots.txt |
| Node Name | http://127.0.0.1:8080/robots.txt |
| Method | GET |
| Parameter | x-content-type-options |
| Attack | |
| Evidence | |
| Other Info | This issue still applies to error type pages (401, 403, 500, etc.) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type. At "High" threshold this scan rule will not alert on client or server error responses. |
| URL | http://127.0.0.1:8080/search?q=bonjour |
| Node Name | http://127.0.0.1:8080/search (q) |
| Method | GET |
| Parameter | x-content-type-options |
| Attack | |
| Evidence | |
| Other Info | This issue still applies to error type pages (401, 403, 500, etc.) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type. At "High" threshold this scan rule will not alert on client or server error responses. |
| Instances | 4 |
| Solution |
Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.
If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.
|
| Reference |
https://learn.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/compatibility/gg622941(v=vs.85)
https://owasp.org/www-community/Security_Headers |
| CWE Id | 693 |
| WASC Id | 15 |
| Plugin Id | 10021 |
|
Informational |
Session Management Response Identified |
|---|---|
| Description |
The given response has been identified as containing a session management token. The 'Other Info' field contains a set of header tokens that can be used in the Header Based Session Management Method. If the request is in a context which has a Session Management Method set to "Auto-Detect" then this rule will change the session management to use the tokens identified.
|
| URL | http://127.0.0.1:8080/ |
| Node Name | http://127.0.0.1:8080/ |
| Method | GET |
| Parameter | lab_demo |
| Attack | |
| Evidence | lab_demo |
| Other Info | cookie:lab_demo |
| URL | http://127.0.0.1:8080/about |
| Node Name | http://127.0.0.1:8080/about |
| Method | GET |
| Parameter | lab_demo |
| Attack | |
| Evidence | lab_demo |
| Other Info | cookie:lab_demo |
| URL | http://127.0.0.1:8080/search?q=bonjour |
| Node Name | http://127.0.0.1:8080/search (q) |
| Method | GET |
| Parameter | lab_demo |
| Attack | |
| Evidence | lab_demo |
| Other Info | cookie:lab_demo |
| Instances | 3 |
| Solution |
This is an informational alert rather than a vulnerability and so there is nothing to fix.
|
| Reference | https://www.zaproxy.org/docs/desktop/addons/authentication-helper/session-mgmt-id/ |
| CWE Id | |
| WASC Id | |
| Plugin Id | 10112 |