ZAP Scanning Report
ZAP Scanning Report
| Risk Level | Number of Alerts |
|---|---|
|
High
|
0
|
|
Medium
|
0
|
|
Low
|
0
|
|
Informational
|
1
|
|
False Positives:
|
0
|
| Level | Reason | Site | Description | Statistic |
|---|---|---|---|---|
|
Info
|
Informational
|
http://host.docker.internal:5173
|
Percentage of responses with status code 4xx
|
100 %
|
|
Info
|
Informational
|
http://host.docker.internal:5173
|
Percentage of endpoints with content type text/plain
|
100 %
|
|
Info
|
Informational
|
http://host.docker.internal:5173
|
Percentage of endpoints with method GET
|
100 %
|
|
Info
|
Informational
|
http://host.docker.internal:5173
|
Count of total endpoints
|
2
|
For each step: result (Pass/Fail) - risk (of highest alert(s) for the step, if any).
| Name | Risk Level | Number of Instances |
|---|---|---|
| Non-Storable Content | Informational | 3 |
|
Informational |
Non-Storable Content |
|---|---|
| Description |
The response contents are not storable by caching components such as proxy servers. If the response does not contain sensitive, personal or user-specific information, it may benefit from being stored and cached, to improve performance.
|
| URL | http://host.docker.internal:5173 |
| Node Name | http://host.docker.internal:5173 |
| Method | GET |
| Parameter | |
| Attack | |
| Evidence | 403 |
| Other Info | |
| URL | http://host.docker.internal:5173/robots.txt |
| Node Name | http://host.docker.internal:5173/robots.txt |
| Method | GET |
| Parameter | |
| Attack | |
| Evidence | 403 |
| Other Info | |
| URL | http://host.docker.internal:5173/sitemap.xml |
| Node Name | http://host.docker.internal:5173/sitemap.xml |
| Method | GET |
| Parameter | |
| Attack | |
| Evidence | 403 |
| Other Info | |
| Instances | 3 |
| Solution |
The content may be marked as storable by ensuring that the following conditions are satisfied:
The request method must be understood by the cache and defined as being cacheable ("GET", "HEAD", and "POST" are currently defined as cacheable)
The response status code must be understood by the cache (one of the 1XX, 2XX, 3XX, 4XX, or 5XX response classes are generally understood)
The "no-store" cache directive must not appear in the request or response header fields
For caching by "shared" caches such as "proxy" caches, the "private" response directive must not appear in the response
For caching by "shared" caches such as "proxy" caches, the "Authorization" header field must not appear in the request, unless the response explicitly allows it (using one of the "must-revalidate", "public", or "s-maxage" Cache-Control response directives)
In addition to the conditions above, at least one of the following conditions must also be satisfied by the response:
It must contain an "Expires" header field
It must contain a "max-age" response directive
For "shared" caches such as "proxy" caches, it must contain a "s-maxage" response directive
It must contain a "Cache Control Extension" that allows it to be cached
It must have a status code that is defined as cacheable by default (200, 203, 204, 206, 300, 301, 404, 405, 410, 414, 501).
|
| Reference |
https://datatracker.ietf.org/doc/html/rfc7234
https://datatracker.ietf.org/doc/html/rfc7231 https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html |
| CWE Id | 524 |
| WASC Id | 13 |
| Plugin Id | 10049 |