Vulnerability Scan Result

Target:

https://www.swisstransfer.com/d/14f67694-41bb-4e9b-b8b9-8fd52521029b

Scanned target: https://www.swisstransfer.com/d/14f67694-41bb-4e9b-b8b9-8fd52521029b

Submitted: Jul 18, 2025 from MN

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

https://www.swisstransfer.com/d/14f67694-41bb-4e9b-b8b9-8fd52521029b

Title:	SwissTransfer - Envoi sécurisé et gratuit de gros fichiers
Description:	Envoyez jusqu'à 50 Go - Gratuit et sans inscription - Gardez vos transferts jusqu'à 30 jours.

IP Information

ip_address	185.125.25.84
country	CH
network_name	Infomaniak Network SA
asn	AS29222

Open Ports

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

Web Technologies

Software / Version	Category
Angular 19.2.14	JavaScript frameworks
Zone.js	JavaScript frameworks
Apache HTTP Server	Web servers
Open Graph	Miscellaneous
React	JavaScript frameworks
reCAPTCHA	Security
Google Tag Manager	Tag managers
HSTS	Security
TypeScript	Programming languages
UserReport	Issue trackers, Surveys

Web Application Vulnerabilities

Evidence

URL Evidence

URL	Evidence
https://www.swisstransfer.com/d/14f67694-41bb-4e9b-b8b9-8fd52521029b	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: script-src directive is missing. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'.

https://www.swisstransfer.com/d/14f67694-41bb-4e9b-b8b9-8fd52521029b

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: script-src directive is missing. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'.

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

Software / Version	Category
Angular 19.2.14	JavaScript frameworks
Zone.js	JavaScript frameworks
Apache HTTP Server	Web servers
Open Graph	Miscellaneous
React	JavaScript frameworks
reCAPTCHA	Security
Google Tag Manager	Tag managers
HSTS	Security
TypeScript	Programming languages
UserReport	Issue trackers, Surveys

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
https://www.swisstransfer.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).

Evidence

URL	Evidence
https://www.swisstransfer.com/d/14f67694-41bb-4e9b-b8b9-8fd52521029b	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
OWASP Top 10 - 2021

Evidence

URL	Method	Summary
https://www.swisstransfer.com/d/14f67694-41bb-4e9b-b8b9-8fd52521029b	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
OWASP Top 10 - 2021

Infrastructure Vulnerabilities

Operating System	Accuracy
Linux 3.2	94%

Evidence

Software / Version	Category
React	JavaScript frameworks
Apache HTTP Server	Web servers
reCAPTCHA	Security
Google Tag Manager	Tag managers
HSTS	Security
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
www.swisstransfer.com	A	IPv4 address	185.125.25.84
www.swisstransfer.com	NS	Name server	ns11.infomaniak.ch
www.swisstransfer.com	NS	Name server	ns12.infomaniak.ch
www.swisstransfer.com	MX	Mail server	5 mta-gw.infomaniak.ch
www.swisstransfer.com	SOA	Start of Authority	ns11.infomaniak.ch. hostmaster.infomaniak.ch. 2025062004 10800 3600 605800 3600
www.swisstransfer.com	TXT	Text record	"facebook-domain-verification=5czto9guw48dsycwgsxwagbjdjn3dv"
www.swisstransfer.com	TXT	Text record	"google-site-verification=RZyn5Ud6SrvZB1TxU4O-R3WJrkBSuKoTm8OAtPIVPlE"
www.swisstransfer.com	SPF	Sender Policy Framework	"v=spf1 include:spf.infomaniak.ch -all"
www.swisstransfer.com	CNAME	Canonical name	swisstransfer.com

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.