Vulnerability Scan Result
| Title: | ALTBANK |
| Description: |
| ip_address | 172.67.74.72 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
| ip_address | 104.26.5.158 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
| ip_address | 104.26.4.158 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | cloudflare - |
2082/tcp | http | Cloudflare http proxy - |
2083/tcp | https | nginx - |
2086/tcp | http | Cloudflare http proxy - |
2087/tcp | https | nginx - |
8080/tcp | http | Cloudflare http proxy - |
8443/tcp | http | cloudflare - |
| Software / Version | Category |
|---|---|
| Albacross | Analytics, Retargeting |
| Facebook Pixel 2.9.235 | Analytics |
| core-js 3.32.2 | JavaScript libraries |
| Google Analytics | Analytics |
| HTTP/3 | Miscellaneous |
| jQuery 3.1.0 | JavaScript libraries |
| Laravel | Web frameworks |
| October CMS | CMS |
| PHP | Programming languages |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://altbank.ua/ | october_session | Set-Cookie: october_session=eyJpdiI6IlV4M1dIVEhnSlpwMGxSSTRQSnY5R2c9PSIsInZhbHVlIjoienU2eVpCN0FXbldaYzVjSERDc3dsajhyNzJsWmo1TUZ2azRvOWdKNVN1SnVUODA2RU1Yd0J3dXY5NkJxTThKNTc3QkNOK2k4aWtDRWdPVUJvQmVCNERzc3lzaGFIZEZHRFpmZHhGTWs2UTlZTVJMSU1JbE85M09VNG45aW9kVE0iLCJtYWMiOiIwNjVmYWY3ZjJkNGIxNWE4NWNmM2U4OTZjODg2YmViMTM0YzM0OTkzNzk4ZjMxN2JhNTMyMDk4ODdkOGY4YmI1In0%3D |
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
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2020-11023 | 6.9 | 0.21319 | 0.9541 | 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. |
| CVE-2020-11022 | 6.9 | 0.22547 | 0.95561 | 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. |
| CVE-2019-11358 | 6.1 | 0.02403 | 0.84441 | 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. |
Vulnerability description
Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.
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. 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
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-1035 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://altbank.ua/ | 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 |
|---|---|
| Albacross | Analytics, Retargeting |
| Facebook Pixel 2.9.235 | Analytics |
| core-js 3.32.2 | JavaScript libraries |
| Google Analytics | Analytics |
| HTTP/3 | Miscellaneous |
| jQuery 3.1.0 | JavaScript libraries |
| Laravel | Web frameworks |
| October CMS | CMS |
| PHP | Programming languages |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| 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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://altbank.ua/ | 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 | Operating system paths found in the HTTP response: |
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
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.
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.altbank.ua | TXT | Text record | "v=DMARC1; p=quarantine; rua=mailto:dmarc@altbank.ua; ruf=mailto:dmarc@altbank.ua; sp=quarantine" |
Vulnerability description
We found that the target uses p=quarantine in the DMARC policy. When a DMARC policy is set to p=quarantine, emails that fail DMARC validation are delivered but placed in the recipient’s spam or junk folder. Although it offers some protection, this policy is less strict than p=reject, which blocks such emails entirely.
Risk description
While emails failing DMARC validation are sent to the spam folder, users may still retrieve them from there, leading to a higher risk of phishing and spoofing attacks succeeding. Moreover, less strict enforcement may allow more fraudulent emails to reach user inboxes if misclassified.
Recommendation
We recommend considering moving to a stricter policy, such as p=reject, where emails that fail DMARC validation are completely rejected rather than delivered to spam folders. This reduces the risk of users interacting with potentially malicious emails.
Evidence
We found insecure DNS cookie usage on the following nameservers: amalia.ns.cloudflare.com, buck.ns.cloudflare.com
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| altbank.ua | SPF | Sender Policy Framework | "v=spf1 ip4:185.254.193.229 ip4:185.254.193.236 ip4:89.162.144.230 ip4:78.27.225.105 a mx include:spf.selzy.com include:spf.protection.outlook.com ~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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| selector1 | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuw/iYgxrSgXXojVLfCDGHvieXBpwZw0Ii24cXvGPjeox63RtfEeQpJ2Zx4j/DQrt65D3a150piYRMJK4CQMPYPhvRTVgQplTYjzmZ9T0MR/CwVNNCO0L8Gj0ToaoJ3YDMOqzteLz6vijZglU7s1k1z12htFRMCQ0n/6oSEimERxYP1bjBOAYiy69JSvXcnN7Q" "7qgzT1LaIkIAJFMqMTsVRqhV5SxuESD4FLJEEtnzOvGMP996eGFn0rBA7OxVwo3AB4Pm3oOGaehlJM4OeBgicbaFFeb5Lqx7rtXJgG6s8TtDqWVe/Rx1R7mGgM5lkXEt1jdfZWDg/ArU+H5y08IrQIDAQAB;" |
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
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 |
|---|---|
| October CMS | CMS |
| PHP | Programming languages |
| Laravel | Web frameworks |
| Google Tag Manager | Tag managers |
| Facebook Pixel 2.9.235 | Analytics |
| Albacross | Analytics, Retargeting |
| Google Analytics | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| HSTS | Security |
| Cloudflare | CDN |
| 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
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
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 |
|---|---|
| FreeBSD 11.1-STABLE | 91% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
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 |
|---|---|---|---|
| altbank.ua | A | IPv4 address | 172.67.74.72 |
| altbank.ua | A | IPv4 address | 104.26.4.158 |
| altbank.ua | A | IPv4 address | 104.26.5.158 |
| altbank.ua | NS | Name server | amalia.ns.cloudflare.com |
| altbank.ua | NS | Name server | buck.ns.cloudflare.com |
| altbank.ua | MX | Mail server | 0 altbank-ua.mail.protection.outlook.com |
| altbank.ua | SOA | Start of Authority | amalia.ns.cloudflare.com. dns.cloudflare.com. 2385397375 10000 2400 604800 1800 |
| altbank.ua | AAAA | IPv6 address | 2606:4700:20::ac43:4a48 |
| altbank.ua | AAAA | IPv6 address | 2606:4700:20::681a:59e |
| altbank.ua | AAAA | IPv6 address | 2606:4700:20::681a:49e |
| altbank.ua | TXT | Text record | "MS=ms19456525" |
| altbank.ua | SPF | Sender Policy Framework | "v=spf1 ip4:185.254.193.229 ip4:185.254.193.236 ip4:89.162.144.230 ip4:78.27.225.105 a mx include:spf.selzy.com include:spf.protection.outlook.com ~all" |
| _dmarc.altbank.ua | TXT | Text record | "v=DMARC1; p=quarantine; rua=mailto:dmarc@altbank.ua; ruf=mailto:dmarc@altbank.ua; sp=quarantine" |
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.