Security Assessment Report
Vulnerability findings for the public-facing infrastructure of tauspace.com
01 Executive overview Severity distribution across 40 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 | Absence of Anti-CSRF Tokens | tauspace.com | 4 |
| 02 | Medium | Content Security Policy (CSP) Header Not Set | tauspace.com | 5 |
| 03 | Medium | Cross-Domain Misconfiguration | tauspace.com | 5 |
| 04 | Medium | Missing Anti-clickjacking Header | tauspace.com | 5 |
| 05 | Medium | Sub Resource Integrity Attribute Missing | tauspace.com | 5 |
| 06 | Low | Cross-Origin-Embedder-Policy Header Missing or Invalid | tauspace.com | 5 |
| 07 | Low | Cross-Origin-Opener-Policy Header Missing or Invalid | tauspace.com | 5 |
| 08 | Low | Information Disclosure - Debug Error Messages | tauspace.com | 1 |
| 09 | Low | Permissions Policy Header Not Set | tauspace.com | 5 |
| 10 | Low | Strict-Transport-Security Header Not Set | tauspace.com | 5 |
| 11 | Low | X-Content-Type-Options Header Missing | tauspace.com | 2 |
| 12 | Informational | Information Disclosure - Suspicious Comments | tauspace.com | 1 |
| 13 | Informational | Modern Web Application | tauspace.com | 3 |
| 14 | Informational | Non-Storable Content | tauspace.com | 1 |
| 15 | Informational | Re-examine Cache-control Directives | tauspace.com | 5 |
| 16 | Informational | Storable and Cacheable Content | tauspace.com | 2 |
| 17 | Informational | Storable but Non-Cacheable Content | tauspace.com | 4 |
03 Findings Detailed observations, ordered by severity
Each finding records what was observed, where it was observed, and supporting evidence from the scanning toolchain.
Absence of Anti-CSRF Tokens
No Anti-CSRF tokens were found in a HTML submission form.
A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.
CSRF attacks are effective in a number of situations, including:
* The victim has an active session on the target site.
* The victim is authenticated via HTTP auth on the target site.
* The victim is on the same local network as the target site.
CSRF has primarily been used to perform an action against a target site using the victim's privileges, but recent techniques have been discovered to disclose information by gaining access to the response. The risk of information disclosure is dramatically increased when the target site is vulnerable to XSS, because XSS can be used as a platform for CSRF, allowing the attack to operate within the bounds of the same-origin policy.
Phase: Architecture and Design
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
For example, use anti-CSRF packages such as the OWASP CSRFGuard.
Phase: Implementation
Ensure that your application is free of cross-site scripting issues, because most CSRF defenses can be bypassed using attacker-controlled script.
Phase: Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
Note that this can be bypassed using XSS.
Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
Note that this can be bypassed using XSS.
Use the ESAPI Session Management control.
This control includes a component for CSRF.
Do not use the GET method for any request that triggers a state change.
Phase: Implementation
Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
- https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html
- https://cwe.mitre.org/data/definitions/352.html
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/
Cross-Domain Misconfiguration
Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.
Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.
- https://vulncat.fortify.com/en/detail?category=HTML5&subcategory=Overly%20Permissive%20CORS%20Policy
Missing Anti-clickjacking Header
The response does not protect against 'ClickJacking' attacks. It should include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options.
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.
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-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/Defenses/Subresource_Integrity
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
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.
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/
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
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
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 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/
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
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 23 observations
| # | Endpoint | Service | Detail | Severity |
|---|---|---|---|---|
| N-01 | 104.21.85.127:443 | https | Service https on 104.21.85.127:443/tcp | Info |
| N-02 | 104.21.85.127:80 | http | Service http on 104.21.85.127:80/tcp | Info |
| N-03 | 104.21.85.127:8080 | http-proxy | Service http-proxy on 104.21.85.127:8080/tcp | Info |
| N-04 | 104.21.85.127:8443 | https-alt | Service https-alt on 104.21.85.127:8443/tcp | Info |
| N-05 | https://tauspace.com | Status 200 | Cloudflare, Cloudflare Browser Insights, HTTP/3 | Info |
| N-06 | innovation.tauspace.com | subfinder | source: submd | Info |
| N-07 | tspfsense01.firewall.tauspace.com | subfinder | source: submd | Info |
| N-08 | za.tauspace.com | subfinder | source: submd | Info |
| N-09 | u003eprojects.tauspace.com | subfinder | source: submd | Info |
| N-10 | s1.tauspace.com | subfinder | source: thc | Info |
| N-11 | strat.tauspace.com | subfinder | source: thc | Info |
| N-12 | www.strat.tauspace.com | subfinder | source: thc | Info |
| N-13 | bd.tauspace.com | subfinder | source: thc | Info |
| N-14 | helpdesk.tauspace.com | subfinder | source: thc | Info |
| N-15 | helpfuldesk.tauspace.com | subfinder | source: thc | Info |
| N-16 | homebase.tauspace.com | subfinder | source: thc | Info |
| N-17 | support.tauspace.com | subfinder | source: thc | Info |
| N-18 | bd-aws.tauspace.com | subfinder | source: thc | Info |
| N-19 | fcapi.tauspace.com | subfinder | source: thc | Info |
| N-20 | tspfsense02.firewall.tauspace.com | subfinder | source: thc | Info |
| N-21 | projects.tauspace.com | subfinder | source: thc | Info |
| N-22 | wiki.tauspace.com | subfinder | source: thc | Info |
| N-23 | www.tauspace.com | subfinder | source: thc | Info |
05 Additional informational findings 0 items
| # | Finding | Affected | Instances |
|---|