Vulnerability Scan Result
IP address | 75.102.22.38 |
Country | US |
AS number | AS23352 |
Net name | Server Central Network |
21/tcp | ftp | Pure-FTPd |
25/tcp | smtp | |
53/tcp | domain | PowerDNS Authoritative Server 4.9.1 |
80/tcp | http | |
110/tcp | pop3 | Dovecot pop3d |
143/tcp | imap | Dovecot imapd |
443/tcp | https | |
465/tcp | smtp | Exim smtpd 4.96.2 |
587/tcp | smtp | Exim smtpd 4.96.2 |
993/tcp | imap | Dovecot imapd |
995/tcp | pop3 | Dovecot pop3d |
3306/tcp | mysql | MySQL 5.5.5-10.6.20-MariaDB-cll-lve |
8888/tcp | sun-answerbook |
Software / Version | Category |
---|---|
Imunify360 1.21 | Security |
Web Application Vulnerabilities
Evidence
URL | Evidence |
---|---|
https://nubeamarilla.com/ | Response headers do not include the X-Content-Type-Options HTTP security header |
Vulnerability description
We noticed that the target application's server responses lack the <code>X-Content-Type-Options</code> header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.
Recommendation
We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.
Classification
CWE | CWE-693 |
OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
URL | Evidence |
---|---|
https://nubeamarilla.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.
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 | A6 - Security Misconfiguration |
OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
URL | Evidence |
---|---|
https://nubeamarilla.com/ | Response headers do not include the Referrer-Policy HTTP security header as well as the <meta> tag with name 'referrer' is not present in the response. |
Vulnerability description
We noticed that the target application's server responses lack the <code>Referrer-Policy</code> HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.
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
URL | Evidence |
---|---|
https://nubeamarilla.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.
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
Software / Version | Category |
---|---|
Imunify360 1.21 | 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.
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 |
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
PORT STATE SERVICE VERSION
3306/tcp open mysql MySQL 5.5.5-10.6.20-MariaDB-cll-lve
Vulnerability description
We identified that the MySQL service is publicly accessible. MySQL serves as a common database for numerous web applications and services for data storage, making it a potential prime target for determined attackers.
Recommendation
We recommend turning off public Internet access to MySQL and opting for a Virtual Private Network (VPN) that enforces two-factor authentication (2FA). Avoid enabling direct user authentication to the MySQL service via the Internet, as this could enable attackers to engage in password-guessing and potentially initiate attacks leading to complete control. However, if the MySQL service is required to be directly accessible over the Internet, we recommend reconfiguring it to be accessible only from known IP addresses.
Evidence
Risk level | CVSS | CVE | Summary | Exploit |
---|---|---|---|---|
4.3 | CVE-2018-14040 | In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute. | N/A | |
4.3 | CVE-2018-14042 | In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip. | N/A | |
4.3 | CVE-2016-10735 | In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute, a different vulnerability than CVE-2018-14041. | N/A | |
4.3 | CVE-2018-20676 | In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute. | N/A | |
4.3 | CVE-2018-20677 | In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property. | N/A |
Vulnerability description
Vulnerabilities found for Bootstrap 3.3.7
Recommendation
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
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.
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.
Starting Nmap ( https://nmap.org ) at 2025-01-21 10:17 EET
Nmap scan report for nubeamarilla.com (75.102.22.38)
Host is up (0.12s latency).
rDNS record for 75.102.22.38: bh8924.banahosting.com
PORT STATE SERVICE VERSION
995/tcp open ssl/pop3 Dovecot pop3d
|_pop3-capabilities: RESP-CODES UIDL CAPA SASL(PLAIN LOGIN) PIPELINING AUTH-RESP-CODE USER TOP
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 8.29 seconds
Vulnerability description
We found that the Post Office Protocol (POP3) service is publicly accessible and doesn’t include STARTTLS capability. Email clients use the Post Office Protocol (POP) to download emails for user accounts. Some POP servers are initially set up to operate over an unsecured protocol. When email clients download email content through this plaintext protocol, it can pose a substantial risk to the organization's network, especially depending on which user account is set to receive the emails.
Recommendation
We recommend turning off POP3 access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the POP3 service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, activating STARTTLS capability (switching the connection to a secure communication) or utilizing Secure POP3 (POP3S) is recommended, as this protocol employs encryption.
Evidence
Domain Queried | DNS Record Type | Description | Value |
---|---|---|---|
nubeamarilla.com | SPF | Sender Policy Framework | "v=spf1 ip4:75.102.22.34 +a +mx include:relay.mailchannels.net ~all" |
Vulnerability description
We found that the Sender Policy Framework (SPF) record for the domain is configured with ~all (soft fail), which indicates that emails from unauthorized IP addresses are not explicitly denied. Instead, the recipient mail server is instructed to treat these messages with suspicion but may still accept them. This configuration may not provide enough protection against email spoofing and unauthorized email delivery, leaving the domain more vulnerable to impersonation attempts.
Recommendation
We recommend changing the SPF record's ~all (soft fail) directive to -all (hard fail). The -all setting tells recipient mail servers to reject emails from any IP addresses not listed in the SPF record, providing stronger protection against email spoofing. Ensure that all legitimate IP addresses and services that send emails on behalf of your domain are properly included in the SPF record before implementing this change.
Evidence
Domain Queried | DNS Record Type | Description | Value |
---|---|---|---|
nubeamarilla.com | TXT | Text record | "google-site-verification=ovCf2DENF90axjBjtHl9JVLxfLJ7MQ9gDOQraCNfgLo" |
Vulnerability description
We found that the target server has no DMARC policy configured. A missing DMARC (Domain-based Message Authentication, Reporting, and Conformance) policy means that the domain is not enforcing any DMARC policies to protect against email spoofing and phishing attacks. Without DMARC, even if SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail) are configured, there is no mechanism to tell receiving email servers how to handle messages that fail authentication. This leaves the domain vulnerable to abuse, such as email spoofing and impersonation.
Recommendation
We recommend implementing a DMARC policy for your domain. Start by configuring a DMARC record with a policy of p=none, which will allow you to monitor email flows without impacting legitimate emails. This initial setup helps identify how emails from your domain are being processed by recipient servers. Once you’ve verified that legitimate emails are passing SPF and DKIM checks, you can gradually enforce stricter policies like p=quarantine or p=reject to protect against spoofing and phishing attacks. Additionally, include rua and ruf email addresses in the DMARC record to receive aggregate and forensic reports. These reports will provide valuable insights into authentication failures and help you detect any spoofing attempts.
Evidence
DKIM selector | Key type | Key size | Value |
---|---|---|---|
default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAr0ULYluw9lV0sYbol99+yemONtlmDL8vWJV3F7cVKdpEkIfaJRgmDYPN6ieC8zOmqopFzMC7GiTZwAQU4z3mXMA+BfoXrxYj8nN6NKyBcOrDMeLtY9PRSdwZkUl4U5EyTuOcXWjIoBBO9PpwzZII8AHE4ELweAAes7/G18+K8BDe2fu/YdiI5myRuay8Falvd" "996rIexiVsvL59lv9nmK019Dt+3eNU296y3HjcydXDbJTl2V5ojCpd+KRByCOj2RimnLPo4eccX3fKaibJusRUzCD8G4NP3FroJORofOANbVkt7OG0NJAAGJmLScYKdNzUxgRy7K6HuXQ93aFwwYQIDAQAB;" |
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.
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.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
Domain Queried | DNS Record Type | Description | Value |
---|---|---|---|
nubeamarilla.com | A | IPv4 address | 75.102.22.38 |
nubeamarilla.com | NS | Name server | ns8925.banahosting.com |
nubeamarilla.com | NS | Name server | ns8924.banahosting.com |
nubeamarilla.com | MX | Mail server | 0 nubeamarilla.com |
nubeamarilla.com | SOA | Start of Authority | ns8924.banahosting.com. support.banahosting.com. 2025012102 86400 7200 1600000 86400 |
nubeamarilla.com | TXT | Text record | "google-site-verification=ovCf2DENF90axjBjtHl9JVLxfLJ7MQ9gDOQraCNfgLo" |
nubeamarilla.com | SPF | Sender Policy Framework | "v=spf1 ip4:75.102.22.34 +a +mx include:relay.mailchannels.net ~all" |
Recommendation
We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.
Evidence
Operating System |
---|
Linux 4.4 |
Vulnerability description
OS Detection
Evidence
DKIM selector | Key type | Key size | Value |
---|---|---|---|
default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAr0ULYluw9lV0sYbol99+yemONtlmDL8vWJV3F7cVKdpEkIfaJRgmDYPN6ieC8zOmqopFzMC7GiTZwAQU4z3mXMA+BfoXrxYj8nN6NKyBcOrDMeLtY9PRSdwZkUl4U5EyTuOcXWjIoBBO9PpwzZII8AHE4ELweAAes7/G18+K8BDe2fu/YdiI5myRuay8Falvd" "996rIexiVsvL59lv9nmK019Dt+3eNU296y3HjcydXDbJTl2V5ojCpd+KRByCOj2RimnLPo4eccX3fKaibJusRUzCD8G4NP3FroJORofOANbVkt7OG0NJAAGJmLScYKdNzUxgRy7K6HuXQ93aFwwYQIDAQAB;" |
Evidence
Software / Version | Category |
---|---|
Bootstrap 3.3.7 | UI frameworks |
reCAPTCHA | 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.
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.