Vulnerability Scan Result

Target:

https://mydhl.express.dhl/be/en/shipment.html?shipmentId=73dd5922-55b9-43ea-9938-33a9a46b4592

Scanned target: https://mydhl.express.dhl/be/en/shipment.html?shipmentId=73dd5922-55b9-43ea-9938-33a9a46b4592

Submitted: May 23, 2025 from MV

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

https://mydhl.express.dhl/be/en/shipment.html?shipmentId=73dd5922-55b9-43ea-9938-33a9a46b4592

Title:	Create a Shipment \| DHL Express Shipping Labels \| MyDHL+
Description:	Create shipping, package labels and customs invoice. Get DHL Express shipping rate quotes, find shipping services and schedule a courier pickup in MyDHL+

IP Information

IP address	2.18.64.6
Country	DE
AS number	AS20940
Net name	Akamai International B.V

IP address	2.18.64.24
Country	DE
AS number	AS20940
Net name	Akamai International B.V

Open Ports

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

Web Technologies

Software / Version	Category
Akamai	CDN
Nginx	Web servers, Reverse proxies
Akamai Bot Manager	Security
DigiCert	SSL/TLS certificate authorities
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://mydhl.express.dhl/be/en/shipment.html	_abck, bm_sz	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: _abck=11C070BE0B9AA19FF9A81F26A48C2044-1YAAQtsJkX6rQgMSWAQAA6ZG8/A0vpKj7DRhwZH57B56Z7ye9jA6W+aseF3bWGRI3sLZTCo+OwlNgePpQMh60KUKpcgPLRHk+nTFnvhRcnfgybdYbao0D+IoIULWBlBZlRFsJ7OL2Ha7INOT/VDWnQnNMt+tGYUpBhi3HYIPh7a9Z3uwcbCFU+gn5aca6ttAlvLZ3sZYJGJRiwpJHnOL09ekxEGdoXjlLSGzbk1WEZNWdbiMLmz/lfXEP6ec/2M3BvEIUbeAQBvkafR3ttwG05zmbnrRI6EeGS5ch4NGbckoMkgwFUGwIUVFUUVmykCUNQCNZm2IjrlEHs53+GTZqGSbrSH1SYtdL3cqA+gC0VRm2c6sWWKR05KHSgMbFs8QACPiJFgeBH+uXhyHg3TeaNzvmWsRpv9l/bHdRHmdeFgNtbKQV4oIoQjd4HFKisOb9sV7yhts=-1-1~~-1 Set-Cookie: bm_sz=280D961F627ACB4D933C19E1DB1E3808~~YAAQtsJkX6vQgMSWAQAA6ZG8/BtoK0XMNxnsmB7ePQ6zry1Wdk9T2956L0N3+6PJkbVbU2CGlOxwAz0a4MQKH/6KR5T4WalTpSf0azb1FCrE9bippvj8SqJ2ycWT6oqCiTS2EfeMDBn2kkXXKB6jkpGGxsXEeaRs3bQMmLZ2hAAtOcO6gyCc+ZIkzxkXEmTZFQbFM3ggtDBzflvJlEyXYAGImnkOtebbnTrQJBKPWO3yiJS7M0Gp8HBqBoH1bC9MPhGmt5ZKcT6/PKvCW/EM3g/+JxiAxni8Oqi9zCZdBSq7dSRZgkNBtQirZPbB+2k2SQo6vrE4Azq+Ts7e5U+p1vwQh/IP77QC8Hfbhp7b~~4339766~~3424821

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://mydhl.express.dhl/be/en/shipment.html	bm_sz	Set-Cookie: bm_sz=280D961F627ACB4D933C19E1DB1E3808YAAQtsJkX6vQgMSWAQAA6ZG8/BtoK0XMNxnsmB7ePQ6zry1Wdk9T2956L0N3+6PJkbVbU2CGlOxwAz0a4MQKH/6KR5T4WalTpSf0azb1FCrE9bippvj8SqJ2ycWT6oqCiTS2EfeMDBn2kkXXKB6jkpGGxsXEeaRs3bQMmLZ2hAAtOcO6gyCc+ZIkzxkXEmTZFQbFM3ggtDBzflvJlEyXYAGImnkOtebbnTrQJBKPWO3yiJS7M0Gp8HBqBoH1bC9MPhGmt5ZKcT6/PKvCW/EM3g/+JxiAxni8Oqi9zCZdBSq7dSRZgkNBtQirZPbB+2k2SQo6vrE4Azq+Ts7e5U+p1vwQh/IP77QC8Hfbhp7b4339766~3424821

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	Cookie Name	Evidence
https://mydhl.express.dhl/be/en/shipment.html	_abck	Set-Cookie: .express.dhl

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	Method	Parameters	Evidence
https://mydhl.express.dhl/be/en/help-and-support.html	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 Cookies: _abck=B7AE701064F86ECA7E70BFEFD22074DD~-1~YAAQjMJkXyEY0tGWAQAAc7G8/A3HsQ/YA5nU9dXq3i2Y+/FlZTT6bSZWNf5yvQAAjS+pyQxKZWphSYHYgYp6wEJ8QQawgcaDpx8P...	The following form sends inputs of type password plainly in the URL: ` ... (truncated)
https://mydhl.express.dhl/be/en/ship/optional-services.html	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 Cookies: _abck=B7AE701064F86ECA7E70BFEFD22074DD~-1~YAAQjMJkXyEY0tGWAQAAc7G8/A3HsQ/YA5nU9dXq3i2Y+/FlZTT6bSZWNf5yvQAAjS+pyQxKZWphSYHYgYp6wEJ8QQawgcaDpx8P...	The following form sends inputs of type password plainly in the URL: ` ... (truncated)
https://mydhl.express.dhl/be/en/shipment.html	GET	Query: shipmentId=73dd5922-55b9-43ea-9938-33a9a46b4592 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	The following form sends inputs of type password plainly in the URL: ` ... (truncated)

