Vulnerability Scan Result

Target:

http://mrock.cybermail.jp/ (redirect)

Scanned target: https://mrock.cybermail.jp/

Submitted: May 23, 2025 from SR

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Title:	CyberMail
Description:	No description found

IP Information

IP address	59.84.175.230
Country	JP
AS number	AS10010
Net name	Tokai Communications Corporation

Open Ports

80/tcp	http	F5 BIG-IP load balancer http proxy -
110/tcp	pop3	- -
143/tcp	imap	- -
443/tcp	https	Apache httpd -
465/tcp	smtp	Mail2000 smtpd 8
587/tcp	smtp	Mail2000 smtpd 8
993/tcp	imap	- -
995/tcp	pop3	- -

Web Technologies

Software / Version	Category
jQuery Migrate 3.3.1	JavaScript libraries
Apache HTTP Server	Web servers
jQuery	JavaScript libraries
DreamWeaver	Editors

Web Application Vulnerabilities

Evidence

URL	Evidence
https://mrock.cybermail.jp/	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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://mrock.cybermail.jp/	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

Vulnerability description

We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.

Risk description

The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.

Recommendation

The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.

Classification

CWE	CWE-693
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL Evidence

URL	Evidence
https://mrock.cybermail.jp/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. object-src: We recommend restricting object-src to 'none'. frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval().

https://mrock.cybermail.jp/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. object-src: We recommend restricting object-src to 'none'. frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval().

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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://mrock.cybermail.jp/	Response headers do not include the X-Content-Type-Options HTTP security header

Vulnerability description

We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.

Risk description

The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.

Recommendation

We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.

Classification

CWE	CWE-693
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

Software / Version	Category
jQuery Migrate 3.3.1	JavaScript libraries
Apache HTTP Server	Web servers
jQuery	JavaScript libraries
DreamWeaver	Editors

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

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL
https://mrock.cybermail.jp/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).

Classification

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://mrock.cybermail.jp/cgi-bin/login	`<input autocomplete="off" maxlength="318" name="USERID" onfocus="stBoard && stBoard.setTarget(this)" placeholder="ã¦ã¼ã¶ID - UserID ï¼" value=""/> <input autocomplete="off" maxlength="32" name="PASSWD" onfocus="stBoard && stBoard.setTarget(this)" placeholder="ãã¹ã¯ã¼ã - Password ï¼" type="password"/> <input type="submit" value="Login"/>`

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	Method	Parameters	Evidence
https://mrock.cybermail.jp/cgi-bin/login	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 Cookies: BIGipServercmsp1_Pool_80=2282006720.20480.0000	Operating system paths found in the HTTP response: `/webmail/tmp/340251.13916.var`

Vulnerability description

We found operating system paths returned in a HTTP response.

Risk description

The risk is that path disclosure may help an attacker learn more about the remote server's file system, thus increasing the effectiveness and precision of any future attacks.

Recommendation

Configure the web server to avoid leaking path information by using generic error messages that do not reveal any internal file paths. Make sure no server file is referred with its absolute path in the website code.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://mrock.cybermail.jp/.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.

Classification

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Method	Summary
https://mrock.cybermail.jp/	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: HEAD,GET,POST,OPTIONS` Request / Response

Vulnerability description

We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.

Risk description

The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.

Recommendation

We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.

Classification

CWE	CWE-16
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Infrastructure Vulnerabilities

Evidence

We managed to detect a publicly accessible Post Office Protocol (POP3) service.

