Security Assessment Report
Vulnerability findings for the public-facing infrastructure of overwatch.overdrive.co.za
01 Executive overview Severity distribution across 18 findings
02 Top findings Ranked by severity
Highest-impact issues identified during the assessment (non-informational), ordered by severity.
| # | Severity | Finding | Affected | Instances |
|---|---|---|---|---|
| 01 | Medium | Content Security Policy (CSP) Header Not Set | overwatch.overdrive.co.za | 3 |
| 02 | Low | Cookie No HttpOnly Flag | overwatch.overdrive.co.za | 2 |
| 03 | Low | Cookie Without Secure Flag | overwatch.overdrive.co.za | 1 |
| 04 | Low | Cookie with SameSite Attribute None | overwatch.overdrive.co.za | 1 |
| 05 | Low | Cookie without SameSite Attribute | overwatch.overdrive.co.za | 1 |
| 06 | Low | Cross-Origin-Embedder-Policy Header Missing or Invalid | overwatch.overdrive.co.za | 1 |
| 07 | Low | Cross-Origin-Opener-Policy Header Missing or Invalid | overwatch.overdrive.co.za | 1 |
| 08 | Low | Cross-Origin-Resource-Policy Header Missing or Invalid | overwatch.overdrive.co.za | 1 |
| 09 | Low | Permissions Policy Header Not Set | overwatch.overdrive.co.za | 3 |
| 10 | Low | Server Leaks Version Information via "Server" HTTP Response Header Field | overwatch.overdrive.co.za | 3 |
| 11 | Low | Strict-Transport-Security Header Not Set | overwatch.overdrive.co.za | 3 |
| 12 | Informational | Modern Web Application | overwatch.overdrive.co.za | 1 |
| 13 | Informational | Non-Storable Content | overwatch.overdrive.co.za | 3 |
| 14 | Informational | Re-examine Cache-control Directives | overwatch.overdrive.co.za | 1 |
| 15 | Informational | Session Management Response Identified | overwatch.overdrive.co.za | 1 |
| 16 | Informational | Storable but Non-Cacheable Content | overwatch.overdrive.co.za | 1 |
03 Findings Detailed observations, ordered by severity
Each finding records what was observed, where it was observed, and supporting evidence from the scanning toolchain.
Content Security Policy (CSP) Header Not Set
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.
Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.
- 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/
Cookie No HttpOnly Flag
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.
- https://owasp.org/www-community/HttpOnly
Cookie Without Secure Flag
A cookie has been set without the secure flag, which means that the cookie can be accessed via unencrypted connections.
Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.
- https://owasp.org/www-project-web-security-testing-guide/v41/4-Web_Application_Security_Testing/06-Session_Management_Testing/02-Testing_for_Cookies_Attributes.html
Cookie with SameSite Attribute None
A cookie has been set with its SameSite attribute set to "none", 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.
Ensure that the SameSite attribute is set to either 'lax' or ideally 'strict' for all cookies.
- https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-same-site
Cookie without SameSite Attribute
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.
Ensure that the SameSite attribute is set to either 'lax' or ideally 'strict' for all cookies.
- https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-same-site
Cross-Origin-Embedder-Policy Header Missing or Invalid
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).
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).
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cross-Origin-Embedder-Policy
Cross-Origin-Opener-Policy Header Missing or Invalid
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.
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).
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cross-Origin-Opener-Policy
Cross-Origin-Resource-Policy Header Missing or Invalid
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.
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).
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cross-Origin-Embedder-Policy
Permissions Policy Header Not Set
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.
Ensure that your web server, application server, load balancer, etc. is configured to set the Permissions-Policy header.
- 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/
Server Leaks Version Information via "Server" HTTP Response Header Field
The web/application server is leaking version information via the "Server" HTTP response header. Access to such information may facilitate attackers identifying other vulnerabilities your web/application server is subject to.
Ensure that your web server, application server, load balancer, etc. is configured to suppress the "Server" header or provide generic details.
- https://httpd.apache.org/docs/current/mod/core.html#servertokens
- https://learn.microsoft.com/en-us/previous-versions/msp-n-p/ff648552(v=pandp.10)
- https://www.troyhunt.com/shhh-dont-let-your-response-headers/
Strict-Transport-Security Header Not Set
HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.
Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.
- https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Strict_Transport_Security_Cheat_Sheet.html
- https://owasp.org/www-community/Security_Headers
- https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
- https://caniuse.com/stricttransportsecurity
- https://datatracker.ietf.org/doc/html/rfc6797
Modern Web Application
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.
This is an informational alert and so no changes are required.
Non-Storable Content
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).
- https://datatracker.ietf.org/doc/html/rfc7234
- https://datatracker.ietf.org/doc/html/rfc7231
- https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html
Re-examine Cache-control Directives
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".
- https://cheatsheetseries.owasp.org/cheatsheets/Session_Management_Cheat_Sheet.html#web-content-caching
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cache-Control
- https://grayduck.mn/2021/09/13/cache-control-recommendations/
Session Management Response Identified
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.
This is an informational alert rather than a vulnerability and so there is nothing to fix.
- https://www.zaproxy.org/docs/desktop/addons/authentication-helper/session-mgmt-id/
Storable but Non-Cacheable Content
The response contents are storable by caching components such as proxy servers, but will not be retrieved directly from the cache, without validating the request upstream, in response to similar requests from other users.
- https://datatracker.ietf.org/doc/html/rfc7234
- https://datatracker.ietf.org/doc/html/rfc7231
- https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html
04 Network & transport 2 observations
| # | Endpoint | Service | Detail | Severity |
|---|---|---|---|---|
| N-01 | 100.63.22.229:443 | https | Service https on 100.63.22.229:443/tcp | Info |
| N-02 | https://overwatch.overdrive.co.za/ | Status 200 | Amazon ALB, Amazon Web Services, HSTS, Nginx | Info |
05 Additional informational findings 0 items
| # | Finding | Affected | Instances |
|---|