Vulnerability Scan Result

Target:

http://ibank.accordmetro.com/ (redirect)

Scanned target: http://ibank.accordmetro.com/login.php

Submitted: April 19, 2025 from BH

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	Accord Metro Bank - Login
Description:	No description found

IP Information

IP address	185.56.136.50
Country	NL
AS number	AS60558
Net name	Phoenix Nap LLC

Open Ports

21/tcp	ftp	Pure-FTPd -
25/tcp	smtp	- -
53/tcp	domain	PowerDNS Authoritative Server 4.9.2
80/tcp	http	LiteSpeed -
110/tcp	pop3	Dovecot pop3d -
143/tcp	imap	Dovecot imapd -
443/tcp	https	LiteSpeed -
465/tcp	smtp	Exim smtpd 4.98.1
587/tcp	smtp	Exim smtpd 4.98.1
993/tcp	imaps	- -
995/tcp	pop3s	- -
3306/tcp	mysql	MySQL 8.0.37-cll-lve
5666/tcp	tcpwrapped	- -

Web Technologies

Software / Version	Category
Bootstrap 4.6.0	UI frameworks
Google Font API	Font scripts
Highlight.js	JavaScript libraries
jQuery 3.1.1	JavaScript libraries
PHP	Programming languages
Popper	Miscellaneous
SweetAlert	JavaScript libraries
SweetAlert2	JavaScript libraries

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
http://ibank.accordmetro.com/login.php	PHPSESSID	Set-Cookie: PHPSESSID=alp418k7nvvhujdnvi9o5atgvj

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

Evidence

URL	Cookie Name	Evidence
http://ibank.accordmetro.com/login.php	PHPSESSID	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: PHPSESSID=alp418k7nvvhujdnvi9o5atgvj

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

Evidence

URL	Response URL	Evidence
http://ibank.accordmetro.com/login.php	http://ibank.accordmetro.com/login.php	Communication is made over unsecure, unencrypted HTTP.

Vulnerability description

We noticed that the communication between the web browser and the server is done using the HTTP protocol, which transmits data unencrypted over the network.

Risk description

The risk is that an attacker who manages to intercept the communication at the network level can read and modify the data transmitted (including passwords, secret tokens, credit card information and other sensitive data).

Recommendation

We recommend you to reconfigure the web server to use HTTPS - which encrypts the communication between the web browser and the server.

Classification

CWE	CWE-311
OWASP Top 10 - 2017	A3 - Sensitive Data Exposure
OWASP Top 10 - 2021	A4 - Insecure Design

Evidence

URL	Evidence
http://ibank.accordmetro.com/assets/css/components	Found output resembling directory listing.
http://ibank.accordmetro.com/assets/js/authentication	Found output resembling directory listing.
http://ibank.accordmetro.com/assets/js/components/	Found output resembling directory listing.
http://ibank.accordmetro.com/bootstrap/	Found output resembling directory listing.
http://ibank.accordmetro.com/bootstrap/css/	Found output resembling directory listing.
http://ibank.accordmetro.com/plugins/animate	Found output resembling directory listing.
http://ibank.accordmetro.com/plugins/notification/snackbar	Found output resembling directory listing.
http://ibank.accordmetro.com/plugins/perfect-scrollbar/	Found output resembling directory listing.
http://ibank.accordmetro.com/plugins/sweetalerts	Found output resembling directory listing.

Vulnerability description

We noticed that the target application's web server is affected by a Directory Listing vulnerability in its URL structure. Directory listing is enabled due to misconfigured server settings, allowing attackers to view all files and subdirectories on the server.

Risk description

The risk is that it's often the case that sensitive files are "hidden" among public files in that location and attackers can use this vulnerability to access them.

Recommendation

We recommend reconfiguring the web server in order to deny directory listing. Furthermore, you should verify that there are no sensitive files at the mentioned URLs.

Classification

CWE	CWE-548
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A1 - Broken Access Control

Evidence

CVSS	CVE	Summary	Affected software
4.3	CVE-2019-11358	jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.	jquery 3.1.1
4.3	CVE-2020-11023	In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.	jquery 3.1.1
4.3	CVE-2020-11022	In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.	jquery 3.1.1

Vulnerability description

We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.

Risk description

