Vulnerability Scan Result
| Title: | Login – Nextcloud |
| Description: | No description found |
| ip_address | 5.78.130.151 |
| country | US  |
| network_name | Hetzner Online GMBH |
| asn | AS212317 |
22/tcp | ssh | OpenSSH 8.9p1 Ubuntu 3ubuntu0.13 |
80/tcp | http | Golang net/http server - |
443/tcp | https | Golang net/http server - |
8080/tcp | https | Golang net/http server - |
8443/tcp | https-alt | - - |
| Software / Version | Category |
|---|---|
| Backbone.js 1.6.0 | JavaScript frameworks |
| Debian | Operating systems |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.37.0 | JavaScript libraries |
| Handlebars 4.7.8 | JavaScript frameworks |
| Apache HTTP Server 2.4.62 | Web servers |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.3 | JavaScript libraries |
| Moment.js 2.30.1 | JavaScript libraries |
| ownCloud | Miscellaneous |
| PHP 8.2.27 | Programming languages |
| Select2 | JavaScript libraries |
| Underscore.js | JavaScript libraries |
| PWA | Miscellaneous |
| Lodash 1.13.6 | JavaScript libraries |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://cloud.neospend.com/login | oc3icsuskabj, oc_sessionPassphrase, nc_sameSiteCookielax, nc_sameSiteCookiestrict | Set-Cookie: oc3icsuskabj=85a7108c3d844bfe52515bdec9e3e45c Set-Cookie: oc_sessionPassphrase=npcASG40WBzB5MQkDNUXi7CkOR6QhF%2BEsdPr9i9QraXQSSQYyRY04%2FePixLC5oLfuyig5IEPCNbhpzYLDrw4i7swSXaj2z0GrAA2yLjPZ5A8REz7xyyVjwsGib0rRPt1 Set-Cookie: nc_sameSiteCookielax=true Set-Cookie: nc_sameSiteCookiestrict=true |
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://cloud.neospend.com/login | 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
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 |
|---|---|
| Backbone.js 1.6.0 | JavaScript frameworks |
| Debian | Operating systems |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.37.0 | JavaScript libraries |
| Handlebars 4.7.8 | JavaScript frameworks |
| Apache HTTP Server 2.4.62 | Web servers |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.3 | JavaScript libraries |
| Moment.js 2.30.1 | JavaScript libraries |
| ownCloud | Miscellaneous |
| PHP 8.2.27 | Programming languages |
| Select2 | JavaScript libraries |
| Underscore.js | JavaScript libraries |
| PWA | Miscellaneous |
| Lodash 1.13.6 | 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
| URL | Evidence |
|---|---|
| https://cloud.neospend.com/login | 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.
Risk description
The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).
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 | |
| OWASP Top 10 - 2021 |
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2025-07-18 17:19 EEST Nmap scan report for cloud.neospend.com (5.78.130.151) Host is up (0.16s latency). rDNS record for 5.78.130.151: static.151.130.78.5.clients.your-server.de
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 8.9p1 Ubuntu 3ubuntu0.13 (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 2.27 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 |
|---|---|
| PHP 8.2.27 | Programming languages |
| Debian | Operating systems |
| Apache HTTP Server 2.4.62 | 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 |
|---|---|
| Linux 4.15 - 5.6 | 100% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| cloud.neospend.com | A | IPv4 address | 5.78.130.151 |
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.