Vulnerability Scan Result
| Title: | TSA Tallinn (W) – Siauliai (W) Diffusione in diretta di | Donne. Lega Baltica, 12.03.2025 | guarda online / LiveTV |
| Description: | TSA Tallinn (W) - Siauliai (W) Diffusione in diretta di Donne. Lega Baltica 12.03.25. Guarda il calcio online gratuitamente in qualità HD su tutti i dispositivi. Ora di inizio: 19:00 (UTC+3). |
| IP address | 104.21.32.1 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
| IP address | 104.21.48.1 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
| IP address | 104.21.96.1 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
| IP address | 104.21.80.1 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
| IP address | 104.21.16.1 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
| IP address | 104.21.64.1 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
| IP address | 104.21.112.1 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | cloudflare - |
8080/tcp | http | Cloudflare http proxy - |
8443/tcp | http | cloudflare - |
| Software / Version | Category |
|---|---|
| Facebook Pixel | Analytics |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| Liveinternet | Analytics |
| Yandex.Metrika | Analytics |
| MinIO | Network storage |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Cloudflare | CDN |
| RSS | Miscellaneous |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://livetvx.torrentproxy.net/it/eventinfo/281319354_tsa_tallinn_w_siauliai_w | view, PHPSESSID | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: view=1 Set-Cookie: PHPSESSID=oo092g6nvc7reoiklcrn180b0o |
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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://livetvx.torrentproxy.net/it/eventinfo/281319354_tsa_tallinn_w_siauliai_w | view, PHPSESSID | Set-Cookie: view=1 Set-Cookie: PHPSESSID=oo092g6nvc7reoiklcrn180b0o |
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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| Software / Version | Category |
|---|---|
| Facebook Pixel | Analytics |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| Liveinternet | Analytics |
| Yandex.Metrika | Analytics |
| MinIO | Network storage |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Cloudflare | CDN |
| RSS | 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.
Classification
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
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).
Classification
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| livetvx.torrentproxy.net | A | IPv4 address | 104.21.16.1 |
| livetvx.torrentproxy.net | A | IPv4 address | 104.21.80.1 |
| livetvx.torrentproxy.net | A | IPv4 address | 104.21.48.1 |
| livetvx.torrentproxy.net | A | IPv4 address | 104.21.112.1 |
| livetvx.torrentproxy.net | A | IPv4 address | 104.21.64.1 |
| livetvx.torrentproxy.net | A | IPv4 address | 104.21.32.1 |
| livetvx.torrentproxy.net | A | IPv4 address | 104.21.96.1 |
| livetvx.torrentproxy.net | AAAA | IPv6 address | 2606:4700:3030::6815:1001 |
| livetvx.torrentproxy.net | AAAA | IPv6 address | 2606:4700:3030::6815:7001 |
| livetvx.torrentproxy.net | AAAA | IPv6 address | 2606:4700:3030::6815:4001 |
| livetvx.torrentproxy.net | AAAA | IPv6 address | 2606:4700:3030::6815:2001 |
| livetvx.torrentproxy.net | AAAA | IPv6 address | 2606:4700:3030::6815:3001 |
| livetvx.torrentproxy.net | AAAA | IPv6 address | 2606:4700:3030::6815:5001 |
| livetvx.torrentproxy.net | AAAA | IPv6 address | 2606:4700:3030::6815:6001 |
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.0-RELEASE | 91% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| MinIO | Network storage |
| PHP | Programming languages |
| Yandex.Metrika | Analytics |
| Liveinternet | Analytics |
| Cloudflare | CDN |
| HTTP/3 | 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 |
|---|---|
| MinIO | Network storage |
| PHP | Programming languages |
| Yandex.Metrika | Analytics |
| Liveinternet | Analytics |
| Cloudflare | CDN |
| HTTP/3 | 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 |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | 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 |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | 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.