Vulnerability Scan Result
| Title: | Your site isn’t published yet | Wix Vibe |
| Description: | No description found |
| ip_address | 104.18.31.108 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
| ip_address | 104.18.30.108 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | cloudflare - |
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 | http | cloudflare - |
| Software / Version | Category |
|---|---|
| Google Cloud | IaaS |
| Google Cloud CDN | CDN |
| Open Graph | Miscellaneous |
| React | JavaScript frameworks |
| Sirvoy | Appointment scheduling |
| Cloudflare | CDN |
| Lodash | JavaScript libraries |
| HSTS | Security |
| Wix | CMS, Blogs |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| http://www.vanguardlabs.ai/ | ssr-caching | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: ssr-caching=cache#desc=hit#varnish=hit_hit#dc#desc=fastly_g |
Vulnerability description
We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
| CWE | CWE-1004 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| http://www.vanguardlabs.ai/ | ssr-caching | Set-Cookie: ssr-caching=cache#desc=hit#varnish=hit_hit#dc#desc=fastly_g |
Vulnerability description
We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.
Recommendation
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.
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Response URL | Evidence |
|---|---|---|
| http://www.vanguardlabs.ai/ | http://www.vanguardlabs.ai/ | Communication is made over unsecure, unencrypted HTTP. |
Vulnerability description
We noticed that the communication between the web browser and the server is done using the HTTP protocol, which transmits data unencrypted over the network.
Risk description
The risk is that an attacker who manages to intercept the communication at the network level can read and modify the data transmitted (including passwords, secret tokens, credit card information and other sensitive data).
Recommendation
We recommend you to reconfigure the web server to use HTTPS - which encrypts the communication between the web browser and the server.
Classification
| CWE | CWE-311 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Google Cloud | IaaS |
| Google Cloud CDN | CDN |
| Open Graph | Miscellaneous |
| React | JavaScript frameworks |
| Sirvoy | Appointment scheduling |
| Cloudflare | CDN |
| Lodash | JavaScript libraries |
| HSTS | Security |
| Wix | CMS, Blogs |
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
| URL | Evidence |
|---|---|
| http://www.vanguardlabs.ai/ | Response does not include the HTTP Content-Security-Policy security header or meta tag |
Vulnerability description
We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.
Risk description
The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.
Recommendation
Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Wix | CMS, Blogs |
| React | JavaScript frameworks |
| Google Cloud | IaaS |
| Lodash | JavaScript libraries |
| Sirvoy | Appointment scheduling |
| HSTS | Security |
| Google Cloud CDN | CDN |
| Cloudflare | CDN |
| Open Graph | Miscellaneous |
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 |
|---|---|
| Wix | CMS, Blogs |
| React | JavaScript frameworks |
| Google Cloud | IaaS |
| Lodash | JavaScript libraries |
| Sirvoy | Appointment scheduling |
| HSTS | Security |
| Google Cloud CDN | CDN |
| Cloudflare | CDN |
| Open Graph | Miscellaneous |
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 |
|---|---|
| Wix | CMS, Blogs |
| React | JavaScript frameworks |
| Google Cloud | IaaS |
| Lodash | JavaScript libraries |
| Sirvoy | Appointment scheduling |
| HSTS | Security |
| Google Cloud CDN | CDN |
| Cloudflare | CDN |
| Open Graph | Miscellaneous |
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 |
|---|---|
| Wix | CMS, Blogs |
| React | JavaScript frameworks |
| Google Cloud | IaaS |
| Lodash | JavaScript libraries |
| Sirvoy | Appointment scheduling |
| HSTS | Security |
| Google Cloud CDN | CDN |
| Cloudflare | CDN |
| Open Graph | Miscellaneous |
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 |
|---|---|
| Wix | CMS, Blogs |
| React | JavaScript frameworks |
| Google Cloud | IaaS |
| Lodash | JavaScript libraries |
| Sirvoy | Appointment scheduling |
| HSTS | Security |
| Google Cloud CDN | CDN |
| Cloudflare | CDN |
| Open Graph | Miscellaneous |
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.vanguardlabs.ai | A | IPv4 address | 104.18.31.108 |
| www.vanguardlabs.ai | A | IPv4 address | 104.18.30.108 |
| www.vanguardlabs.ai | AAAA | IPv6 address | 2606:4700::6812:1e6c |
| www.vanguardlabs.ai | AAAA | IPv6 address | 2606:4700::6812:1f6c |
| www.vanguardlabs.ai | CNAME | Canonical name | cname.wix-vibe.com |
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 |
|---|---|
| Wix | CMS, Blogs |
| React | JavaScript frameworks |
| Google Cloud | IaaS |
| Sirvoy | Appointment scheduling |
| HSTS | Security |
| Google Cloud CDN | CDN |
| Cloudflare | CDN |
| Lodash | 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 |
|---|---|
| Wix | CMS, Blogs |
| React | JavaScript frameworks |
| Google Cloud | IaaS |
| Lodash | JavaScript libraries |
| Sirvoy | Appointment scheduling |
| HSTS | Security |
| Google Cloud CDN | CDN |
| Cloudflare | CDN |
| Open Graph | Miscellaneous |
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 |
|---|---|
| Wix | CMS, Blogs |
| React | JavaScript frameworks |
| Google Cloud | IaaS |
| Lodash | JavaScript libraries |
| Sirvoy | Appointment scheduling |
| HSTS | Security |
| Google Cloud CDN | CDN |
| Cloudflare | CDN |
| Open Graph | Miscellaneous |
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.