Vulnerability Scan Result
| Title: | Login | BoniCloud |
| Description: |
| ip_address | 193.142.41.53 |
| country | DE  |
| network_name | IP-Projects GmbH & Co. KG |
| asn | AS48314 |
21/tcp | ftp | ProFTPD - |
22/tcp | ssh | OpenSSH 9.2p1 Debian 2+deb12u7 |
| Software / Version | Category |
|---|---|
| Google Font API | Font scripts |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| PHP 8.4.17 | Programming languages |
| spin.js | JavaScript graphics |
| SweetAlert2 11 | JavaScript libraries |
| jsDelivr | CDN |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.my.bonicloud.de/auth | fuelcid | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: fuelcid=S%3A1Yb27s6hJ3sIi1eSpHGOV7y4A0AwEfouUmWXaLu-1kt6z2U-YqCkp3B-oyijNyidFRFEPqSv3cKWOjnhjH4GVuQaxhzBXuCmnoj6yP334EqQDJckZjEVBlarOHcOklUVZpj3Lm3CB0VsauoJ6uwQ6R7rG1YMmONpOtJDYuDNkoDwnUtV9RIZSr0DNmfiiJZi6FRgTMhKSwBdkDzyNxtvMcWqirVThyAOJVY2r8uiSKnM1uB3gfFwmKRqDv8q9Q2IZx5l915qEZQHqCuNSip-x_UgUKkh0AMXdpAHbbSU-Jb4Ibyu5hPITfAegCC3nGz23zHgnCxVl2aVi8Qmnxu5pAklt7pdlvlm5C-tsAQHHDlaz5cmaqZtW92AOXigbVsO8dDRIpUsIqvIW16nNmXhq_CWXX7oah8vHGSNxkYxHXhCrFJha9R3luE1yxtH7FIkO5S8-8HLxY9DzY1URuEvs292WtBtIY0XN_e_6hL0yQXKiXzqV9sZRos-fkf-KA5iBYV58ZJ4iVG716f4YMd9XqPfz85gaUgMomlMURO5jBdv_U4Dz5UHXcuGiYiMPePUier24YGHMOde5mvc1c_1SyUQLDciHr9iXe_fm0Vl2ZzPAeh13oRX1bAkuckXOnN3sg%3D%3D |
Vulnerability description
We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
| CWE | CWE-1004 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.my.bonicloud.de/auth | 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 | The following form sends inputs of type password plainly in the URL: ` |
| https://www.my.bonicloud.de/auth | GET | Query: password=Secure123456$ username=1d3d2d231d2dd4 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 Cookies: fuelcid=S%3ACnGefDpnPzT3IWjBDACSjeiKKQqPeOXjeqQSUYkPgkD0tuqw54KQ4lIr1OlYhXKhco7SI... | The following form sends inputs of type password plainly in the URL: ` |
Vulnerability description
We found a form which is submitted using a GET method and has inputs of the type password. The end result is that passwords are submitted in URLs.
Risk description
Passwords submitted in URLs have a higher chance of being leaked. The main reason is that URLs can be leaked in browser cross-site requests via the Referer header. Additionally, URLs are usually stored in all kinds of logs. If any access or error logs of the server were publicly accessible, an attacker could also harvest password from it.
Recommendation
You should submit passwords using POST rather than GET. This way sensitive data won't be shared to other locations via URLs.
Evidence
| URL | Evidence |
|---|---|
| https://www.my.bonicloud.de/auth | 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 |
|---|---|
| Google Font API | Font scripts |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| PHP 8.4.17 | Programming languages |
| spin.js | JavaScript graphics |
| SweetAlert2 11 | JavaScript libraries |
| jsDelivr | CDN |
| 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.
Evidence
| URL | Evidence |
|---|---|
| https://www.my.bonicloud.de/auth |
|
Vulnerability description
We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.
Risk description
The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.
Recommendation
Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2026-01-29 05:01 EET Nmap scan report for www.my.bonicloud.de (193.142.41.53) Host is up (0.014s latency). rDNS record for 193.142.41.53: mail.bonicloud.de
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 9.2p1 Debian 2+deb12u7 (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.84 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
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.my.bonicloud.de | A | IPv4 address | 193.142.41.53 |
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
| Operating System | Accuracy |
|---|---|
| Linux 5.0 - 5.4 | 100% |
Vulnerability description
OS Detection