Vulnerability findings for the public-facing infrastructure of takealot.com
01 Executive overview Severity distribution across 25 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 | CSP: Failure to Define Directive with No Fallback | takealot.com | 3 |
| 02 | Medium | CSP: script-src unsafe-eval | takealot.com | 3 |
| 03 | Medium | CSP: style-src unsafe-inline | takealot.com | 3 |
| 04 | Medium | Sub Resource Integrity Attribute Missing | takealot.com | 2 |
| 05 | Low | Cookie with SameSite Attribute None | takealot.com | 4 |
| 06 | Low | Cookie without SameSite Attribute | takealot.com | 3 |
| 07 | Low | Cross-Origin-Embedder-Policy Header Missing or Invalid | takealot.com | 1 |
| 08 | Low | Cross-Origin-Opener-Policy Header Missing or Invalid | takealot.com | 1 |
| 09 | Low | Cross-Origin-Resource-Policy Header Missing or Invalid | takealot.com | 1 |
| 10 | Low | Permissions Policy Header Not Set | takealot.com | 1 |
| 11 | Low | Server Leaks Information via "X-Powered-By" HTTP Response Header Field(s) | takealot.com | 1 |
| 12 | Low | Timestamp Disclosure - Unix | takealot.com | 5 |
| 13 | Low | X-Content-Type-Options Header Missing | takealot.com | 1 |
| 14 | Informational | CSP: Header & Meta | takealot.com | 3 |
| 15 | Informational | Loosely Scoped Cookie | takealot.com | 3 |
| 16 | Informational | Modern Web Application | takealot.com | 4 |
| 17 | Informational | Non-Storable Content | takealot.com | 3 |
| 18 | Informational | Re-examine Cache-control Directives | takealot.com | 1 |
| 19 | Informational | Session Management Response Identified | takealot.com | 2 |
| 20 | Informational | Storable and Cacheable Content | takealot.com | 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.
CSP: Failure to Define Directive with No Fallback
The Content Security Policy fails to define one of the directives that has no fallback. Missing/excluding them is the same as allowing anything.
Ensure that your web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.
- https://www.w3.org/TR/CSP/
- https://caniuse.com/#search=content+security+policy
- https://content-security-policy.com/
- https://github.com/HtmlUnit/htmlunit-csp
- https://web.dev/articles/csp#resource-options
CSP: script-src unsafe-eval
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.
Ensure that your web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.
- https://www.w3.org/TR/CSP/
- https://caniuse.com/#search=content+security+policy
- https://content-security-policy.com/
- https://github.com/HtmlUnit/htmlunit-csp
- https://web.dev/articles/csp#resource-options
CSP: style-src unsafe-inline
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.
Ensure that your web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.
- https://www.w3.org/TR/CSP/
- https://caniuse.com/#search=content+security+policy
- https://content-security-policy.com/
- https://github.com/HtmlUnit/htmlunit-csp
- https://web.dev/articles/csp#resource-options
Sub Resource Integrity Attribute Missing
The integrity attribute is missing on a script or link tag served by an external server. The integrity tag prevents an attacker who have gained access to this server from injecting a malicious content.
Provide a valid integrity attribute to the tag.
- https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
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 Information via "X-Powered-By" HTTP Response Header Field(s)
The web/application server is leaking information via one or more "X-Powered-By" HTTP response headers. Access to such information may facilitate attackers identifying other frameworks/components your web application is reliant upon and the vulnerabilities such components may be subject to.
Ensure that your web server, application server, load balancer, etc. is configured to suppress "X-Powered-By" headers.
- https://owasp.org/www-project-web-security-testing-guide/v42/4-Web_Application_Security_Testing/01-Information_Gathering/08-Fingerprint_Web_Application_Framework
- https://www.troyhunt.com/shhh-dont-let-your-response-headers/
Timestamp Disclosure - Unix
A timestamp was disclosed by the application/web server. - Unix
Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.
- https://cwe.mitre.org/data/definitions/200.html
X-Content-Type-Options Header Missing
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.
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.
- 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
CSP: Header & Meta
The message contained both CSP specified via header and via Meta tag. It was not possible to union these policies in order to perform an analysis. Therefore, they have been evaluated individually.
Ensure that your web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.
- https://www.w3.org/TR/CSP/
- https://caniuse.com/#search=content+security+policy
- https://content-security-policy.com/
- https://github.com/HtmlUnit/htmlunit-csp
- https://web.dev/articles/csp#resource-options
Loosely Scoped Cookie
Cookies can be scoped by domain or path. This check is only concerned with domain scope.The domain scope applied to a cookie determines which domains can access it. For example, a cookie can be scoped strictly to a subdomain e.g. www.nottrusted.com, or loosely scoped to a parent domain e.g. nottrusted.com. In the latter case, any subdomain of nottrusted.com can access the cookie. Loosely scoped cookies are common in mega-applications like google.com and live.com. Cookies set from a subdomain like app.foo.bar are transmitted only to that domain by the browser. However, cookies scoped to a parent-level domain may be transmitted to the parent, or any subdomain of the parent.
Always scope cookies to a FQDN (Fully Qualified Domain Name).
- https://datatracker.ietf.org/doc/html/rfc6265#section-4.1
- 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
- https://code.google.com/archive/p/browsersec/wikis/Part2.wiki
Modern Web Application
The application appears to be a modern web application. If you need to explore it automatically then the Ajax 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 and Cacheable Content
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.
- 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 5 observations
| # | Endpoint | Service | Detail | Severity |
|---|---|---|---|---|
| N-01 | 104.16.71.64:443 | https | Service https on 104.16.71.64:443/tcp | Info |
| N-02 | 104.16.71.64:80 | http | Service http on 104.16.71.64:80/tcp | Info |
| N-03 | 104.16.71.64:8080 | http-proxy | Service http-proxy on 104.16.71.64:8080/tcp | Info |
| N-04 | 104.16.71.64:8443 | https-alt | Service https-alt on 104.16.71.64:8443/tcp | Info |
| N-05 | https://www.takealot.com/ | Status 200 | Cloudflare, Cloudflare Bot Management, Cloudflare Browser Insights, Envoy, HSTS | Info |
05 Additional informational findings 0 items
| # | Finding | Affected | Instances |
|---|