Vulnerability Scan Result
| Title: | Laravel |
| Description: | No description found |
| ip_address | 62.72.21.219 |
| country | LT  |
| network_name | Ripe NCC ASN Block |
| asn | AS47583 |
22/tcp | ssh | OpenSSH 9.6p1 Ubuntu 3ubuntu13.11 |
80/tcp | http | nginx - |
443/tcp | https | nginx - |
| Software / Version | Category |
|---|---|
| Alpine.js 3.14.3 | JavaScript frameworks |
| Bunny | CDN |
| Filamentphp | Development |
| Bunny Fonts | Font scripts |
| Livewire | Web frameworks, Miscellaneous |
| Laravel | Web frameworks |
| Nginx | Web servers, Reverse proxies |
| PHP | Programming languages |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://tw-tracker.com/ | Response headers do not include the HTTP Strict-Transport-Security header |
Vulnerability description
We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.
Risk description
The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).
Recommendation
The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://tw-tracker.com/ | 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
| Software / Version | Category |
|---|---|
| Alpine.js 3.14.3 | JavaScript frameworks |
| Bunny | CDN |
| Filamentphp | Development |
| Bunny Fonts | Font scripts |
| Livewire | Web frameworks, Miscellaneous |
| Laravel | Web frameworks |
| Nginx | Web servers, Reverse proxies |
| PHP | Programming languages |
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 |
|---|---|
| https://tw-tracker.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
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.
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
We found insecure DNS cookie usage on the following nameservers: ns2.dns-parking.com, ns1.dns-parking.com
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 4.15 - 5.6 | 100% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| PHP | Programming languages |
| Nginx | Web servers, Reverse proxies |
| Laravel | Web frameworks |
| Alpine.js | JavaScript frameworks |
| Livewire | Web frameworks, 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 |
|---|---|---|---|
| tw-tracker.com | A | IPv4 address | 62.72.21.219 |
| tw-tracker.com | NS | Name server | ns2.dns-parking.com |
| tw-tracker.com | NS | Name server | ns1.dns-parking.com |
| tw-tracker.com | SOA | Start of Authority | ns1.dns-parking.com. dns.hostinger.com. 2025103001 10000 2400 604800 600 |
| tw-tracker.com | CAA | Certificate Authority Authorization | 0 issuewild "globalsign.com" |
| tw-tracker.com | CAA | Certificate Authority Authorization | 0 issue "globalsign.com" |
| tw-tracker.com | CAA | Certificate Authority Authorization | 0 issue "sectigo.com" |
| tw-tracker.com | CAA | Certificate Authority Authorization | 0 issuewild "sectigo.com" |
| tw-tracker.com | CAA | Certificate Authority Authorization | 0 issue "digicert.com" |
| tw-tracker.com | CAA | Certificate Authority Authorization | 0 issuewild "pki.goog" |
| tw-tracker.com | CAA | Certificate Authority Authorization | 0 issue "pki.goog" |
| tw-tracker.com | CAA | Certificate Authority Authorization | 0 issue "comodoca.com" |
| tw-tracker.com | CAA | Certificate Authority Authorization | 0 issuewild "digicert.com" |
| tw-tracker.com | CAA | Certificate Authority Authorization | 0 issuewild "comodoca.com" |
| tw-tracker.com | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| tw-tracker.com | CAA | Certificate Authority Authorization | 0 issuewild "letsencrypt.org" |
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.