Vulnerability Scan Result

Target:

http://m365.us.vadesecure.com/ (redirect)

Scanned target: https://m365.us.vadesecure.com/

Submitted: Aug 16, 2025 from MC

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Hornetsecurity - Vade for M365
Description:	No description found

IP Information

ip_address	13.68.138.172
country	US
network_name	Microsoft Corporation
asn	AS8075

Open Ports

25/tcp	smtp	- -
80/tcp	http	- -
443/tcp	https	nginx -

Web Technologies

Software / Version	Category
Font Awesome	Font scripts
core-js 3.8.3	JavaScript libraries
Nginx	Web servers, Reverse proxies
Umami	Analytics
Lodash 4.17.21	JavaScript libraries

Web Application Vulnerabilities

Evidence

Software / Version	Category
Font Awesome	Font scripts
core-js 3.8.3	JavaScript libraries
Nginx	Web servers, Reverse proxies
Umami	Analytics
Lodash 4.17.21	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.

Evidence

URL Evidence

URL	Evidence
https://m365.us.vadesecure.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues: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'. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers.

https://m365.us.vadesecure.com/

Response headers include the HTTP Content-Security-Policy security header with the following security issues: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'. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers.

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
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://m365.us.vadesecure.com/	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
OWASP Top 10 - 2021

Evidence

URL
https://m365.us.vadesecure.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).

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Nginx	Web servers, Reverse proxies
Font Awesome	Font scripts

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
m365.us.vadesecure.com	A	IPv4 address	13.68.138.172
m365.us.vadesecure.com	MX	Mail server	10 mx-m365.us.vadesecure.com
m365.us.vadesecure.com	SPF	Sender Policy Framework	"v=spf1 ip4:40.71.22.12 ip4:13.82.28.67 -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.