ZAP Scanning Report

Site: http://host.docker.internal:16310

Generated on Sat, 14 Nov 2026 02:24:02

ZAP Version: 2.17.0

ZAP by Checkmarx

Summary of Alerts

Risk Level Number of Alerts
High
0
Medium
2
Low
5
Informational
4
False Positives:
0

Insights

Level Reason Site Description Statistic
Info
Informational
http://host.docker.internal:16310
Percentage of responses with status code 2xx
33 %
Info
Informational
http://host.docker.internal:16310
Percentage of responses with status code 3xx
11 %
Info
Informational
http://host.docker.internal:16310
Percentage of responses with status code 4xx
55 %
Info
Informational
http://host.docker.internal:16310
Percentage of endpoints with content type application/problem+json
57 %
Info
Informational
http://host.docker.internal:16310
Percentage of endpoints with content type text/html
28 %
Info
Informational
http://host.docker.internal:16310
Percentage of endpoints with method GET
85 %
Info
Informational
http://host.docker.internal:16310
Percentage of endpoints with method POST
14 %
Info
Informational
http://host.docker.internal:16310
Count of total endpoints
7
Info
Informational
http://host.docker.internal:16310
Percentage of slow responses
11 %

Summary of Sequences

For each step: result (Pass/Fail) - risk (of highest alert(s) for the step, if any).

Alerts

Name Risk Level Number of Instances
Content Security Policy (CSP) Header Not Set Medium 2
Missing Anti-clickjacking Header Medium 1
Cross-Origin-Embedder-Policy Header Missing or Invalid Low 2
Cross-Origin-Opener-Policy Header Missing or Invalid Low 2
Cross-Origin-Resource-Policy Header Missing or Invalid Low 2
Permissions Policy Header Not Set Low 2
X-Content-Type-Options Header Missing Low 2
Authentication Request Identified Informational 1
Non-Storable Content Informational 3
Session Management Response Identified Informational 2
Storable and Cacheable Content Informational 4

Alert Detail

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://host.docker.internal:16310/staff/login
Node Name http://host.docker.internal:16310/staff/login
Method GET
Parameter
Attack
Evidence
Other Info
URL http://host.docker.internal:16310/staff/login?error=1
Node Name http://host.docker.internal:16310/staff/login (error)
Method GET
Parameter
Attack
Evidence
Other Info
Instances 2
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://host.docker.internal:16310/staff/login?error=1
Node Name http://host.docker.internal:16310/staff/login (error)
Method GET
Parameter x-frame-options
Attack
Evidence
Other Info
Instances 1
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
Cross-Origin-Embedder-Policy Header Missing or Invalid
Description
Cross-Origin-Embedder-Policy header is a response header that prevents a document from loading any cross-origin resources that don't explicitly grant the document permission (using CORP or CORS).
URL http://host.docker.internal:16310/staff/login
Node Name http://host.docker.internal:16310/staff/login
Method GET
Parameter Cross-Origin-Embedder-Policy
Attack
Evidence
Other Info
URL http://host.docker.internal:16310/staff/login?error=1
Node Name http://host.docker.internal:16310/staff/login (error)
Method GET
Parameter Cross-Origin-Embedder-Policy
Attack
Evidence
Other Info
Instances 2
Solution
Ensure that the application/web server sets the Cross-Origin-Embedder-Policy header appropriately, and that it sets the Cross-Origin-Embedder-Policy header to 'require-corp' for documents.

