Security Assessment Report
Vulnerability findings for the public-facing infrastructure of scan.overdrive.co.za
01 Executive overview Severity distribution across 27 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: script-src unsafe-inline | scan.overdrive.co.za | 5 |
| 02 | Medium | CSP: style-src unsafe-inline | scan.overdrive.co.za | 5 |
| 03 | Low | Application Error Disclosure | scan.overdrive.co.za | 8 |
| 04 | Low | Cross-Origin-Embedder-Policy Header Missing or Invalid | scan.overdrive.co.za | 5 |
| 05 | Low | Information Disclosure - Debug Error Messages | scan.overdrive.co.za | 8 |
| 06 | Informational | Authentication Request Identified | scan.overdrive.co.za | 2 |
| 07 | Informational | Information Disclosure - Sensitive Information in URL | scan.overdrive.co.za | 5 |
| 08 | Informational | Information Disclosure - Suspicious Comments | scan.overdrive.co.za | 4 |
| 09 | Informational | Modern Web Application | scan.overdrive.co.za | 5 |
| 10 | Informational | Non-Storable Content | scan.overdrive.co.za | 1 |
| 11 | Informational | Re-examine Cache-control Directives | scan.overdrive.co.za | 1 |
| 12 | Informational | Storable and Cacheable Content | scan.overdrive.co.za | 5 |
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: script-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
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
Application Error Disclosure
This page contains an error/warning message that may disclose sensitive information like the location of the file that produced the unhandled exception. This information can be used to launch further attacks against the web application. The alert could be a false positive if the error message is found inside a documentation page.
Review the source code of this page. Implement custom error pages. Consider implementing a mechanism to provide a unique error reference/identifier to the client (browser) while logging the details on the server side and not exposing them to the user.
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
Information Disclosure - Debug Error Messages
The response appeared to contain common error messages returned by platforms such as ASP.NET, and Web-servers such as IIS and Apache. You can configure the list of common debug messages.
Disable debugging messages before pushing to production.
Authentication Request Identified
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.
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/auth-req-id/
Information Disclosure - Sensitive Information in URL
The request appeared to contain sensitive information leaked in the URL. This can violate PCI and most organizational compliance policies. You can configure the list of strings for this check to add or remove values specific to your environment.
Do not pass sensitive information in URIs.
Information Disclosure - Suspicious Comments
The response appears to contain suspicious comments which may help an attacker.
Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.
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/
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 15 observations
| # | Endpoint | Service | Detail | Severity |
|---|---|---|---|---|
| N-01 | 129.232.138.226:110 | pop3 | Service pop3 on 129.232.138.226:110/tcp | Info |
| N-02 | 129.232.138.226:143 | imap | Service imap on 129.232.138.226:143/tcp | Info |
| N-03 | 129.232.138.226:21 | ftp | Service ftp on 129.232.138.226:21/tcp | Info |
| N-04 | 129.232.138.226:22 | ssh | Service ssh on 129.232.138.226:22/tcp | Info |
| N-05 | 129.232.138.226:443 | https | Service https on 129.232.138.226:443/tcp | Info |
| N-06 | 129.232.138.226:465 | smtps | Service smtps on 129.232.138.226:465/tcp | Info |
| N-07 | 129.232.138.226:587 | submission | Service submission on 129.232.138.226:587/tcp | Info |
| N-08 | 129.232.138.226:80 | http | Service http on 129.232.138.226:80/tcp | Info |
| N-09 | 129.232.138.226:993 | imaps | Service imaps on 129.232.138.226:993/tcp | Info |
| N-10 | 129.232.138.226:995 | pop3s | Service pop3s on 129.232.138.226:995/tcp | Info |
| N-11 | https://scan.overdrive.co.za/ | Status 200 | Apache HTTP Server, HSTS | Info |
| N-12 | mail.scan.overdrive.co.za | subfinder | source: thc | Info |
| N-13 | smtp.scan.overdrive.co.za | subfinder | source: thc | Info |
| N-14 | www.scan.overdrive.co.za | subfinder | source: thc | Info |
| N-15 | imap.scan.overdrive.co.za | subfinder | source: thc | Info |
05 Additional informational findings 0 items
| # | Finding | Affected | Instances |
|---|