Vulnerability Scan Result
| Title: | tawk.to – "100% FREE live chat software for your website!" |
| Description: | www.tawk.to is 100% Free Live Chat Software to monitor and chat with visitors on your website or from a free customizable page. |
| IP address | 104.22.44.142 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
| IP address | 104.22.45.142 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
| IP address | 172.67.15.14 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
2082/tcp | http | Cloudflare http proxy - |
2083/tcp | https | nginx - |
2086/tcp | http | Cloudflare http proxy - |
2087/tcp | https | nginx - |
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| Twitter Ads | Advertising |
| Linkedin Ads | Advertising |
| Linkedin Insight Tag | Analytics |
| Google Hosted Libraries | CDN |
| Elementor 3.29.0 | Page builders, WordPress plugins |
| Hello Elementor | WordPress themes |
| Facebook Pixel | Analytics |
| Font Awesome | Font scripts |
| jQuery Migrate | JavaScript libraries |
| Heap | Analytics |
| HTTP/3 | Miscellaneous |
| jQuery 3.6.3 | JavaScript libraries |
| MySQL | Databases |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| Site Kit 1.153.0 | Analytics, WordPress plugins |
| Google Ads Conversion Tracking | Analytics |
| Tawk.to | Live chat |
| Basic | Security |
| WordPress | CMS, Blogs |
| WPML 4.7.4 | WordPress plugins, Translation |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| WordPress Super Cache | Caching, WordPress plugins |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://www.tawk.to/ | 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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| https://www.tawk.to/ | 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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| Twitter Ads | Advertising |
| Linkedin Ads | Advertising |
| Linkedin Insight Tag | Analytics |
| Google Hosted Libraries | CDN |
| Elementor 3.29.0 | Page builders, WordPress plugins |
| Hello Elementor | WordPress themes |
| Facebook Pixel | Analytics |
| Font Awesome | Font scripts |
| jQuery Migrate | JavaScript libraries |
| Heap | Analytics |
| HTTP/3 | Miscellaneous |
| jQuery 3.6.3 | JavaScript libraries |
| MySQL | Databases |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| Site Kit 1.153.0 | Analytics, WordPress plugins |
| Google Ads Conversion Tracking | Analytics |
| Tawk.to | Live chat |
| Basic | Security |
| WordPress | CMS, Blogs |
| WPML 4.7.4 | WordPress plugins, Translation |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| WordPress Super Cache | Caching, WordPress plugins |
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
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
Vulnerability description
Website is accessible.
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
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.tawk.to | TXT | Text record | "v=DMARC1; p=none; sp=none; rua=mailto:dmarc.rua@tawk.to; ruf=mailto:dmarc.ruf@tawk.to; rf=afrf; ri=86400; pct=100; fo=1; adkim=r; aspf=r;" |
Vulnerability description
We found that the target uses p=none in the DMARC policy. The DMARC policy set to p=none means that the domain owner is not taking any action on emails that fail DMARC validation. This configuration effectively disables enforcement, allowing potentially spoofed or fraudulent emails to be delivered without any additional scrutiny.
Risk description
Emails that fail DMARC checks are still delivered to recipients. This leaves the domain highly vulnerable to email spoofing and phishing attacks, as malicious actors can impersonate the domain without facing any consequences from DMARC enforcement.
Recommendation
We recommend changing the DMARC policy to p=quarantine or, ideally, p=reject to actively block or quarantine emails that fail DMARC validation. This will enhance the security of your domain against spoofing and phishing attacks by ensuring that only legitimate emails are delivered.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.tawk.to | TXT | Text record | "v=DMARC1; p=none; sp=none; rua=mailto:dmarc.rua@tawk.to; ruf=mailto:dmarc.ruf@tawk.to; rf=afrf; ri=86400; pct=100; fo=1; adkim=r; aspf=r;" |
Vulnerability description
We found that the DMARC record for the domain is configured with sp=none, meaning that no policy is enforced for subdomains. This allows subdomains to send emails without being subject to DMARC checks, making it easier for attackers to spoof emails from these subdomains. Subdomains are often overlooked in email security, and attackers can exploit this misconfiguration to launch phishing or spoofing attacks from seemingly legitimate subdomains of a protected domain.
Risk description
When the DMARC record is configured with sp=none, subdomains are not subject to DMARC enforcement, allowing attackers to spoof emails from subdomains without being blocked. This creates a significant risk of phishing and impersonation attacks, where malicious emails appear to originate from trusted subdomains. These spoofed emails can be used to deceive users or damage the organization's reputation, undermining the security benefits of DMARC for the primary domain.
Recommendation
To mitigate the risk, we recommend that the subdomain policy should be updated to sp=reject to ensure that any email failing DMARC checks from subdomains is automatically rejected. This will help prevent unauthorized emails from being sent from subdomains, reducing the risk of spoofing and phishing. Additionally, it's important to regularly monitor DMARC reports to track email activity from subdomains and adjust policies as needed to maintain consistent security across the entire domain.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| tawk.to | A | IPv4 address | 104.22.45.142 |
| tawk.to | A | IPv4 address | 104.22.44.142 |
| tawk.to | A | IPv4 address | 172.67.15.14 |
| tawk.to | NS | Name server | amy.ns.cloudflare.com |
| tawk.to | NS | Name server | seth.ns.cloudflare.com |
| tawk.to | MX | Mail server | 1 aspmx.l.google.com |
| tawk.to | MX | Mail server | 10 aspmx2.googlemail.com |
| tawk.to | MX | Mail server | 10 aspmx3.googlemail.com |
| tawk.to | MX | Mail server | 5 alt1.aspmx.l.google.com |
| tawk.to | MX | Mail server | 5 alt2.aspmx.l.google.com |
| tawk.to | SOA | Start of Authority | amy.ns.cloudflare.com. dns.cloudflare.com. 2373920103 10000 2400 604800 1800 |
| tawk.to | AAAA | IPv6 address | 2606:4700:10::ac43:f0e |
| tawk.to | AAAA | IPv6 address | 2606:4700:10::6816:2d8e |
| tawk.to | AAAA | IPv6 address | 2606:4700:10::6816:2c8e |
| tawk.to | TXT | Text record | "MS=ms74305633" |
| tawk.to | TXT | Text record | "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJkb21haW4iOiJ0YXdrLnRvIiwiZXhwIjoxNjU3NzU2ODAwfQ.KNwUZ7T6rHHLFEUKH23Mrr0AGIZnzWdIEXrznoludcU" |
| tawk.to | TXT | Text record | "facebook-domain-verification=qhde5lf0e95om273eq3dax2594sz4j" |
| tawk.to | TXT | Text record | "google-site-verification=xfxcBNycIC4X65bnF6gQAEui_JhaWq7QxiM2Jzmj17k" |
| tawk.to | TXT | Text record | "tiktok-developers-site-verification=AuZueQR2DuNvtrOpAW7qwDZrDJizOmrZ" |
| tawk.to | SPF | Sender Policy Framework | "v=spf1 include:_spf.google.com include:amazonses.com include:smtp1.uservoice.com include:mta.tawk.to -all" |
| _dmarc.tawk.to | TXT | Text record | "v=DMARC1; p=none; sp=none; rua=mailto:dmarc.rua@tawk.to; ruf=mailto:dmarc.ruf@tawk.to; rf=afrf; ri=86400; pct=100; fo=1; adkim=r; aspf=r;" |
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
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.1-STABLE | 91% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| tawk.to | SPF | Sender Policy Framework | "v=spf1 include:_spf.google.com include:amazonses.com include:smtp1.uservoice.com include:mta.tawk.to -all" |
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| s1 | rsa | 1446 | "k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0jfMOk/IeYkMAeA2gUgxBzEzyCSiAbuuEsXKwipvoHQyRvp2HcT7BCD/HaitlvvLmeSQzCHzxJdWwk+uKVnIb1j9i633j/KzPHBoCL0n6lnhyiW9qkdm/o/jbeLYfXPsVlEhfxXKHydnIFHhhGW2GuzxxTjQYUu4iSOa87r/QgmqgH3mtxc1ink7/jCGVqxfJ8kLh" "QTcazfAl5RhiPi9XDx/Ontr7/PFqiiRo5zk0DcjEKPiPZcyL9ea6+wLqgis41jFxFzntmHqZYiU2G3VAEIN3Z/dzylnP2YAtd2FWS/+R/4fZIkIY9hLehQSLqe6l1NhoUPd88rHSfnvJyjrMQIDAQAB" |
| s2 | rsa | 1446 | "k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAm2/bCFoIfqBhnAjNs/iAzIFiZj0xG2cb2/KKZ6uw75e25uDf0eus2IbGbtDGYhOs/4pXdBo+ejP7SM9eHU42Y7ohYfi8r4OzjWuXoGgqYlVUmsciYSt0lNSHDpJGRHQFPT1QkGWdvAvzCh9L5TWuGqxdE3ZNClpCl1GMVsXyqJgdrypqPG4zYGjIHGRd0/GYUDDcU" "FOqJ6YUQvMATLyv07ibl/fR//7D3oPmUZoPHkmKa9JsvxKK8YzcVec7vaYO/n6IQedmW00eBTIANIiyDZnYkc9zMXy1pLzFMRHc3EPvIHYjbbNtpQ9egjXrCzCwpjBN+zeuzWApWLe5xh4cjwIDAQAB" |
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.