If possible, ensure that the end user uses a standards-compliant and modern web browser that supports the Cross-Origin-Embedder-Policy header (https://caniuse.com/mdn-http_headers_cross-origin-embedder-policy).
Reference https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cross-Origin-Embedder-Policy
CWE Id 693
WASC Id 14
Plugin Id 90004
Low
Cross-Origin-Opener-Policy Header Missing or Invalid
Description
Cross-Origin-Opener-Policy header is a response header that allows a site to control if others included documents share the same browsing context. Sharing the same browsing context with untrusted documents might lead to data leak.
URL http://host.docker.internal:16310/staff/login
Node Name http://host.docker.internal:16310/staff/login
Method GET
Parameter Cross-Origin-Opener-Policy
Attack
Evidence
Other Info
URL http://host.docker.internal:16310/staff/login?error=1
Node Name http://host.docker.internal:16310/staff/login (error)
Method GET
Parameter Cross-Origin-Opener-Policy
Attack
Evidence
Other Info
Instances 2
Solution
Ensure that the application/web server sets the Cross-Origin-Opener-Policy header appropriately, and that it sets the Cross-Origin-Opener-Policy header to 'same-origin' for documents.

'same-origin-allow-popups' is considered as less secured and should be avoided.

If possible, ensure that the end user uses a standards-compliant and modern web browser that supports the Cross-Origin-Opener-Policy header (https://caniuse.com/mdn-http_headers_cross-origin-opener-policy).
Reference https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cross-Origin-Opener-Policy
CWE Id 693
WASC Id 14
Plugin Id 90004
Low
Cross-Origin-Resource-Policy Header Missing or Invalid
Description
Cross-Origin-Resource-Policy header is an opt-in header designed to counter side-channels attacks like Spectre. Resource should be specifically set as shareable amongst different origins.
URL http://host.docker.internal:16310/staff/login
Node Name http://host.docker.internal:16310/staff/login
Method GET
Parameter Cross-Origin-Resource-Policy
Attack
Evidence
Other Info
URL http://host.docker.internal:16310/staff/login?error=1
Node Name http://host.docker.internal:16310/staff/login (error)
Method GET
Parameter Cross-Origin-Resource-Policy
Attack
Evidence
Other Info
Instances 2
Solution
Ensure that the application/web server sets the Cross-Origin-Resource-Policy header appropriately, and that it sets the Cross-Origin-Resource-Policy header to 'same-origin' for all web pages.

'same-site' is considered as less secured and should be avoided.

If resources must be shared, set the header to 'cross-origin'.

If possible, ensure that the end user uses a standards-compliant and modern web browser that supports the Cross-Origin-Resource-Policy header (https://caniuse.com/mdn-http_headers_cross-origin-resource-policy).
Reference https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cross-Origin-Embedder-Policy
CWE Id 693
WASC Id 14
Plugin Id 90004
Low
Permissions Policy Header Not Set
Description
Permissions Policy Header is an added layer of security that helps to restrict from unauthorized access or usage of browser/client features by web resources. This policy ensures the user privacy by limiting or specifying the features of the browsers can be used by the web resources. Permissions Policy provides a set of standard HTTP headers that allow website owners to limit which features of browsers can be used by the page such as camera, microphone, location, full screen etc.
URL http://host.docker.internal:16310/staff/login
Node Name http://host.docker.internal:16310/staff/login
Method GET
Parameter
Attack
Evidence
Other Info
URL http://host.docker.internal:16310/staff/login?error=1
Node Name http://host.docker.internal:16310/staff/login (error)
Method GET
Parameter
Attack
Evidence
Other Info
Instances 2
Solution
Ensure that your web server, application server, load balancer, etc. is configured to set the Permissions-Policy header.
Reference https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy
https://developer.chrome.com/blog/feature-policy/
https://scotthelme.co.uk/a-new-security-header-feature-policy/
https://w3c.github.io/webappsec-feature-policy/
https://www.smashingmagazine.com/2018/12/feature-policy/
CWE Id 693
WASC Id 15
Plugin Id 10063
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://host.docker.internal:16310/staff/login
Node Name http://host.docker.internal:16310/staff/login
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://host.docker.internal:16310/staff/login?error=1
Node Name http://host.docker.internal:16310/staff/login (error)
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 2
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
Authentication Request Identified
Description
The given request has been identified as an authentication request. The 'Other Info' field contains a set of key=value lines which identify any relevant fields. If the request is in a context which has an Authentication Method set to "Auto-Detect" then this rule will change the authentication to match the request identified.
URL http://host.docker.internal:16310/staff/signin
Node Name http://host.docker.internal:16310/staff/signin ()(__RequestVerificationToken,email,password,returnUrl)
Method POST
Parameter email
Attack
Evidence password
Other Info
userParam=email

userValue=zaproxy@

passwordParam=password

referer=http://host.docker.internal:16310/staff/login

csrfToken=__RequestVerificationToken
Instances 1
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/auth-req-id/
CWE Id
WASC Id
Plugin Id 10111
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:16310/staff/login
Node Name http://host.docker.internal:16310/staff/login
Method GET
Parameter
Attack
Evidence no-store
Other Info
URL http://host.docker.internal:16310/staff/login?error=1
Node Name http://host.docker.internal:16310/staff/login (error)
Method GET
Parameter
Attack
Evidence no-store
Other Info
URL http://host.docker.internal:16310/staff/signin
Node Name http://host.docker.internal:16310/staff/signin ()(__RequestVerificationToken,email,password,returnUrl)
Method POST
Parameter
Attack
Evidence 302
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
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://host.docker.internal:16310/staff/login
Node Name http://host.docker.internal:16310/staff/login
Method GET
Parameter .AspNetCore.Antiforgery.1rtHG0sNqZA
Attack
Evidence .AspNetCore.Antiforgery.1rtHG0sNqZA
Other Info
cookie:.AspNetCore.Antiforgery.1rtHG0sNqZA
URL http://host.docker.internal:16310/staff/login
Node Name http://host.docker.internal:16310/staff/login
Method GET
Parameter .AspNetCore.Antiforgery.1rtHG0sNqZA
Attack
Evidence .AspNetCore.Antiforgery.1rtHG0sNqZA
Other Info
cookie:.AspNetCore.Antiforgery.1rtHG0sNqZA
Instances 2
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
Informational
Storable and Cacheable Content
Description
The response contents are storable by caching components such as proxy servers, and may be retrieved directly from the cache, rather than from the origin server by the caching servers, in response to similar requests from other users. If the response data is sensitive, personal or user-specific, this may result in sensitive information being leaked. In some cases, this may even result in a user gaining complete control of the session of another user, depending on the configuration of the caching components in use in their environment. This is primarily an issue where "shared" caching servers such as "proxy" caches are configured on the local network. This configuration is typically found in corporate or educational environments, for instance.
URL http://host.docker.internal:16310/
Node Name http://host.docker.internal:16310/
Method GET
Parameter
Attack
Evidence
Other Info
In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234.
URL http://host.docker.internal:16310/robots.txt
Node Name http://host.docker.internal:16310/robots.txt
Method GET
Parameter
Attack
Evidence
Other Info
In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234.
URL http://host.docker.internal:16310/sitemap.xml
Node Name http://host.docker.internal:16310/sitemap.xml
Method GET
Parameter
Attack
Evidence
Other Info
In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234.
URL http://host.docker.internal:16310/staff
Node Name http://host.docker.internal:16310/staff
Method GET
Parameter
Attack
Evidence
Other Info
In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234.
Instances 4
Solution
Validate that the response does not contain sensitive, personal or user-specific information. If it does, consider the use of the following HTTP response headers, to limit, or prevent the content being stored and retrieved from the cache by another user:

Cache-Control: no-cache, no-store, must-revalidate, private

Pragma: no-cache

Expires: 0

This configuration directs both HTTP 1.0 and HTTP 1.1 compliant caching servers to not store the response, and to not retrieve the response (without validation) from the cache, in response to a similar request.
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

Sequence Details

With the associated active scan results.