Vulnerability Scan Result
| Title: | Essential Prepper Gear for Survival Preparedness |
| Description: | Discover essential gear for preparedness and survival. Equip yourself with top-quality supplies that ensure you're ready for any emergency situation. |
| ip_address | 84.17.59.115 |
| country | IT  |
| network_name | Datacamp Limited |
| asn | AS60068 |
22/tcp | ssh | OpenSSH 9.6p1 |
80/tcp | http | nginx - |
443/tcp | https | nginx - |
6000/tcp | http | nginx - |
6001/tcp | http | nginx - |
7000/tcp | http | nginx - |
7001/tcp | http | nginx - |
| Software / Version | Category |
|---|---|
| Alpine.js | JavaScript frameworks |
| Bunny | CDN |
| Bunny Fonts | Font scripts |
| Livewire | Web frameworks, Miscellaneous |
| Laravel | Web frameworks |
| PHP | Programming languages |
| PWA | Miscellaneous |
| HSTS | Security |
| RSS | Miscellaneous |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Alpine.js | JavaScript frameworks |
| Bunny | CDN |
| Bunny Fonts | Font scripts |
| Livewire | Web frameworks, Miscellaneous |
| Laravel | Web frameworks |
| PHP | Programming languages |
| PWA | Miscellaneous |
| HSTS | Security |
| RSS | 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.
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
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://survival-prepper-depot.goshoptechnology.com/our-newsletter | POST | Body: email=example_email@example.com message_field_N00gYjGjjp2kvQmm=1d3d2d231d2dd4 opal_three_ingrain=eyJpdiI6IkhnRXdCWmF0ZEJwYTU3a1RBM2J5ZUE9PSIsInZhbHVlIjoiRXYzYkk1eEpBNmRoVCtSVlVqM0Vwdz09IiwibWFjIjoiYmVkZjc3M2MyMjhlNWRmYjk3MjY1NGZkNDYzODI5NGRhYTgzODZhMmIzMzVmMDAxODMzNWYwZmI2OWJlMzk5MiI... | Response has an internal server error status code: 500 |
Vulnerability description
We noticed that the target application's website does not properly handle or incorrectly manages exceptional conditions like Internal Server Errors. These errors can reveal sensitive information through their error messages. For instance, an error message could inadvertently disclose system paths or private application details.
Risk description
The risk exists that attackers could utilize information revealed in Internal Server Error messages to mount more targeted and effective attacks. Detailed error messages could, for example, expose a path traversal weakness (CWE-22) or other exploitable system vulnerabilities.
Recommendation
Ensure that error messages only contain minimal details that are useful to the intended audience, and nobody else. The messages need to strike the balance between being too cryptic and not being cryptic enough. They should not necessarily reveal the methods that were used to determine the error. Such detailed information can be used to refine the original attack to increase the chances of success. If errors must be tracked in some detail, capture them in log messages - but consider what could occur if the log messages can be viewed by attackers. Avoid recording highly sensitive information such as passwords in any form. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a username is valid or not.
Classification
| CWE | CWE-209 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://survival-prepper-depot.goshoptechnology.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
Website is accessible.
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.
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2025-08-18 01:48 EEST Nmap scan report for survival-prepper-depot.goshoptechnology.com (84.17.59.115) Host is up (0.00047s latency). rDNS record for 84.17.59.115: 84-17-59-115.bunnyinfra.net
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 9.6p1 (protocol 2.0) | ssh-auth-methods: | Supported authentication methods: | publickey |_ password
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 0.88 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 |
|---|---|
| Nginx | Web servers, Reverse proxies |
| Bunny | CDN |
| Bunny Fonts | Font scripts |
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
| Software / Version | Category |
|---|---|
| PHP | Programming languages |
| Laravel | Web frameworks |
| Alpine.js 3.14.9 | JavaScript frameworks |
| Matomo Analytics | Analytics |
| Lodash 4.17.21 | JavaScript libraries |
| Axios | JavaScript libraries |
| HSTS | Security |
| Bunny | CDN |
| Livewire | Web frameworks, Miscellaneous |
| RSS | Miscellaneous |
| 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 2.6.32 | 94% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Nginx | Web servers, Reverse proxies |
| Bunny | CDN |
| Bunny Fonts | Font scripts |
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
| Software / Version | Category |
|---|---|
| PHP | Programming languages |
| Laravel | Web frameworks |
| Alpine.js | JavaScript frameworks |
| HSTS | Security |
| Bunny | CDN |
| Livewire | Web frameworks, Miscellaneous |
| Bunny Fonts | Font scripts |
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
| Software / Version | Category |
|---|---|
| Nginx | Web servers, Reverse proxies |
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 |
|---|---|---|---|
| survival-prepper-depot.goshoptechnology.com | A | IPv4 address | 84.17.59.115 |
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.