Vulnerability Scan Result
| Title: | No title found |
| Description: | No description found |
| ip_address | 78.47.98.59 |
| country | DE  |
| network_name | Hetzner Online GmbH |
| asn | AS24940 |
22/tcp | ssh | OpenSSH 9.6p1 Ubuntu 3ubuntu13.16 |
80/tcp | http | Golang net/http server - |
443/tcp | https | - - |
8000/tcp | http | nginx - |
| Software / Version | Category |
|---|---|
| core-js 3.48.0 | JavaScript libraries |
| HTTP/3 | Miscellaneous |
| Mantine | UI frameworks |
| PDF.js 5.5.207 | Miscellaneous |
| Material UI | UI frameworks |
| HeroUI | UI frameworks |
| Open Graph | Miscellaneous |
| PostHog | Analytics |
| React | JavaScript frameworks |
| React Router 7.13.2 | JavaScript frameworks |
| Stripe basil | Payment processors |
| PWA | Miscellaneous |
| HSTS | Security |
| TypeScript | Programming languages |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| core-js 3.48.0 | JavaScript libraries |
| HTTP/3 | Miscellaneous |
| Mantine | UI frameworks |
| PDF.js 5.5.207 | Miscellaneous |
| Material UI | UI frameworks |
| HeroUI | UI frameworks |
| Open Graph | Miscellaneous |
| PostHog | Analytics |
| React | JavaScript frameworks |
| React Router 7.13.2 | JavaScript frameworks |
| Stripe basil | Payment processors |
| PWA | Miscellaneous |
| HSTS | Security |
| TypeScript | Programming languages |
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.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
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.
Classification
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2026-07-02 18:21 EEST Nmap scan report for pdf.data-art.ch (78.47.98.59) Host is up (0.019s latency). rDNS record for 78.47.98.59: static.59.98.47.78.clients.your-server.de
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 9.6p1 Ubuntu 3ubuntu13.16 (Ubuntu Linux; protocol 2.0) | ssh-auth-methods: | Supported authentication methods: | publickey |_ password Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 0.75 seconds
Vulnerability description
We found that the SSH service with username/password authentication is publicly accessible. Network administrators often use remote administration protocols to control devices like switches, routers, and other essential systems. However, allowing these services to be accessible via the Internet can increase security risks, creating potential opportunities for attacks on the organization.
Risk description
Exposing this service online with username/password authentication can enable attackers to launch authentication attacks, like guessing login credentials, and potentially gaining unauthorized access. Vulnerabilities, such as unpatched software, protocol flaws, or backdoors could also be exploited. An example is the CVE-2024-3094 (XZ Utils Backdoor) vulnerability.
Recommendation
We recommend turning off SSH with username/password authentication access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the SSH service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, it is advisable to utilize SSH Public Key Authentication since it employs a key pair to verify the identity of a user or process.
Evidence
| Software / Version | Category |
|---|---|
| TypeScript | Programming languages |
| Material UI | UI frameworks |
| HeroUI | UI frameworks |
| Mantine | UI frameworks |
| React | JavaScript frameworks |
| Stripe basil | Payment processors |
| React Router 7.13.2 | JavaScript frameworks |
| HSTS | Security |
| HTTP/3 | Miscellaneous |
| PostHog | Analytics |
| core-js 3.48.0 | JavaScript libraries |
| PDF.js 5.5.207 | Miscellaneous |
| PWA | Miscellaneous |
| Open Graph | 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 |
|---|---|---|---|
| pdf.data-art.ch | A | IPv4 address | 78.47.98.59 |
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
| Software / Version | Category |
|---|---|
| PHP | Programming languages |
| Laravel | Web frameworks |
| Nginx | Web servers, Reverse proxies |
| Alpine.js 3.14.9 | JavaScript frameworks |
| Livewire | Web frameworks, Miscellaneous |
| Open Graph | 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 4.15 - 5.6 | 100% |
Vulnerability description
OS Detection