ZAP Scanning Report

Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks. Including (but not limited to) 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.

The following directives either allow wildcard sources (or ancestors), are not defined, or are overly broadly defined:

connect-src

The following directives either allow wildcard sources (or ancestors), are not defined, or are overly broadly defined:

connect-src

The following directives either allow wildcard sources (or ancestors), are not defined, or are overly broadly defined:

connect-src

Ensure that your web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.

Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks. Including (but not limited to) 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.

script-src includes unsafe-inline.

script-src includes unsafe-inline.

script-src includes unsafe-inline.

Ensure that your web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.

Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks. Including (but not limited to) 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.

style-src includes unsafe-inline.

style-src includes unsafe-inline.

style-src includes unsafe-inline.

Ensure that your web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.

The server has responded with a redirect that seems to provide a large response. This may indicate that although the server sent a redirect it also responded with body content (which may include sensitive details, PII, etc.).

Location header URI length: 31 [https://helpdesk.mpba.dev/login].

Predicted response size: 331.

Response Body Length: 370.

Location header URI length: 31 [https://helpdesk.mpba.dev/login].

Predicted response size: 331.

Response Body Length: 370.

Location header URI length: 41 [https://helpdesk.mpba.dev/forgot-password].

Predicted response size: 341.

Response Body Length: 410.

Location header URI length: 31 [https://helpdesk.mpba.dev/login].

Predicted response size: 331.

Response Body Length: 370.

Location header URI length: 34 [https://helpdesk.mpba.dev/register].

Predicted response size: 334.

Response Body Length: 382.

Ensure that no sensitive information is leaked via redirect responses. Redirect responses should have almost no content.

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.

Ensure that the HttpOnly flag is set for all cookies.

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.

userParam=email

userValue=zaproxy@example.com

passwordParam=password

referer=https://helpdesk.mpba.dev/login

csrfToken=_token

This is an informational alert rather than a vulnerability and so there is nothing to fix.

The application appears to be a modern web application. If you need to explore it automatically then the Client Spider may well be more effective than the standard one.

Links have been found that do not have traditional href attributes, which is an indication that this is a modern web application.

Links have been found that do not have traditional href attributes, which is an indication that this is a modern web application.

This is an informational alert and so no changes are required.

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.

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).

The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.

For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".

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.

cookie:XSRF-TOKEN

cookie:mpba-helpdesk-session

cookie:XSRF-TOKEN

cookie:mpba-helpdesk-session

cookie:XSRF-TOKEN

cookie:mpba-helpdesk-session

cookie:XSRF-TOKEN

cookie:mpba-helpdesk-session

cookie:XSRF-TOKEN

cookie:mpba-helpdesk-session

cookie:XSRF-TOKEN

cookie:mpba-helpdesk-session

cookie:XSRF-TOKEN

cookie:mpba-helpdesk-session

cookie:XSRF-TOKEN

cookie:mpba-helpdesk-session

This is an informational alert rather than a vulnerability and so there is nothing to fix.

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.

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.