Vulnerability Scan Result
| Title: | Startseite - Megger Service Excellence |
| Description: | No description found |
| ip_address | 185.66.108.54 |
| country | CH  |
| network_name | Zettaplan Ag |
| asn | AS200713 |
21/tcp | ftp | Microsoft ftpd - |
25/tcp | smtp | MailEnable smptd 10.53-- |
80/tcp | http | Microsoft IIS httpd 10 |
110/tcp | pop3 | MailEnable POP3 Server - |
135/tcp | msrpc | Microsoft Windows RPC - |
443/tcp | https | Microsoft IIS httpd 10 |
465/tcp | smtp | MailEnable smptd 10.53-- |
995/tcp | pop3 | MailEnable POP3 Server - |
1433/tcp | ms-sql-s | Microsoft SQL Server 2019 15.00.2000 |
3306/tcp | mysql | MySQL 5.5.5-10.6.22-MariaDB |
3389/tcp | ms-wbt-server | Microsoft Terminal Services - |
8443/tcp | https | Microsoft IIS httpd 10 |
| Software / Version | Category |
|---|---|
| cdnjs | CDN |
| jQuery CDN | CDN |
| Font Awesome | Font scripts |
| Adobe Fonts | Font scripts |
| Bootstrap 4.5.2 | UI frameworks |
| jQuery 3.5.1 | JavaScript libraries |
| Windows Server | Operating systems |
| Popper 1.14.7 | Miscellaneous |
| Swiper | JavaScript libraries |
| Typekit | Font scripts |
| Microsoft ASP.NET | Web frameworks |
| Cloudflare | CDN |
| IIS 10.0 | Web servers |
| Plesk | Hosting panels |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.megger-service-excellence.com/ | .AspNetCore.Antiforgery.RqDzPpLm4HY | Set-Cookie: .AspNetCore.Antiforgery.RqDzPpLm4HY=CfDJ8LyXaiPyMnVAhFqWaN7OnhztGe8J9cf5QhyB4KBkhU1KALfJuKEL4qARWj_2v6FIjfsGbpKm2OP7Rz4WZT901ZGcFOSPyNWqCh3HWpWuiR1XgnxM9oMZd6Hq-_96Y-_vgqTG4ynN9TK9MSCe5jex3qE |
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 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.megger-service-excellence.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
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
| Software / Version | Category |
|---|---|
| cdnjs | CDN |
| jQuery CDN | CDN |
| Font Awesome | Font scripts |
| Adobe Fonts | Font scripts |
| Bootstrap 4.5.2 | UI frameworks |
| jQuery 3.5.1 | JavaScript libraries |
| Windows Server | Operating systems |
| Popper 1.14.7 | Miscellaneous |
| Swiper | JavaScript libraries |
| Typekit | Font scripts |
| Microsoft ASP.NET | Web frameworks |
| Cloudflare | CDN |
| IIS 10.0 | Web servers |
| Plesk | Hosting panels |
| 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.
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.
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.megger-service-excellence.com/ | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 | Email Address: service.aachen@megger.com |
Vulnerability description
We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.
Risk description
The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.
Recommendation
Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
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 managed to detect a publicly accessible MySQL service. PORT STATE SERVICE VERSION 3306/tcp open mysql MySQL 5.5.5-10.6.22-MariaDB
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.
Risk description
The risk exists that an attacker exploits this issue by launching a password-based attack on the MySQL service. Furthermore, they could exploit zero-day vulnerabilities to obtain remote access to the MySQL database server, thereby gaining complete control over its operating system and associated services. Such an attack could lead to the exposure of confidential or sensitive information.
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
We managed to detect a publicly accessible Windows Microsoft SQL Server (MSSQL) service. PORT STATE SERVICE VERSION 1433/tcp open ms-sql-s Microsoft SQL Server 2019 15.00.2000
Vulnerability description
We found that the Microsoft SQL Server (MSSQL) is publicly accessible. This service often holds critical organizational data, making it a potential prime target for determined attackers.
Risk description
The risk exists that an attacker exploits this issue by launching a password-based attack on the MSSQL service. If an attacker identifies a correct set of login details, they could gain access to the database and start enumerating, potentially revealing confidential information. Moreover, such vulnerabilities could lead to other forms of attacks, including privilege escalation, allowing attackers to run system commands and move laterally to other systems in the internal network.
Recommendation
We recommend ensuring that the Microsoft SQL Server (MSSQL) service is not publicly accessible. The MSSQL service should be safeguarded behind a firewall or made available only to users connected through a Virtual Private Network (VPN) server. However, if the MSSQL service is required to be directly accessible over the Internet, we recommend reconfiguring it such that it is accessible only from known IP addresses.
Evidence
We managed to detect a publicly accessible Remote Procedure Call (RPC) service. PORT STATE SERVICE VERSION 135/tcp open msrpc Microsoft Windows RPC
Vulnerability description
We found that the Windows Remote Procedure Call (RPC) service is publicly accessible. RPC is a protocol that one program can use to request a service from a program located on another computer in a network.
Risk description
Exposing this service online can enable attackers to launch attacks, including unauthorized access, remote code execution, information disclosure, denial of service (DoS), and potential lateral movement within the network.
Recommendation
We recommend turning off RPC access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the RPC service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall.
Evidence
We managed to detect that MySQL has reached the End-of-Life (EOL).
Version detected: 5.5.5-10.6.22-mariadb End-of-life date: 2018-12-31 Latest version for the cycle: 5.5.63 This release cycle (5.5) doesn't have long-term-support (LTS). The cycle was released on 2010-12-03 and its latest release date was 2018-12-21. The support ended on 2015-12-31.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
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
We managed to detect a publicly accessible Post Office Protocol (POP3) service. Starting Nmap ( https://nmap.org ) at 2025-11-19 11:42 EET Nmap scan report for www.megger-service-excellence.com (185.66.108.54) Host is up (0.018s latency). rDNS record for 185.66.108.54: s2079.rootserver.io
PORT STATE SERVICE VERSION 995/tcp open ssl/pop3 MailEnable POP3 Server |_pop3-capabilities: USER TOP UIDL Service Info: OS: Windows; CPE: cpe:/o:microsoft:windows
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 7.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.
Risk description
Exposing this service online can enable attackers to conduct man-in-the-middle attacks, thereby gaining access to sensitive user credentials and the contents of emails. Given that POP3 operates via a plaintext protocol, the entirety of the data exchanged between the client and server is left unencrypted. This critical information could then be leveraged in further attacks on the organization's network.
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
We managed to detect that Bootstrap has reached the End-of-Life (EOL).
Version detected: 4.5.0 End-of-life date: 2023-01-01 Latest version for the cycle: 4.6.2 This release cycle (4) does have long-term-support (LTS). The cycle was released on 2018-01-18 and its latest release date was 2022-07-19. The support ended on 2021-11-01.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
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
We managed to detect a publicly accessible File Transfer Protocol (FTP) service. PORT STATE SERVICE VERSION 21/tcp open ftp Microsoft 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
We managed to detect a publicly accessible Post Office Protocol (POP3) service. Starting Nmap ( https://nmap.org ) at 2025-11-19 11:42 EET Nmap scan report for www.megger-service-excellence.com (185.66.108.54) Host is up (0.018s latency). rDNS record for 185.66.108.54: s2079.rootserver.io
PORT STATE SERVICE VERSION 110/tcp open pop3 MailEnable POP3 Server |_pop3-capabilities: UIDL TOP USER Service Info: OS: Windows; CPE: cpe:/o:microsoft:windows
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 0.91 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.
Risk description
Exposing this service online can enable attackers to conduct man-in-the-middle attacks, thereby gaining access to sensitive user credentials and the contents of emails. Given that POP3 operates via a plaintext protocol, the entirety of the data exchanged between the client and server is left unencrypted. This critical information could then be leveraged in further attacks on the organization's network.
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
| Software / Version | Category |
|---|---|
| Plesk | Hosting panels |
| Windows Server | Operating systems |
| Microsoft ASP.NET | Web frameworks |
| RequireJS | JavaScript frameworks |
| Prototype | JavaScript frameworks |
| IIS 10.0 | Web servers |
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
| Operating System | Accuracy |
|---|---|
| Microsoft Windows XP SP3 | 85% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Plesk | Hosting panels |
| Windows Server | Operating systems |
| Microsoft ASP.NET | Web frameworks |
| Bootstrap 4.5.0 | UI frameworks |
| IIS 10.0 | Web servers |
| Typekit | Font scripts |
| jQuery 3.5.1 | JavaScript libraries |
| Adobe Fonts | Font scripts |
| HSTS | Security |
| Cloudflare | CDN |
| jQuery CDN | CDN |
| Font Awesome | Font scripts |
| cdnjs | CDN |
| Popper 1.14.7 | 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 |
|---|---|---|---|
| www.megger-service-excellence.com | A | IPv4 address | 185.66.108.54 |
| www.megger-service-excellence.com | NS | Name server | ns01.hostfactory.ch |
| www.megger-service-excellence.com | NS | Name server | ns02.hostfactory.ch |
| www.megger-service-excellence.com | MX | Mail server | 10 mx1.hostfactory.ch |
| www.megger-service-excellence.com | MX | Mail server | 40 mx4.hostfactory.swiss |
| www.megger-service-excellence.com | MX | Mail server | 30 mx3.hostfactory.ch |
| www.megger-service-excellence.com | MX | Mail server | 20 mx2.hostfactory.swiss |
| www.megger-service-excellence.com | SOA | Start of Authority | ns01.hostfactory.ch. jonas_knaus.hotmail.com. 2024052401 7200 7200 1209600 7200 |
| www.megger-service-excellence.com | SPF | Sender Policy Framework | "v=spf1 a:spf.hostfactory.ch -all" |
| www.megger-service-excellence.com | CNAME | Canonical name | megger-service-excellence.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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.megger-service-excellence.com | SPF | Sender Policy Framework | "v=spf1 a:spf.hostfactory.ch -all" |