Starting Nmap ( https://nmap.org ) at 2025-05-23 03:04 EEST
Nmap scan report for mrock.cybermail.jp (59.84.175.230)
Host is up (0.25s latency).
rDNS record for 59.84.175.230: cm.cybermail.jp

PORT    STATE SERVICE VERSION
110/tcp open  pop3
|_pop3-capabilities: PIPELINING USER EXPIRE(NEVER) UIDL TOP
| fingerprint-strings: 
|   GenericLines: 
|     +OK MPOP3D V8.0 at cm.cybermail.jp starting.
|     -ERR Unknown command: "".
|     -ERR Unknown command: "".
|   HTTPOptions: 
|     +OK MPOP3D V8.0 at cm.cybermail.jp starting.
|     -ERR Unknown command: "OPTIONS".
|     -ERR Unknown command: "".
|   NULL: 
|_    +OK MPOP3D V8.0 at cm.cybermail.jp starting.
1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service :
SF-Port110-TCP:V=7.93%I=7%D=5/23%Time=682FBBAE%P=x86_64-pc-linux-gnu%r(NUL
SF:L,2E,"\+OK\x20MPOP3D\x20V8\.0\x20at\x20cm\.cybermail\.jp\x20starting\.\
SF:r\n")%r(GenericLines,64,"\+OK\x20MPOP3D\x20V8\.0\x20at\x20cm\.cybermail
SF:\.jp\x20starting\.\r\n-ERR\x20Unknown\x20command:\x20\"\"\.\r\n-ERR\x20
SF:Unknown\x20command:\x20\"\"\.\r\n")%r(HTTPOptions,6B,"\+OK\x20MPOP3D\x2
SF:0V8\.0\x20at\x20cm\.cybermail\.jp\x20starting\.\r\n-ERR\x20Unknown\x20c
SF:ommand:\x20\"OPTIONS\"\.\r\n-ERR\x20Unknown\x20command:\x20\"\"\.\r\n");

Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 19.53 seconds

Vulnerability description

We found that the Post Office Protocol (POP3) service is publicly accessible and doesn’t include STARTTLS capability. Email clients use the Post Office Protocol (POP) to download emails for user accounts. Some POP servers are initially set up to operate over an unsecured protocol. When email clients download email content through this plaintext protocol, it can pose a substantial risk to the organization's network, especially depending on which user account is set to receive the emails.

Risk description

Exposing this service online can enable attackers to conduct man-in-the-middle attacks, thereby gaining access to sensitive user credentials and the contents of emails. Given that POP3 operates via a plaintext protocol, the entirety of the data exchanged between the client and server is left unencrypted. This critical information could then be leveraged in further attacks on the organization's network.

Recommendation

We recommend turning off POP3 access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the POP3 service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, activating STARTTLS capability (switching the connection to a secure communication) or utilizing Secure POP3 (POP3S) is recommended, as this protocol employs encryption.

Evidence

We managed to detect a publicly accessible Post Office Protocol (POP3) service.

Starting Nmap ( https://nmap.org ) at 2025-05-23 03:05 EEST
Nmap scan report for mrock.cybermail.jp (59.84.175.230)
Host is up (0.28s latency).
rDNS record for 59.84.175.230: cm.cybermail.jp

PORT    STATE SERVICE  VERSION
995/tcp open  ssl/pop3
| fingerprint-strings: 
|   GenericLines: 
|     +OK MPOP3D V8.0 at cm.cybermail.jp starting.
|     -ERR Unknown command: "".
|     -ERR Unknown command: "".
|   HTTPOptions: 
|     +OK MPOP3D V8.0 at cm.cybermail.jp starting.
|     -ERR Unknown command: "OPTIONS".
|     -ERR Unknown command: "".
|   NULL: 
|_    +OK MPOP3D V8.0 at cm.cybermail.jp starting.
|_pop3-capabilities: USER TOP EXPIRE(NEVER) UIDL PIPELINING
1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service :
SF-Port995-TCP:V=7.93%T=SSL%I=7%D=5/23%Time=682FBBC9%P=x86_64-pc-linux-gnu
SF:%r(NULL,2E,"\+OK\x20MPOP3D\x20V8\.0\x20at\x20cm\.cybermail\.jp\x20start
SF:ing\.\r\n")%r(GenericLines,64,"\+OK\x20MPOP3D\x20V8\.0\x20at\x20cm\.cyb
SF:ermail\.jp\x20starting\.\r\n-ERR\x20Unknown\x20command:\x20\"\"\.\r\n-E
SF:RR\x20Unknown\x20command:\x20\"\"\.\r\n")%r(HTTPOptions,6B,"\+OK\x20MPO
SF:P3D\x20V8\.0\x20at\x20cm\.cybermail\.jp\x20starting\.\r\n-ERR\x20Unknow
SF:n\x20command:\x20\"OPTIONS\"\.\r\n-ERR\x20Unknown\x20command:\x20\"\"\.
SF:\r\n");

Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 27.28 seconds

Vulnerability description

Risk description

Recommendation

Evidence

Domain Queried	DNS Record Type	Description	Value
mrock.cybermail.jp	A	IPv4 address	59.84.175.230

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.

Operating System	Accuracy
OpenBSD 4.0	86%

Evidence

Software / Version	Category
DreamWeaver	Editors
Apache HTTP Server	Web servers
jQuery	JavaScript libraries
jQuery Migrate 3.3.1	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.