Vulnerability description

We found a form which is submitted using a GET method and has inputs of the type password. The end result is that passwords are submitted in URLs.

Risk description

Passwords submitted in URLs have a higher chance of being leaked. The main reason is that URLs can be leaked in browser cross-site requests via the Referer header. Additionally, URLs are usually stored in all kinds of logs. If any access or error logs of the server were publicly accessible, an attacker could also harvest password from it.

Recommendation

You should submit passwords using POST rather than GET. This way sensitive data won't be shared to other locations via URLs.

Classification

OWASP Top 10 - 2017
OWASP Top 10 - 2021	A4 - Insecure Design

Evidence

URL	Evidence
https://mydhl.express.dhl/be/en/shipment.html	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

URL	Evidence
https://mydhl.express.dhl/be/en/shipment.html	Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). object-src: We recommend restricting object-src to 'none'. default-src: https: 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'. default-src: data: URI in default-src allows the execution of unsafe scripts. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: http: URI in default-src allows the execution of unsafe scripts. default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files.

https://mydhl.express.dhl/be/en/shipment.html

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). object-src: We recommend restricting object-src to 'none'. default-src: https: 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'. default-src: data: URI in default-src allows the execution of unsafe scripts. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: http: URI in default-src allows the execution of unsafe scripts. default-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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

Software / Version	Category
Akamai	CDN
Nginx	Web servers, Reverse proxies
Akamai Bot Manager	Security
DigiCert	SSL/TLS certificate authorities
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.

Classification

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

Evidence

URL
https://mydhl.express.dhl/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 Evidence

URL	Evidence
https://mydhl.express.dhl/be/en/shipment.html	<input aqa-id="loginFormUserNameField" autocomplete="off" autofocus="" class="input input_width_full required fancy-form-input" ewf-input="" ewf-input-no-char-validation="true" ewf-validate-email="" ewf-validate-required="" ewf-validate-required-message="Email address required" ewf-watch-input-value="" id="popup_form_username" name="username" ng-model="loginCtrl.username" ng-model-options="{updateOn: 'blur'}" type="email"/> <input aqa-id="loginFormPasswordField" autocomplete="off" class="input input_width_full required fancy-form-input" ewf-input="" ewf-input-no-char-validation="true" ewf-input-password="" ewf-validate-length="" ewf-validate-length-max="35" ewf-validate-length-message="Invalid format" ewf-validate-pattern="PASSWORD" ewf-validate-pattern-message="Invalid format" ewf-validate-required="" ewf-validate-required-message="Required" ewf-watch-input-value="" id="popup_form_password" name="password" ng-model="loginCtrl.password" ng-model-options="{ updateOn: 'blur input'}" type="password"/> <a aqa-id="guestLoginButton" aria-expanded="{{!toggleSwitchCtrl.collapsed}}" class="top-nav__link v2-top-nav__link" data-tracking="{'type':'dhlTopNavMenuGuest','title':{'en': 'Login guest'}}" id="loginButton" ng-click="toggleSwit... (truncated)

