Vulnerability Scan Result
| Title: | No title found |
| Description: | No description found |
| ip_address | 208.212.215.222 |
| country | US  |
| network_name | Verizon Business |
| asn | AS701 |
| ip_address | 4.17.154.92 |
| country | US |
| network_name | Level 3 Parent, LLC |
| asn | AS3356 |
25/tcp | smtp | IA Mailserver smtpd - |
80/tcp | http | Microsoft HTTPAPI httpd 2 |
443/tcp | https | - - |
465/tcp | smtp | IA Mailserver smtpd - |
587/tcp | smtp | IA Mailserver smtpd - |
993/tcp | imap | - - |
995/tcp | pop3 | - - |
5222/tcp | xmpp-client | - - |
| Software / Version | Category |
|---|---|
| AngularJS 1.8.3 | JavaScript frameworks |
| Amazon Web Services | PaaS |
| D3 5.16.0 | JavaScript graphics |
| Font Awesome | Font scripts |
| Froala Editor 5.0.0 | Rich text editors |
| FullCalendar 6.1.20 | Widgets |
| core-js 3.37.1 | JavaScript libraries |
| HTTP/3 | Miscellaneous |
| jQuery 3.7.1 | JavaScript libraries |
| Angular Material | UI frameworks |
| Moment.js 2.30.1 | JavaScript libraries |
| HeroUI | UI frameworks |
| PHP | Programming languages |
| React | JavaScript frameworks |
| Showdown | JavaScript libraries |
| Filestack | CDN |
| Lodash 1.13.8 | JavaScript libraries |
| HSTS | Security |
| TypeScript | Programming languages |
| XRegExp 5.1.2 | JavaScript libraries |
Web Application Vulnerabilities
Evidence
| URL | Response URL | Evidence |
|---|---|---|
| http://mail2.enguard.com/interface/root | http://mail2.enguard.com/interface/root | 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-319 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2023-26118 | 5.3 | 0.0061 | 0.69966 | Versions of the package angular from 1.4.9 are vulnerable to Regular Expression Denial of Service (ReDoS) via the <input type="url"> element due to the usage of an insecure regular expression in the input[url] functionality. Exploiting this vulnerability is possible by a large carefully-crafted input, which can result in catastrophic backtracking. |
| CVE-2023-26117 | 5.3 | 0.00318 | 0.54973 | Versions of the package angular from 1.0.0 are vulnerable to Regular Expression Denial of Service (ReDoS) via the $resource service due to the usage of an insecure regular expression. Exploiting this vulnerability is possible by a large carefully-crafted input, which can result in catastrophic backtracking. |
| CVE-2023-26116 | 5.3 | 0.00318 | 0.54973 | Versions of the package angular from 1.2.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the angular.copy() utility function due to the usage of an insecure regular expression. Exploiting this vulnerability is possible by a large carefully-crafted input, which can result in catastrophic backtracking. |
| CVE-2022-25844 | 5.3 | 0.01924 | 0.83567 | The package angular after 1.7.0 are vulnerable to Regular Expression Denial of Service (ReDoS) by providing a custom locale rule that makes it possible to assign the parameter in posPre: ' '.repeat() of NUMBER_FORMATS.PATTERNS[1].posPre with a very high value. **Note:** 1) This package has been deprecated and is no longer maintained. 2) The vulnerable versions are 1.7.0 and higher. |
| CVE-2024-8373 | 4.8 | 0.00013 | 0.02397 | Improper sanitization of the value of the [srcset] attribute in <source> HTML elements in AngularJS allows attackers to bypass common image source restrictions, which can also lead to a form of Content Spoofing https://owasp.org/www-community/attacks/Content_Spoofing . This issue affects all versions of AngularJS. Note: The AngularJS project is End-of-Life and will not receive any updates to address this issue. For more information see here https://docs.angularjs.org/misc/version-support-status . |
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 |
|---|---|
| http://mail2.enguard.com/interface/root | Response headers do not include the Referrer-Policy HTTP security header as well as the |
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 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| http://mail2.enguard.com/interface/root | 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
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
| Software / Version | Category |
|---|---|
| AngularJS 1.8.3 | JavaScript frameworks |
| Amazon Web Services | PaaS |
| D3 5.16.0 | JavaScript graphics |
| Font Awesome | Font scripts |
| Froala Editor 5.0.0 | Rich text editors |
| FullCalendar 6.1.20 | Widgets |
| core-js 3.37.1 | JavaScript libraries |
| HTTP/3 | Miscellaneous |
| jQuery 3.7.1 | JavaScript libraries |
| Angular Material | UI frameworks |
| Moment.js 2.30.1 | JavaScript libraries |
| HeroUI | UI frameworks |
| PHP | Programming languages |
| React | JavaScript frameworks |
| Showdown | JavaScript libraries |
| Filestack | CDN |
| Lodash 1.13.8 | JavaScript libraries |
| HSTS | Security |
| TypeScript | Programming languages |
| XRegExp 5.1.2 | 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
| 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 Post Office Protocol (POP3) service. Starting Nmap ( https://nmap.org ) at 2026-05-17 06:01 EEST Nmap scan report for mail2.enguard.com (208.212.215.222) Host is up (0.15s latency). Other addresses for mail2.enguard.com (not scanned): 4.17.154.92
PORT STATE SERVICE VERSION
995/tcp open ssl/pop3
| fingerprint-strings:
| GenericLines:
| +OK EnGuard POP nice to meet you
| -ERR Invalid command
| -ERR Invalid command
| HTTPOptions:
| +OK EnGuard POP nice to meet you
| -ERR Invalid command
| -ERR Invalid command
| NULL:
|_ +OK EnGuard POP nice to meet you
|_pop3-capabilities: APOP IMPLEMENTATION(Smartertools_SmarterMail) SASL(NTLM PLAIN) UIDL TOP UTF8(USER) USER
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/17%Time=6A092F8C%P=x86_64-pc-linux-gnu
SF:%r(NULL,5B,"+OK\x20EnGuard\x20POP\x20nice\x20to\x20meet\x20you\x20\r\n")%r(GenericL
SF:ines,87,"+OK\x20EnGuard\x20POP\x20nice\x20to\x20meet\x20you\x20\r\n-ERR\x20Invalid
SF:x20command\r\n-ERR\x20Invalid\x20command\r\n")%r(HTTPOptions,87,"+OK\x
SF:20EnGuard\x20POP\x20nice\x20to\x20meet\x20you\x20\r\n-ERR\x20Invalid\x20command\r\n-
SF:ERR\x20Invalid\x20command\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 25.16 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
| Operating System | Accuracy |
|---|---|
| Windows | 100% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| PHP | Programming languages |
| HeroUI | UI frameworks |
| React | JavaScript frameworks |
| AngularJS | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Filestack | CDN |
| HSTS | Security |
| DigiCert | SSL/TLS certificate authorities |
| 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 |
|---|---|---|---|
| mail2.enguard.com | A | IPv4 address | 208.212.215.222 |
| mail2.enguard.com | A | IPv4 address | 4.17.154.92 |
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
| Software / Version | Category |
|---|---|
| PHP | Programming languages |
| HeroUI | UI frameworks |
| React | JavaScript frameworks |
| AngularJS | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Filestack | CDN |
| HSTS | Security |
| 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.