Vulnerability Scan Result

Target:

https://sas-mtep.deutsche-boerse.com/selfEnrollment/index.aspx?code=v1vW2RPoxzWlrFW6fts28qsJk (redirect)

Scanned target: https://sas-mtep.deutsche-boerse.com/selfEnrollment/transit.aspx

Submitted: May 22, 2025 from SI

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

https://sas-mtep.deutsche-boerse.com/selfEnrollment/index.aspx?code=v1vW2RPoxzWlrFW6fts28qsJk

Title:	No title found
Description:	No description found

IP Information

IP address	193.29.71.185
Country	DE
AS number	AS12625
Net name	Deutsche Boerse Ag

Open Ports

443/tcp

https

F5 BIG-IP load balancer http proxy -

Web Technologies

Software / Version	Category
Microsoft ASP.NET	Web frameworks
DigiCert	SSL/TLS certificate authorities

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://sas-mtep.deutsche-boerse.com/selfEnrollment/transit.aspx	TS01d99b39	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: TS01d99b39=0123537947cce5f21c84567f17f43c3b0119b57d33d25c9e5d1afbb07d01f10a6efec311bd3e13154b226722ae564688660eb5d36dd649388f6a66b56febdadb790a94c1cdc25930f6ebfee4249f557097a200a1650488e86bad94c788afa9a86db8b08304181a0f8f8a966219c5e5db2a2f9e7e47975a52e368a62094c0e5003fe76aa880f07defb1c6135d564ca3f2e04f90b134

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://sas-mtep.deutsche-boerse.com/selfEnrollment/transit.aspx	ASP.NET_SessionId, X-Frame-Options, X-XSS-Protection, Content-Security-Policy, X-Content-Type-Options, Referrer-Policy, TS01d99b39	Set-Cookie: ASP.NET_SessionId=dnoq025fdoqsux2suf4xv12h Set-Cookie: X-Frame-Options= Set-Cookie: X-XSS-Protection= Set-Cookie: Content-Security-Policy= Set-Cookie: X-Content-Type-Options= Set-Cookie: Referrer-Policy= Set-Cookie: TS01d99b39=0123537947cce5f21c84567f17f43c3b0119b57d33d25c9e5d1afbb07d01f10a6efec311bd3e13154b226722ae564688660eb5d36dd649388f6a66b56febdadb790a94c1cdc25930f6ebfee4249f557097a200a1650488e86bad94c788afa9a86db8b08304181a0f8f8a966219c5e5db2a2f9e7e47975a52e368a62094c0e5003fe76aa880f07defb1c6135d564ca3f2e04f90b134

Vulnerability description

We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.

Recommendation

Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.

Classification

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

Evidence

URL	Evidence
https://sas-mtep.deutsche-boerse.com/selfEnrollment/transit.aspx	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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL Evidence

URL	Evidence
https://sas-mtep.deutsche-boerse.com/selfEnrollment/transit.aspx	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. 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'.`

https://sas-mtep.deutsche-boerse.com/selfEnrollment/transit.aspx

Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. 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'.

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
Microsoft ASP.NET	Web frameworks
DigiCert	SSL/TLS certificate authorities

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
Missing: https://sas-mtep.deutsche-boerse.com/.well-known/security.txt

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

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

Evidence

URL	Method	Summary
https://sas-mtep.deutsche-boerse.com/selfEnrollment/transit.aspx	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: OPTIONS, TRACE, GET, HEAD, POST` 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
sas-mtep.deutsche-boerse.com	A	IPv4 address	193.29.71.185

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
Microsoft ASP.NET	Web frameworks
F5 BigIP	Reverse proxies
jQuery	JavaScript libraries
Clipboard.js	JavaScript libraries
DigiCert	SSL/TLS certificate authorities

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.