Vulnerability Scan Result

ip_address | 148.75.192.117 |
country | US ![]() |
network_name | Cablevision Systems Corp |
asn | AS6128 |
80/tcp | http | OpenResty web app server - |
443/tcp | https | openresty - |
3389/tcp | ms-wbt-server | Microsoft Terminal Services - |
Software / Version | Category |
---|---|
Nginx | Web servers, Reverse proxies |
OpenResty | Web servers |
PHP 8.4.10 | Programming languages |
Vue.js | JavaScript frameworks |
HSTS | Security |
Web Application Vulnerabilities
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).
Evidence
URL | Evidence |
---|---|
https://browsiradio.galaxcast.com/login | 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 |
---|---|
Nginx | Web servers, Reverse proxies |
OpenResty | Web servers |
PHP 8.4.10 | Programming languages |
Vue.js | JavaScript frameworks |
HSTS | Security |
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
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.
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible Remote Desktop Protocol (RDP) service. PORT STATE SERVICE VERSION 3389/tcp open ms-wbt-server Microsoft Terminal Services
Vulnerability description
We found that the Remote Desktop Protocol (RDP) service is publicly accessible. Attackers often look for the Remote Desktop Protocol service due to its capability to provide remote access and control of a server, usually one that operates on the Microsoft Windows operating system.
Risk description
Exposing this service online can enable attackers to launch authentication attacks, like guessing login credentials, potentially gaining unauthorized access. Attackers might use publicly available employee information for brute-force attacks. Vulnerabilities, such as unpatched software or protocol flaws, could also be exploited. An example is CVE-2019-0708 (Bluekeep) vulnerability. Additionally, integration with Active Directory Domain Services could allow attackers to move laterally across the network, accessing more systems and sensitive data.
Recommendation
We recommend turning off Remote Desktop Protocol access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). Avoid permitting direct user authentication to Active Directory over the Internet to prevent attackers from engaging in password guessing or causing the lockout of legitimate domain user accounts. If the Remote Desktop Protocol service is essential for business purposes, limiting access to designated IP addresses is recommended.
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
Domain Queried | DNS Record Type | Description | Value |
---|---|---|---|
browsiradio.galaxcast.com | A | IPv4 address | 148.75.192.117 |
browsiradio.galaxcast.com | NS | Name server | ns2.dns-parking.com |
browsiradio.galaxcast.com | NS | Name server | ns1.dns-parking.com |
browsiradio.galaxcast.com | SOA | Start of Authority | ns1.dns-parking.com. dns.hostinger.com. 2025071701 10000 2400 604800 600 |
browsiradio.galaxcast.com | CAA | Certificate Authority Authorization | 0 issuewild "letsencrypt.org" |
browsiradio.galaxcast.com | CAA | Certificate Authority Authorization | 0 issue "globalsign.com" |
browsiradio.galaxcast.com | CAA | Certificate Authority Authorization | 0 issue "sectigo.com" |
browsiradio.galaxcast.com | CAA | Certificate Authority Authorization | 0 issuewild "pki.goog" |
browsiradio.galaxcast.com | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
browsiradio.galaxcast.com | CAA | Certificate Authority Authorization | 0 issuewild "digicert.com" |
browsiradio.galaxcast.com | CAA | Certificate Authority Authorization | 0 issue "comodoca.com" |
browsiradio.galaxcast.com | CAA | Certificate Authority Authorization | 0 issuewild "comodoca.com" |
browsiradio.galaxcast.com | CAA | Certificate Authority Authorization | 0 issue "pki.goog" |
browsiradio.galaxcast.com | CAA | Certificate Authority Authorization | 0 issue "digicert.com" |
browsiradio.galaxcast.com | CAA | Certificate Authority Authorization | 0 issuewild "sectigo.com" |
browsiradio.galaxcast.com | CAA | Certificate Authority Authorization | 0 issuewild "globalsign.com" |
browsiradio.galaxcast.com | CNAME | Canonical name | galaxcast.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
Operating System | Accuracy |
---|---|
Windows | 100% |
Vulnerability description
OS Detection
Evidence
Software / Version | Category |
---|---|
PHP 8.4.10 | Programming languages |
Nginx | Web servers, Reverse proxies |
Vue.js | JavaScript frameworks |
OpenResty | Web servers |
HSTS | Security |
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.