Vulnerability Scan Result

Target:

http://mail.discordultimate.com/ (redirect)

Scanned target: https://mail.discordultimate.com/

Submitted: Jun 14, 2025 from DK

Public Scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

Title:	Mail UI
Description:	No description found

IP Information

ip_address	47.229.45.11
country	US
network_name	Charter Communications
asn	AS20115

Open Ports

22/tcp	ssh	OpenSSH 9.6p1 Ubuntu 3ubuntu13.11
25/tcp	smtp	Postfix smtpd -
80/tcp	http	Apache httpd 2.4.58
143/tcp	imap	Dovecot imapd -
443/tcp	https	Apache httpd 2.4.58
465/tcp	smtp	Postfix smtpd -
587/tcp	smtp	Postfix smtpd -

Web Technologies

Software / Version	Category
DataTables 1.13.1	JavaScript libraries
jQuery 3.6.0	JavaScript libraries
Nginx	Web servers, Reverse proxies
PHP	Programming languages
Chart.js	JavaScript graphics
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://mail.discordultimate.com/	PHPSESSID	Set-Cookie: PHPSESSID=ada19286b9364e84802324d37a822468

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	Cookie Name	Evidence
https://mail.discordultimate.com/	mailcow_locale	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: mailcow_locale=cs-cz

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	Evidence
https://mail.discordultimate.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

Software / Version	Category
DataTables 1.13.1	JavaScript libraries
jQuery 3.6.0	JavaScript libraries
Nginx	Web servers, Reverse proxies
PHP	Programming languages
Chart.js	JavaScript graphics
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
https://mail.discordultimate.com/robots.txt

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 Evidence

URL	Evidence
https://mail.discordultimate.com/	`<input autocapitalize="none" autocomplete="username" autocorrect="off" autofocus="" class="form-control" id="login_user" name="login_user" placeholder="Username" required="" type="text"/> <input autocomplete="current-password" class="form-control" id="pass_user" name="pass_user" placeholder="Password" required="" type="password"/> <button class="btn btn-xs-lg btn-success w-100 mt-2 mx-auto" style="max-width: 400px;" type="submit" value="Login">Login</button>`

https://mail.discordultimate.com/

<input autocapitalize="none" autocomplete="username" autocorrect="off" autofocus="" class="form-control" id="login_user" name="login_user" placeholder="Username" required="" type="text"/> <input autocomplete="current-password" class="form-control" id="pass_user" name="pass_user" placeholder="Password" required="" type="password"/> <button class="btn btn-xs-lg btn-success w-100 mt-2 mx-auto" style="max-width: 400px;" type="submit" value="Login">Login</button>

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.

Evidence

URL
Missing: https://mail.discordultimate.com/.well-known/security.txt

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

CVE	CVSS	EPSS Score	EPSS Percentile	CISA KEV	Summary
CVE-2024-38474	9.8	0.00764	0.72335	No	Substitution encoding issue in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows attacker to execute scripts in directories permitted by the configuration but not directly reachable by any URL or source disclosure of scripts meant to only to be executed as CGI. Users are recommended to upgrade to version 2.4.60, which fixes this issue. Some RewriteRules that capture and substitute unsafely will now fail unless rewrite flag "UnsafeAllow3F" is specified.
CVE-2024-38476	9.8	0.01393	0.79476	No	Vulnerability in core of Apache HTTP Server 2.4.59 and earlier are vulnerably to information disclosure, SSRF or local script execution via backend applications whose response headers are malicious or exploitable. Users are recommended to upgrade to version 2.4.60, which fixes this issue.
CVE-2024-38475	9.1	0.92401	0.99715	Yes	Improper escaping of output in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows an attacker to map URLs to filesystem locations that are permitted to be served by the server but are not intentionally/directly reachable by any URL, resulting in code execution or source code disclosure. Substitutions in server context that use a backreferences or variables as the first segment of the substitution are affected. Some unsafe RewiteRules will be broken by this change and the rewrite flag "UnsafePrefixStat" can be used to opt back in once ensuring the substitution is appropriately constrained.
CVE-2024-27316	7.5	0.89857	0.99542	No	HTTP/2 incoming headers exceeding the limit are temporarily buffered in nghttp2 in order to generate an informative HTTP 413 response. If a client does not stop sending headers, this leads to memory exhaustion.
CVE-2024-38477	7.5	0.01465	0.79966	No	null pointer dereference in mod_proxy in Apache HTTP Server 2.4.59 and earlier allows an attacker to crash the server via a malicious request. Users are recommended to upgrade to version 2.4.60, which fixes this issue.

Vulnerability description

Vulnerabilities found for Apache Httpd 2.4.58

Risk description

These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed "high" severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.

Recommendation

We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	CISA KEV	Summary
CVE-2024-38474	9.8	0.00764	0.72335	No	Substitution encoding issue in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows attacker to execute scripts in directories permitted by the configuration but not directly reachable by any URL or source disclosure of scripts meant to only to be executed as CGI. Users are recommended to upgrade to version 2.4.60, which fixes this issue. Some RewriteRules that capture and substitute unsafely will now fail unless rewrite flag "UnsafeAllow3F" is specified.
CVE-2024-38476	9.8	0.01393	0.79476	No	Vulnerability in core of Apache HTTP Server 2.4.59 and earlier are vulnerably to information disclosure, SSRF or local script execution via backend applications whose response headers are malicious or exploitable. Users are recommended to upgrade to version 2.4.60, which fixes this issue.
CVE-2024-38475	9.1	0.92401	0.99715	Yes	Improper escaping of output in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows an attacker to map URLs to filesystem locations that are permitted to be served by the server but are not intentionally/directly reachable by any URL, resulting in code execution or source code disclosure. Substitutions in server context that use a backreferences or variables as the first segment of the substitution are affected. Some unsafe RewiteRules will be broken by this change and the rewrite flag "UnsafePrefixStat" can be used to opt back in once ensuring the substitution is appropriately constrained.
CVE-2024-27316	7.5	0.89857	0.99542	No	HTTP/2 incoming headers exceeding the limit are temporarily buffered in nghttp2 in order to generate an informative HTTP 413 response. If a client does not stop sending headers, this leads to memory exhaustion.
CVE-2024-38477	7.5	0.01465	0.79966	No	null pointer dereference in mod_proxy in Apache HTTP Server 2.4.59 and earlier allows an attacker to crash the server via a malicious request. Users are recommended to upgrade to version 2.4.60, which fixes this issue.

Vulnerability description

Vulnerabilities found for Apache Httpd 2.4.58

Risk description

Recommendation

We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.

Evidence

Domain Queried	DNS Record Type	Description	Value
mail.discordultimate.com	A	IPv4 address	47.229.45.11

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.