Vulnerability Scan Result
| Title: | Apple MacBook Mac & Laptop Reparatur Service & Verkauf in Berlin |
| Description: | Apple MacBook Mac & Laptop Reparatur Service & Verkauf in Berlin - Kostenlose Diagnose, professionelle Reparaturen ✓ 030 640 81 944 |
| ip_address | 78.46.202.171 |
| country | DE  |
| network_name | Hetzner Online GMBH |
| asn | AS24940 |
21/tcp | ftp | ProFTPD - |
25/tcp | smtp | Postfix smtpd - |
53/tcp | domain | ISC BIND 9.16.22 |
80/tcp | http | Apache httpd - |
106/tcp | tcpwrapped | - - |
110/tcp | pop3 | Courier pop3d - |
143/tcp | imap | Courier Imapd - |
443/tcp | https | Apache httpd - |
465/tcp | smtp | Postfix smtpd - |
993/tcp | imap | Courier Imapd - |
995/tcp | pop3 | Courier pop3d - |
8443/tcp | https | sw-cp-server - |
| Software / Version | Category |
|---|---|
| a3 Lazy Load | WordPress plugins, Performance |
| Google PageSpeed 1.13.35.2 | Caching, Web server extensions, Performance |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.35.1 | JavaScript libraries |
| Apache HTTP Server | Web servers |
| jQuery 3.7.1 | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| SuperPWA | WordPress plugins |
| PWA | Miscellaneous |
| Priority Hints | Performance |
| WordPress | CMS, Blogs |
| reCAPTCHA | Security |
| HSTS | Security |
| RSS | Miscellaneous |
| WP Fastest Cache | WordPress plugins, Performance |
| Yoast SEO 24.4 | SEO, WordPress plugins |
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
| Software / Version | Category |
|---|---|
| a3 Lazy Load | WordPress plugins, Performance |
| Google PageSpeed 1.13.35.2 | Caching, Web server extensions, Performance |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.35.1 | JavaScript libraries |
| Apache HTTP Server | Web servers |
| jQuery 3.7.1 | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| SuperPWA | WordPress plugins |
| PWA | Miscellaneous |
| Priority Hints | Performance |
| WordPress | CMS, Blogs |
| reCAPTCHA | Security |
| HSTS | Security |
| RSS | Miscellaneous |
| WP Fastest Cache | WordPress plugins, Performance |
| Yoast SEO 24.4 | SEO, WordPress plugins |
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://www.macservice030.de/ | Response headers include the HTTP Content-Security-Policy security header with the following security issues: |
Vulnerability description
We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.
Risk description
For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.
Recommendation
Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2023-6516 | 7.5 | 0.00193 | 0.41431 | No | To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to clean up the database. It uses several methods, including some that are asynchronous: a small chunk of memory pointing to the cache element that can be cleaned up is first allocated and then queued for later processing. It was discovered that if the resolver is continuously processing query patterns triggering this type of cache-database maintenance, `named` may not be able to handle the cleanup events in a timely manner. This in turn enables the list of queued cleanup events to grow infinitely large over time, allowing the configured `max-cache-size` limit to be significantly exceeded. This issue affects BIND 9 versions 9.16.0 through 9.16.45 and 9.16.8-S1 through 9.16.45-S1. |
| CVE-2023-5679 | 7.5 | 0.00156 | 0.36901 | No | A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure during recursive resolution, when both of these features are enabled. This issue affects BIND 9 versions 9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.12-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1. |
| CVE-2023-5517 | 7.5 | 0.00156 | 0.36901 | No | A flaw in query-handling code can cause `named` to exit prematurely with an assertion failure when: - `nxdomain-redirect <domain>;` is configured, and - the resolver receives a PTR query for an RFC 1918 address that would normally result in an authoritative NXDOMAIN response. This issue affects BIND 9 versions 9.12.0 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.8-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1. |
| CVE-2023-50387 | 7.5 | 0.42223 | 0.97272 | 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. |
| CVE-2023-4408 | 7.5 | 0.00295 | 0.524 | No | The DNS message parsing code in `named` includes a section whose computational complexity is overly high. It does not cause problems for typical DNS traffic, but crafted queries and responses may cause excessive CPU load on the affected `named` instance by exploiting this flaw. This issue affects both authoritative servers and recursive resolvers. This issue affects BIND 9 versions 9.0.0 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.9.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1. |
Vulnerability description
Vulnerabilities found for Isc Bind 9.16.22
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 ProFTPD
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-10-15 02:30 EEST Nmap scan report for www.macservice030.de (78.46.202.171) Host is up (0.021s latency).
PORT STATE SERVICE VERSION 995/tcp open ssl/pop3 Courier pop3d |_pop3-capabilities: PIPELINING LOGIN-DELAY(10) LANG SASL(LOGIN PLAIN) IMPLEMENTATION(Courier Mail Server) UIDL APOP USER TOP UTF8(USER) Service Info: Host: localhost.localdomain
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 6.95 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 |
|---|---|
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Apache HTTP Server | Web servers |
| Yoast SEO 24.4 | SEO, WordPress plugins |
| SuperPWA | WordPress plugins |
| a3 Lazy Load | WordPress plugins, Performance |
| WP Fastest Cache | WordPress plugins, Performance |
| Twitter Emoji (Twemoji) | Font scripts |
| reCAPTCHA | Security |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| core-js 3.35.1 | JavaScript libraries |
| HSTS | Security |
| Google PageSpeed 1.13.35.2 | Caching, Web server extensions, Performance |
| PWA | 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
| Operating System | Accuracy |
|---|---|
| Linux 5.0 - 5.4 | 96% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Plesk | Hosting panels |
| Sentry | Issue trackers |
| Nginx | Web servers, Reverse proxies |
| RequireJS | JavaScript frameworks |
| Prototype | JavaScript frameworks |
| React | JavaScript frameworks |
| React Router 6 | JavaScript frameworks |
| core-js 3.38.1 | JavaScript libraries |
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.macservice030.de | A | IPv4 address | 78.46.202.171 |
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.