https://mydhl.express.dhl/be/en/shipment.html

<input aqa-id="loginFormUserNameField" autocomplete="off" autofocus="" class="input input_width_full required fancy-form-input" ewf-input="" ewf-input-no-char-validation="true" ewf-validate-email="" ewf-validate-required="" ewf-validate-required-message="Email address required" ewf-watch-input-value="" id="popup_form_username" name="username" ng-model="loginCtrl.username" ng-model-options="{updateOn: 'blur'}" type="email"/> <input aqa-id="loginFormPasswordField" autocomplete="off" class="input input_width_full required fancy-form-input" ewf-input="" ewf-input-no-char-validation="true" ewf-input-password="" ewf-validate-length="" ewf-validate-length-max="35" ewf-validate-length-message="Invalid format" ewf-validate-pattern="PASSWORD" ewf-validate-pattern-message="Invalid format" ewf-validate-required="" ewf-validate-required-message="Required" ewf-watch-input-value="" id="popup_form_password" name="password" ng-model="loginCtrl.password" ng-model-options="{ updateOn: 'blur input'}" type="password"/> <a aqa-id="guestLoginButton" aria-expanded="{{!toggleSwitchCtrl.collapsed}}" class="top-nav__link v2-top-nav__link" data-tracking="{'type':'dhlTopNavMenuGuest','title':{'en': 'Login guest'}}" id="loginButton" ng-click="toggleSwit... (truncated)

Vulnerability description

We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.

Risk description

The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.

Recommendation

Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.

Evidence

URL	Method	Parameters	Evidence
https://mydhl.express.dhl/be/en/shipment.html	GET	Query: shipmentId=73dd5922-55b9-43ea-9938-33a9a46b4592 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	Operating system paths found in the HTTP response: `/etc/clientlibs/dhl/global/public/js/lib/angular/ckeditor`

Vulnerability description

We found operating system paths returned in a HTTP response.

Risk description

The risk is that path disclosure may help an attacker learn more about the remote server's file system, thus increasing the effectiveness and precision of any future attacks.

Recommendation

Configure the web server to avoid leaking path information by using generic error messages that do not reveal any internal file paths. Make sure no server file is referred with its absolute path in the website code.

Classification

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

Evidence

URL	Method	Parameters	Evidence
https://mydhl.express.dhl/be/en/help-and-support.html	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 Cookies: _abck=B7AE701064F86ECA7E70BFEFD22074DD~-1~YAAQjMJkXyEY0tGWAQAAc7G8/A3HsQ/YA5nU9dXq3i2Y+/FlZTT6bSZWNf5yvQAAjS+pyQxKZWphSYHYgYp6wEJ8QQawgcaDpx8P...	Email Address: samedaybelgiumcs@dhl.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	A6: Security Misconfiguration
OWASP Top 10 - 2021	A4: Insecure Design

Evidence

URL
Missing: https://mydhl.express.dhl/.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://mydhl.express.dhl/be/en/shipment.html?shipmentId=73dd5922-55b9-43ea-9938-33a9a46b4592	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
mydhl.express.dhl	A	IPv4 address	95.100.110.9
mydhl.express.dhl	A	IPv4 address	95.100.110.8
mydhl.express.dhl	CNAME	Canonical name	mydhl.express.dhl.new.edgekey.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.

Operating System	Accuracy
Linux 4.15 - 5.6	100%

Evidence

Software / Version	Category
Adobe Experience Manager	CMS
Java	Programming languages
Nginx	Web servers, Reverse proxies
OneTrust	Cookie compliance
jQuery	JavaScript libraries
Akamai Bot Manager	Security
HSTS	Security
DigiCert	SSL/TLS certificate authorities
Akamai	CDN

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.