The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system.

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1026
OWASP Top 10 - 2017	A9 - Using Components with Known Vulnerabilities
OWASP Top 10 - 2021	A6 - Vulnerable and Outdated Components

Evidence

URL	Evidence
http://ibank.accordmetro.com/login.php	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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
http://ibank.accordmetro.com/login.php	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

URL	Evidence
http://ibank.accordmetro.com/login.php	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

Software / Version	Category
Bootstrap 4.6.0	UI frameworks
Google Font API	Font scripts
Highlight.js	JavaScript libraries
jQuery 3.1.1	JavaScript libraries
PHP	Programming languages
Popper	Miscellaneous
SweetAlert	JavaScript libraries
SweetAlert2	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.

Classification

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

Evidence

URL
Missing: http://ibank.accordmetro.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.

Classification

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

Infrastructure Vulnerabilities

Evidence

We managed to detect a publicly accessible MySQL service.

PORT STATE SERVICE VERSION
3306/tcp open mysql MySQL 8.0.37-cll-lve

Vulnerability description

We identified that the MySQL service is publicly accessible. MySQL serves as a common database for numerous web applications and services for data storage, making it a potential prime target for determined attackers.

Risk description

The risk exists that an attacker exploits this issue by launching a password-based attack on the MySQL service. Furthermore, they could exploit zero-day vulnerabilities to obtain remote access to the MySQL database server, thereby gaining complete control over its operating system and associated services. Such an attack could lead to the exposure of confidential or sensitive information.

Recommendation

We recommend turning off public Internet access to MySQL and opting for a Virtual Private Network (VPN) that enforces two-factor authentication (2FA). Avoid enabling direct user authentication to the MySQL service via the Internet, as this could enable attackers to engage in password-guessing and potentially initiate attacks leading to complete control. However, if the MySQL service is required to be directly accessible over the Internet, we recommend reconfiguring it to be accessible only from known IP addresses.

Evidence

We managed to detect a publicly accessible File Transfer Protocol (FTP) service.

PORT STATE SERVICE VERSION
21/tcp open ftp Pure-FTPd

Vulnerability description

We found that the File Transfer Protocol (FTP) service is publicly accessible. The FTP enables client systems to connect to upload and download files. Nonetheless, FTP lacks encryption for the data exchanged between the server and the client, leaving all transferred data exposed in plaintext.

Risk description

Exposing this service online can enable attackers to execute man-in-the-middle attacks, capturing sensitive user credentials and the contents of files because FTP operates without encryption. The entirety of the communication between the client and the server remains unsecured in plaintext. This acquired information could further facilitate additional attacks within the network.

Recommendation

We recommend turning off FTP access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the FTP service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, utilizing SFTP (Secure File Transfer Protocol) is recommended as this protocol employs encryption to secure data transfers.

Evidence

Domain Queried	DNS Record Type	Description	Value
ibank.accordmetro.com	SPF	Sender Policy Framework	"v=spf1 +a +mx +ip4:185.56.136.50 ~all"

Vulnerability description

We found that the Sender Policy Framework (SPF) record for the domain is configured with ~all (soft fail), which indicates that emails from unauthorized IP addresses are not explicitly denied. Instead, the recipient mail server is instructed to treat these messages with suspicion but may still accept them. This configuration may not provide enough protection against email spoofing and unauthorized email delivery, leaving the domain more vulnerable to impersonation attempts.

Risk description

The ~all directive in an SPF record allows unauthorized emails to pass through some email servers, even though they fail SPF verification. While such emails may be marked as suspicious or placed into a spam folder, not all mail servers handle soft fail conditions consistently. This creates a risk that malicious actors can spoof the domain to send phishing emails or other fraudulent communications, potentially causing damage to the organization's reputation and leading to successful social engineering attacks.

Recommendation

We recommend changing the SPF record's ~all (soft fail) directive to -all (hard fail). The -all setting tells recipient mail servers to reject emails from any IP addresses not listed in the SPF record, providing stronger protection against email spoofing. Ensure that all legitimate IP addresses and services that send emails on behalf of your domain are properly included in the SPF record before implementing this change.

Evidence

Domain Queried	DNS Record Type	Description	Value
ibank.accordmetro.com	A	IPv4 address	185.56.136.50
ibank.accordmetro.com	SPF	Sender Policy Framework	"v=spf1 +a +mx +ip4:185.56.136.50 ~all"

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.