Vulnerability Scan Result
| Title: | VIRGIN RADIO ROMANIA |
| Description: | Hip Hop,Trap & New Music |
| ip_address | 185.90.50.130 |
| country | GB  |
| network_name | Bigstep Cloud Limited |
| asn | AS201471 |
21/tcp | ftp | Pure-FTPd - |
25/tcp | smtp | - - |
53/tcp | domain | ISC BIND 9.11.4-P2 |
80/tcp | http | nginx - |
110/tcp | pop3 | Dovecot pop3d - |
143/tcp | imap | Dovecot imapd - |
443/tcp | https | nginx - |
465/tcp | smtp | Exim smtpd 4.99.1 |
587/tcp | smtp | Exim smtpd 4.99.1 |
993/tcp | imaps | - - |
995/tcp | pop3s | - - |
2078/tcp | https | cPanel httpd - |
2082/tcp | http | - - |
2083/tcp | https | - - |
2086/tcp | http | - - |
8080/tcp | http | Apache httpd - |
| Software / Version | Category |
|---|---|
| Facebook Pixel 2.9.252 | Analytics |
| Flickity | JavaScript libraries |
| particles.js | JavaScript graphics |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.21.1 | JavaScript libraries |
| Google Font API | Font scripts |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Moment.js 2.19.2 | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| prettyPhoto | JavaScript libraries |
| Open Graph | Miscellaneous |
| OneSignal | Marketing automation, A/B Testing |
| PHP | Programming languages |
| Skrollr 0.6.29 | JavaScript libraries |
| PWA | Miscellaneous |
| Priority Hints | Performance |
| WordPress | CMS, Blogs |
| Cxense | Personalisation, Segmentation |
| Google Tag Manager | Tag managers |
| MediaElement.js 4.2.16 | Video players |
| OneTrust | Cookie compliance |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2022-31129 | 7.5 | 0.03435 | 0.87153 | moment is a JavaScript date library for parsing, validating, manipulating, and formatting dates. Affected versions of moment were found to use an inefficient parsing algorithm. Specifically using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs. Users may notice a noticeable slowdown is observed with inputs above 10k characters. Users who pass user-provided strings without sanity length checks to moment constructor are vulnerable to (Re)DoS attacks. The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking. Users are advised to upgrade. Users unable to upgrade should consider limiting date lengths accepted from user input. |
| CVE-2022-24785 | 7.5 | 0.01439 | 0.80342 | Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js. |
| CVE-2017-18214 | 7.5 | 0.00322 | 0.54801 | The moment module before 2.19.3 for Node.js is prone to a regular expression denial of service via a crafted date string, a different vulnerability than CVE-2016-4055. |
Vulnerability description
Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.
Risk description
The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.
Classification
| CWE | CWE-1035 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://virginradio.ro/ | 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
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://virginradio.ro/ | 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 |
|---|---|
| Facebook Pixel 2.9.252 | Analytics |
| Flickity | JavaScript libraries |
| particles.js | JavaScript graphics |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.21.1 | JavaScript libraries |
| Google Font API | Font scripts |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Moment.js 2.19.2 | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| prettyPhoto | JavaScript libraries |
| Open Graph | Miscellaneous |
| OneSignal | Marketing automation, A/B Testing |
| PHP | Programming languages |
| Skrollr 0.6.29 | JavaScript libraries |
| PWA | Miscellaneous |
| Priority Hints | Performance |
| WordPress | CMS, Blogs |
| Cxense | Personalisation, Segmentation |
| Google Tag Manager | Tag managers |
| MediaElement.js 4.2.16 | Video players |
| OneTrust | Cookie compliance |
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.
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
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2020-8616 | 8.6 | 0.19877 | 0.95284 | No | A malicious actor who intentionally exploits this lack of effective limitation on the number of fetches performed when processing referrals can, through the use of specially crafted referrals, cause a recursing server to issue a very large number of fetches in an attempt to process the referral. This has at least two potential effects: The performance of the recursing server can potentially be degraded by the additional work required to perform these fetches, and The attacker can exploit this behavior to use the recursing server as a reflector in a reflection attack with a high amplification factor. |
| CVE-2021-25216 | 8.1 | 0.31412 | 0.96645 | No | In BIND 9.5.0 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.11.3-S1 -> 9.11.29-S1 and 9.16.8-S1 -> 9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.1 of the BIND 9.17 development branch, BIND servers are vulnerable if they are running an affected version and are configured to use GSS-TSIG features. In a configuration which uses BIND's default settings the vulnerable code path is not exposed, but a server can be rendered vulnerable by explicitly setting values for the tkey-gssapi-keytab or tkey-gssapi-credential configuration options. Although the default configuration is not vulnerable, GSS-TSIG is frequently used in networks where BIND is integrated with Samba, as well as in mixed-server environments that combine BIND servers with Active Directory domain controllers. For servers that meet these conditions, the ISC SPNEGO implementation is vulnerable to various attacks, depending on the CPU architecture for which BIND was built: For named binaries compiled for 64-bit platforms, this flaw can be used to trigger a buffer over-read, leading to a server crash. For named binaries compiled for 32-bit platforms, this flaw can be used to trigger a server crash due to a buffer overflow and possibly also to achieve remote code execution. We have determined that standard SPNEGO implementations are available in the MIT and Heimdal Kerberos libraries, which support a broad range of operating systems, rendering the ISC implementation unnecessary and obsolete. Therefore, to reduce the attack surface for BIND users, we will be removing the ISC SPNEGO implementation in the April releases of BIND 9.11 and 9.16 (it had already been dropped from BIND 9.17). We would not normally remove something from a stable ESV (Extended Support Version) of BIND, but since system libraries can replace the ISC SPNEGO implementation, we have made an exception in this case for reasons of stability and security. |
| CVE-2020-8625 | 8.1 | 0.02257 | 0.8423 | No | BIND servers are vulnerable if they are running an affected version and are configured to use GSS-TSIG features. In a configuration which uses BIND's default settings the vulnerable code path is not exposed, but a server can be rendered vulnerable by explicitly setting valid values for the tkey-gssapi-keytab or tkey-gssapi-credentialconfiguration options. Although the default configuration is not vulnerable, GSS-TSIG is frequently used in networks where BIND is integrated with Samba, as well as in mixed-server environments that combine BIND servers with Active Directory domain controllers. The most likely outcome of a successful exploitation of the vulnerability is a crash of the named process. However, remote code execution, while unproven, is theoretically possible. Affects: BIND 9.5.0 -> 9.11.27, 9.12.0 -> 9.16.11, and versions BIND 9.11.3-S1 -> 9.11.27-S1 and 9.16.8-S1 -> 9.16.11-S1 of BIND Supported Preview Edition. Also release versions 9.17.0 -> 9.17.1 of the BIND 9.17 development branch |
| CVE-2023-50868 | 7.5 | 0.13757 | 0.94084 | No | The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 5155 specification implies that an algorithm must perform thousands of iterations of a hash function in certain situations. |
| CVE-2023-50387 | 7.5 | 0.50801 | 0.97766 | No | Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records. |
Vulnerability description
Vulnerabilities found for Isc Bind 9.11.4-p2
Risk description
These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed "high" severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
We managed to detect a publicly accessible File Transfer Protocol (FTP) service. PORT STATE SERVICE VERSION 21/tcp open ftp Pure-FTPd
Vulnerability description
We found that the File Transfer Protocol (FTP) service is publicly accessible. The FTP enables client systems to connect to upload and download files. Nonetheless, FTP lacks encryption for the data exchanged between the server and the client, leaving all transferred data exposed in plaintext.
Risk description
Exposing this service online can enable attackers to execute man-in-the-middle attacks, capturing sensitive user credentials and the contents of files because FTP operates without encryption. The entirety of the communication between the client and the server remains unsecured in plaintext. This acquired information could further facilitate additional attacks within the network.
Recommendation
We recommend turning off FTP access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the FTP service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, utilizing SFTP (Secure File Transfer Protocol) is recommended as this protocol employs encryption to secure data transfers.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.virginradio.ro | TXT | Text record | "v=DMARC1; p=quarantine; rua=mailto:admin+dmarc@edi.ro; ruf=mailto:admin+forensics@edi.ro; fo=1; sp=reject" |
Vulnerability description
We found that the target uses p=quarantine in the DMARC policy. When a DMARC policy is set to p=quarantine, emails that fail DMARC validation are delivered but placed in the recipient’s spam or junk folder. Although it offers some protection, this policy is less strict than p=reject, which blocks such emails entirely.
Risk description
While emails failing DMARC validation are sent to the spam folder, users may still retrieve them from there, leading to a higher risk of phishing and spoofing attacks succeeding. Moreover, less strict enforcement may allow more fraudulent emails to reach user inboxes if misclassified.
Recommendation
We recommend considering moving to a stricter policy, such as p=reject, where emails that fail DMARC validation are completely rejected rather than delivered to spam folders. This reduces the risk of users interacting with potentially malicious emails.
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1296 | "v=DKIM1; k=rsa; g=*; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDoIWrEJTAwzczRd576Y+NBQOu8x38iWr4xNl1NKxUQKr6xwBa2tuWmMxwXnYyTddTz9pHt03gyrKBZ+NPHGRHqvc1HK3u8SHEepwENVI5Jd/6kWuy2F6i3FmAnYDmTnSrhewX8X2vc8bP0GM3s6VNkPWtO3Lx7n8zL4JplzzxNvwIDAQAB" |
Vulnerability description
We found that the DKIM record uses common selectors. The use of common DKIM selectors such as default, test, dkim, or mail may indicate a lack of proper customization or key management. Attackers often target domains using such selectors because they suggest that the domain is relying on default configurations, which could be less secure and easier to exploit. This can increase the risk of DKIM key exposure or misuse.
Risk description
Using a common DKIM selector makes it easier for attackers to predict and exploit email authentication weaknesses. Attackers may attempt to find corresponding DKIM keys or improperly managed records associated with common selectors. If a common selector is coupled with a weak key length or poor key management practices, it significantly increases the likelihood of email spoofing and phishing attacks.
Recommendation
We recommend using unique, customized selectors for each DKIM key to make it more difficult for attackers to predict and target the domain's DKIM records. Regularly rotate selectors and associated keys to further strengthen the security of your domain's email authentication infrastructure.
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 4.4 | 100% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| cPanel | Hosting panels |
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 |
|---|---|
| Basic | 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| virginradio.ro | SPF | Sender Policy Framework | "v=spf1 mx ip4:193.33.154.2 include:servers.mcsv.net -all" |
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Nginx | Web servers, Reverse proxies |
| OneTrust | Cookie compliance |
| OneSignal | Marketing automation, A/B Testing |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Facebook Pixel 2.9.252 | Analytics |
| Cxense | Personalisation, Segmentation |
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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1296 | "v=DKIM1; k=rsa; g=*; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDoIWrEJTAwzczRd576Y+NBQOu8x38iWr4xNl1NKxUQKr6xwBa2tuWmMxwXnYyTddTz9pHt03gyrKBZ+NPHGRHqvc1HK3u8SHEepwENVI5Jd/6kWuy2F6i3FmAnYDmTnSrhewX8X2vc8bP0GM3s6VNkPWtO3Lx7n8zL4JplzzxNvwIDAQAB" |
| k1 | rsa | 1296 | "k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;" |
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| virginradio.ro | A | IPv4 address | 185.90.50.130 |
| virginradio.ro | NS | Name server | ns1.edi.ro |
| virginradio.ro | NS | Name server | ns2.edi.ro |
| virginradio.ro | MX | Mail server | 10 mail.virginradio.ro |
| virginradio.ro | SOA | Start of Authority | ns1.edi.ro. hostmaster.edi.ro. 2025062401 3600 900 3600000 3600 |
| virginradio.ro | TXT | Text record | "_z51g6hgcy5d177x0g8kownpwkq00vln" |
| virginradio.ro | TXT | Text record | "google-site-verification=EoqNrmb1kpjWiXZAc13FdYLEYg6gMJSSsFtUQ7FqLt8" |
| virginradio.ro | SPF | Sender Policy Framework | "v=spf1 mx ip4:193.33.154.2 include:servers.mcsv.net -all" |
| _dmarc.virginradio.ro | TXT | Text record | "v=DMARC1; p=quarantine; rua=mailto:admin+dmarc@edi.ro; ruf=mailto:admin+forensics@edi.ro; fo=1; sp=reject" |
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.