Vulnerability Scan Result

Target:

http://apps.microsoft.com/

Scanned target: http://apps.microsoft.com/

Submitted: Nov 18, 2025 from LS

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Microsoft Store - Download apps, games & more for your Windows PC
Description:	Explore the Microsoft Store for apps and games on Windows. Enjoy exclusive deals, new releases, and your favorite content all in one place.

IP Information

ip_address	13.107.246.64
country	US
network_name	Microsoft Corporation
asn	AS8075

ip_address	13.107.213.64
country	US
network_name	Microsoft Corporation
asn	AS8075

Open Ports

80/tcp	http	- -
443/tcp	https	- -

Web Technologies

Software / Version	Category
Azure	PaaS
Azure Monitor	Analytics, Performance
Azure Front Door	Load balancers
Open Graph	Miscellaneous
PWA	Miscellaneous
Priority Hints	Performance
Microsoft ASP.NET	Web frameworks
HSTS	Security

Web Application Vulnerabilities

Evidence

Software / Version	Category
Azure	PaaS
Azure Monitor	Analytics, Performance
Azure Front Door	Load balancers
Open Graph	Miscellaneous
PWA	Miscellaneous
Priority Hints	Performance
Microsoft ASP.NET	Web frameworks
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 Evidence

URL	Evidence
http://apps.microsoft.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: data: URI in default-src allows the execution of unsafe scripts. 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: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. report-uri: report-uri is deprecated in CSP3. Please use the report-to directive instead. object-src: We recommend restricting object-src to 'none'. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files.

http://apps.microsoft.com/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: data: URI in default-src allows the execution of unsafe scripts. 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: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. report-uri: report-uri is deprecated in CSP3. Please use the report-to directive instead. object-src: We recommend restricting object-src to 'none'. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files.

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
http://apps.microsoft.com/	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
OWASP Top 10 - 2021

Evidence

URL	Method	Parameters	Evidence
http://apps.microsoft.com/	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	Email Address: support@microsoft.com

Vulnerability description

We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.

Risk description

The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.

Recommendation

Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.

Classification

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

Evidence

URL	Method	Summary
http://apps.microsoft.com/	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 405 status code and the header: `Allow: GET, HEAD` 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
OWASP Top 10 - 2021

Infrastructure Vulnerabilities

Operating System	Accuracy
Crestron XPanel control system	87%

Evidence

Software / Version	Category
Microsoft ASP.NET	Web frameworks
Azure Front Door	Load balancers
Azure	PaaS
Azure Monitor	Analytics, Performance
PWA	Miscellaneous
Open Graph	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
Microsoft ASP.NET	Web frameworks
Azure Front Door	Load balancers
Azure	PaaS
HSTS	Security
Azure Monitor	Analytics, Performance
PWA	Miscellaneous
Open Graph	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
apps.microsoft.com	A	IPv4 address	13.107.246.64
apps.microsoft.com	A	IPv4 address	13.107.213.64
apps.microsoft.com	AAAA	IPv6 address	2620:1ec:bdf::64
apps.microsoft.com	AAAA	IPv6 address	2620:1ec:46::64
apps.microsoft.com	CNAME	Canonical name	web-store-eyfkgzgudfgwftdc.z01.azurefd.net

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.