Vulnerability Scan Result

Target:

https://shop.infomaniak.com/ (redirect)

Scanned target: https://shop.infomaniak.com/order

Submitted: May 22, 2025 from MX

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	🚀 Shop - Infomaniak
Description:	No description found

IP Information

IP address	185.125.25.1
Country	CH
AS number	AS29222
Net name	Infomaniak Network SA

Open Ports

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

Web Technologies

Software / Version	Category
Angular 13.3.11	JavaScript frameworks
Linkedin Ads	Advertising
Zone.js	JavaScript frameworks
core-js 3.27.1	JavaScript libraries
Matomo Analytics	Analytics
Sectigo	SSL/TLS certificate authorities
Sentry	Issue trackers
Chart.js	JavaScript graphics
reCAPTCHA	Security
Google Tag Manager	Tag managers
Lodash 4.17.21	JavaScript libraries
HSTS	Security
TypeScript	Programming languages
Cart Functionality	Ecommerce

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://shop.infomaniak.com/order	SHOP-XSRF-TOKEN	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: SHOP-XSRF-TOKEN=POesV2ZuHLxZrq5iXNyo1Pvju1mwehxTS9YENGWG

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	Cookie Name	Evidence
https://shop.infomaniak.com/order	SHOP-XSRF-TOKEN	Set-Cookie: .infomaniak.com

Vulnerability description

We found that the target application sets cookies with a domain scope that is too broad. Specifically, cookies intended for use within a particular application are configured in such a way that they can be accessed by multiple subdomains of the same primary domain.

Risk description

The risk is that a cookie set for example.com may be sent along with the requests sent to dev.example.com, calendar.example.com, hostedsite.example.com. Potentially risky websites under your main domain may access those cookies and use the victim session from the main site.

Recommendation

The `Domain` attribute should be set to the origin host to limit the scope to that particular server. For example if the application resides on server app.mysite.com, then it should be set to `Domain=app.mysite.com`

Classification

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

Evidence

URL	Evidence
https://shop.infomaniak.com/order	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

URL	Evidence
https://shop.infomaniak.com/order	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

URL	Evidence
https://shop.infomaniak.com/order	Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: Allow only resources downloaded over HTTPS. frame-src: Allow only resources downloaded over HTTPS. object-src: Allow only resources downloaded over HTTPS. default-src: Allow only resources downloaded over HTTPS. child-src: Allow only resources downloaded over HTTPS. script-src: data: URI in script-src allows the execution of unsafe scripts. font-src: Allow only resources downloaded over HTTPS. object-src: We recommend restricting object-src to 'none' only. style-src: Allow only resources downloaded over HTTPS. report-uri: report-uri is deprecated in CSP3. Please use the report-to directive instead. 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-eval' allows the execution of code injected into DOM APIs such as eval(). worker-src: Allow only resources downloaded over HTTPS. connect-src: Allow only resources downloaded over HTTPS. img-src: Allow only resources downloaded over HTTPS. media-src: Allow only resources downloaded over HTTPS. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers.

https://shop.infomaniak.com/order

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: Allow only resources downloaded over HTTPS. frame-src: Allow only resources downloaded over HTTPS. object-src: Allow only resources downloaded over HTTPS. default-src: Allow only resources downloaded over HTTPS. child-src: Allow only resources downloaded over HTTPS. script-src: data: URI in script-src allows the execution of unsafe scripts. font-src: Allow only resources downloaded over HTTPS. object-src: We recommend restricting object-src to 'none' only. style-src: Allow only resources downloaded over HTTPS. report-uri: report-uri is deprecated in CSP3. Please use the report-to directive instead. 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-eval' allows the execution of code injected into DOM APIs such as eval(). worker-src: Allow only resources downloaded over HTTPS. connect-src: Allow only resources downloaded over HTTPS. img-src: Allow only resources downloaded over HTTPS. media-src: Allow only resources downloaded over HTTPS. 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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

Software / Version	Category
Angular 13.3.11	JavaScript frameworks
Linkedin Ads	Advertising
Zone.js	JavaScript frameworks
core-js 3.27.1	JavaScript libraries
Matomo Analytics	Analytics
Sectigo	SSL/TLS certificate authorities
Sentry	Issue trackers
Chart.js	JavaScript graphics
reCAPTCHA	Security
Google Tag Manager	Tag managers
Lodash 4.17.21	JavaScript libraries
HSTS	Security
TypeScript	Programming languages
Cart Functionality	Ecommerce

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
https://shop.infomaniak.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).

Classification

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

Evidence

URL	Method	Summary
https://shop.infomaniak.com/order	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
shop.infomaniak.com	A	IPv4 address	185.125.25.1
shop.infomaniak.com	AAAA	IPv6 address	2001:1600:0:aaaa::2:6

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.

Operating System	Accuracy
Linux 3.2	94%

Evidence

Software / Version	Category
Cart Functionality	Ecommerce
Google Tag Manager	Tag managers
Sectigo	SSL/TLS certificate authorities
Linkedin Ads	Advertising
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.