Vulnerability Scan Result
| Title: | Vortex - A Modern and Secure Messaging Platform for Schools |
| Description: | A modern messaging platform for school: Earn XP, level up, meet people, and join communities! |
| ip_address | 104.36.84.146 |
| country | US  |
| network_name | Redoubt Networks |
| asn | AS400304 |
22/tcp | ssh | OpenSSH 9.6p1 Ubuntu 3ubuntu13.16 |
80/tcp | http | Caddy httpd - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| cdnjs | CDN |
| Firebase 11.9.1 | Databases, Development |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| DoubleClick Floodlight | Advertising |
| Three.js 134 | JavaScript graphics |
| PWA | Miscellaneous |
| WordPress | CMS, Blogs |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| jsDelivr | CDN |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://kxjbldbeta.qhrk0pr.104.36.84.146.sslip.io/ | 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-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| cdnjs | CDN |
| Firebase 11.9.1 | Databases, Development |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| DoubleClick Floodlight | Advertising |
| Three.js 134 | JavaScript graphics |
| PWA | Miscellaneous |
| WordPress | CMS, Blogs |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| 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.
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-06-30 00:36 EEST Nmap scan report for kxjbldbeta.qhrk0pr.104.36.84.146.sslip.io (104.36.84.146) Host is up (0.14s latency). rDNS record for 104.36.84.146: 146.84.36.104.crunchbits.us
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 1.96 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 found insecure EDNS configuration on the following nameservers: ns-ovh.sslip.io, ns-00.nip.io, ns-01.nip.io ns-ovh.sslip.io:
ns-00.nip.io:
ns-01.nip.io:
Vulnerability description
We found that the server does not properly implement EDNS (Extension Mechanisms for DNS). EDNS allows larger DNS packets and supports modern features such as DNSSEC.
Risk description
The risk exists because improper or missing EDNS support can lead to truncated responses, degraded DNS performance, and compatibility issues with DNSSEC. This exposes users to risks such as incomplete DNS resolution and failed DNSSEC validation.
Recommendation
We recommend ensuring the proper implementation of EDNS on the DNS server. Update the DNS server software to support EDNS fully, including modern features like DNSSEC. Regularly test DNS configurations to ensure compliance and performance.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns-ovh.sslip.io, ns-00.nip.io, ns-01.nip.io
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| Firebase 11.9.1 | Databases, Development |
| MySQL | Databases |
| PHP | Programming languages |
| Three.js 134 | JavaScript graphics |
| Cloudflare | CDN |
| Google Font API | Font scripts |
| jsDelivr | CDN |
| cdnjs | CDN |
| Google Tag Manager | Tag managers |
| DoubleClick Floodlight | Advertising |
| HSTS | Security |
| Open Graph | Miscellaneous |
| PWA | Miscellaneous |
| HTTP/3 | 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 |
|---|---|---|---|
| kxjbldbeta.qhrk0pr.104.36.84.146.sslip.io | A | IPv4 address | 104.36.84.146 |
| kxjbldbeta.qhrk0pr.104.36.84.146.sslip.io | NS | Name server | ns-ovh.sslip.io |
| kxjbldbeta.qhrk0pr.104.36.84.146.sslip.io | NS | Name server | ns-00.nip.io |
| kxjbldbeta.qhrk0pr.104.36.84.146.sslip.io | NS | Name server | ns-01.nip.io |
| kxjbldbeta.qhrk0pr.104.36.84.146.sslip.io | MX | Mail server | 0 kxjbldbeta.qhrk0pr.104.36.84.146.sslip.io |
| kxjbldbeta.qhrk0pr.104.36.84.146.sslip.io | SOA | Start of Authority | kxjbldbeta.qhrk0pr.104.36.84.146.sslip.io. briancunnie.gmail.com. 20260516 900 900 1800 180 |
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 | 96% |
Vulnerability description
OS Detection