Vulnerability Scan Result
| Title: | Online Safety Training and Compliance Solutions |
| Description: | The most popular solution for obtaining an authorized OSHA 10 and OSHA 30 DOL card. ClickSafety helps customers build a comprehensive safety culture. Get started today! |
| ip_address | 104.16.153.25 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
| ip_address | 104.17.93.38 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | Cloudflare http proxy - |
2082/tcp | http | Cloudflare http proxy - |
2083/tcp | https | nginx - |
2086/tcp | http | Cloudflare http proxy - |
2087/tcp | https | nginx - |
8080/tcp | http | Cloudflare http proxy - |
8443/tcp | https | Cloudflare http proxy - |
| Software / Version | Category |
|---|---|
| Microsoft Advertising | Advertising |
| Linkedin Insight Tag | Analytics |
| Facebook Pixel 2.9.347 | Analytics |
| Bootstrap | UI frameworks |
| core-js 3.32.2 | JavaScript libraries |
| Goober | JavaScript libraries |
| Google Analytics | Analytics |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Slick | JavaScript libraries |
| Magento | Ecommerce |
| MySQL | Databases |
| New Relic | RUM |
| PayPal | Payment processors |
| PHP | Programming languages |
| Piwik PRO Core | Analytics |
| Platform.sh | PaaS |
| RequireJS 2.3.7 | JavaScript frameworks |
| Ensighten | Tag managers |
| DoubleClick Floodlight | Advertising |
| Vimeo | Video players |
| WordPress | CMS, Blogs |
| Braintree | Payment processors |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| HubSpot | Marketing automation |
| HubSpot Analytics | Analytics |
| Lodash 1.13.6 | JavaScript libraries |
| Optimizely | A/B Testing, Personalisation |
| HSTS | Security |
| theTradeDesk | Advertising |
| Cart Functionality | Ecommerce |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://www.clicksafety.com/ | Response headers do not include the Referrer-Policy HTTP security header as well as the |
Vulnerability description
We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.
Risk description
The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.
Recommendation
The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Microsoft Advertising | Advertising |
| Linkedin Insight Tag | Analytics |
| Facebook Pixel 2.9.347 | Analytics |
| Bootstrap | UI frameworks |
| core-js 3.32.2 | JavaScript libraries |
| Goober | JavaScript libraries |
| Google Analytics | Analytics |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Slick | JavaScript libraries |
| Magento | Ecommerce |
| MySQL | Databases |
| New Relic | RUM |
| PayPal | Payment processors |
| PHP | Programming languages |
| Piwik PRO Core | Analytics |
| Platform.sh | PaaS |
| RequireJS 2.3.7 | JavaScript frameworks |
| Ensighten | Tag managers |
| DoubleClick Floodlight | Advertising |
| Vimeo | Video players |
| WordPress | CMS, Blogs |
| Braintree | Payment processors |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| HubSpot | Marketing automation |
| HubSpot Analytics | Analytics |
| Lodash 1.13.6 | JavaScript libraries |
| Optimizely | A/B Testing, Personalisation |
| HSTS | Security |
| theTradeDesk | Advertising |
| Cart Functionality | Ecommerce |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.clicksafety.com/ | Response headers include the HTTP Content-Security-Policy security header with the following security issues: |
Vulnerability description
We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.
Risk description
For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.
Recommendation
Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.
Classification
| CWE | CWE-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
Vulnerability description
We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.
Risk description
There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.
Recommendation
We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).
Vulnerability description
We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.
Risk description
There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.
Recommendation
We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.
Classification
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
We managed to detect that Magento has reached the End-of-Life (EOL).
Version detected: 2 End-of-life date: 2018-03-01 Latest version for the cycle: 2.0.18 This release cycle (2.0) doesn't have long-term-support (LTS). The cycle was released on 2015-11-16 and its latest release date was 2018-02-20. The support ended on 2018-03-01.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.0-RELEASE | 91% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.clicksafety.com | A | IPv4 address | 104.16.153.25 |
| www.clicksafety.com | A | IPv4 address | 104.17.93.38 |
| www.clicksafety.com | AAAA | IPv6 address | 2606:4700::6810:9919 |
| www.clicksafety.com | AAAA | IPv6 address | 2606:4700::6811:5d26 |
Risk description
An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.
Recommendation
We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.
Evidence
| Software / Version | Category |
|---|---|
| Magento 2 | Ecommerce |
| Cart Functionality | Ecommerce |
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap | UI frameworks |
| Vimeo | Video players |
| RequireJS 2.3.7 | JavaScript frameworks |
| Braintree | Payment processors |
| Platform.sh | PaaS |
| PayPal | Payment processors |
| New Relic | RUM |
| Lodash 1.13.6 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| Slick | JavaScript libraries |
| Optimizely | A/B Testing, Personalisation |
| Microsoft Advertising | Advertising |
| HubSpot Analytics | Analytics |
| HubSpot | Marketing automation |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| Facebook Pixel 2.9.347 | Analytics |
| Ensighten | Tag managers |
| theTradeDesk | Advertising |
| Goober | JavaScript libraries |
| Piwik PRO Core | Analytics |
| DoubleClick Floodlight | Advertising |
| Linkedin Insight Tag | Analytics |
| HSTS | Security |
| Cloudflare | CDN |
| core-js 3.32.2 | JavaScript libraries |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.