Vulnerability Scan Result

Target:

http://t.marketing.dvv.be/r/?id=h1273cd77,1ec52993,412e7ef&e=cDE9MDc3NjExOTYwMzU&s=mJZWSccsXCO_rqT27IcHv0RtFXEDcc6_6dpnNKR9xJA (redirect)

Scanned target: https://www.dvv.be/nl/verzekeringen/reizen/artikelen/vertraging-annulering-of-verloren-bagage-op-skivakantie-ken-je-rechten.html?utm_source=int_news&utm_medium=email&utm_campaign=202602&utm_content=cta_2&psiAdb=07761196035&deliveryName=DM53887

Submitted: Mar 24, 2026 from LI

Public Scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Problemen op skivakantie? Dit zijn je rechten \| DVV verzekeringen, gewoon goeie service
Description:	Skivakantie verstoord door een geannuleerde vlucht, een bus die niet vertrekt of verloren bagage? Ontdek met DVV je rechten en de juiste stappen.

IP Information

ip_address	141.96.1.55
country	BE
network_name	Proximus Luxembourg S.A.
asn	AS25367

Open Ports

80/tcp	tcpwrapped	- -
443/tcp	tcpwrapped	- -

Web Technologies

Software / Version	Category
AngularJS 1.6.4	JavaScript frameworks
Adobe Experience Platform Identity Service	Customer data platform
Adobe Experience Platform Launch	Tag managers
Hammer.js 2.0.7	JavaScript libraries
Java	Programming languages
jQuery	JavaScript libraries
lit-element 4.1.1	JavaScript libraries
Google Maps	Maps
AOS	JavaScript libraries
Moment.js 2.18.1	JavaScript libraries
Open Graph	Miscellaneous
PWA	Miscellaneous
Adobe Analytics	Analytics
Adobe Experience Manager	CMS
Chart.js	JavaScript graphics
DigiCert	SSL/TLS certificate authorities
reCAPTCHA	Security
OneTrust	Cookie compliance
ServiceNow	Miscellaneous

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2024-21490	7.5	0.02307	0.84595	This affects versions of the package angular from 1.3.0. A regular expression used to split the value of the ng-srcset directive is vulnerable to super-linear runtime due to backtracking. With large carefully-crafted input, this can result in catastrophic backtracking and cause a denial of service. Note: This package is EOL and will not receive any updates to address this issue. Users should migrate to [@angular/core](https://www.npmjs.com/package/@angular/core).

Vulnerability description

Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.

Risk description

The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1035
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2022-31129	7.5	0.03435	0.87367	moment is a JavaScript date library for parsing, validating, manipulating, and formatting dates. Affected versions of moment were found to use an inefficient parsing algorithm. Specifically using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs. Users may notice a noticeable slowdown is observed with inputs above 10k characters. Users who pass user-provided strings without sanity length checks to moment constructor are vulnerable to (Re)DoS attacks. The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking. Users are advised to upgrade. Users unable to upgrade should consider limiting date lengths accepted from user input.
CVE-2022-24785	7.5	0.02256	0.84436	Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.
CVE-2017-18214	7.5	0.00421	0.61766	The moment module before 2.19.3 for Node.js is prone to a regular expression denial of service via a crafted date string, a different vulnerability than CVE-2016-4055.

Vulnerability description

Risk description

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1035
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Cookie Name	Evidence
https://www.dvv.be/nl/verzekeringen/reizen/artikelen/vertraging-annulering-of-verloren-bagage-op-skivakantie-ken-je-rechten.html	TS011fcb94	Set-Cookie: .www.dvv.be

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
OWASP Top 10 - 2021

Evidence

URL	Cookie Name	Evidence
https://www.dvv.be/nl/verzekeringen/reizen/artikelen/vertraging-annulering-of-verloren-bagage-op-skivakantie-ken-je-rechten.html	TS011fcb94	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: TS011fcb94=0138b002f53fe9c0cf2925049c12c3d925714605e412b342b74561ad8a0fecf8871bccc24a31abe51dbee700cd0ebdd8d91eeb0d4a

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
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://www.dvv.be/nl/verzekeringen/reizen/artikelen/vertraging-annulering-of-verloren-bagage-op-skivakantie-ken-je-rechten.html	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
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://www.dvv.be/nl/verzekeringen/reizen/artikelen/vertraging-annulering-of-verloren-bagage-op-skivakantie-ken-je-rechten.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
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://www.dvv.be/nl/verzekeringen/reizen/artikelen	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
https://www.dvv.be/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.dvv.be/nl/verzekeringen/reizen/artikelen/vertraging-annulering-of-verloren-bagage-op-skivakantie-ken-je-rechten.html	Response does not include the HTTP Content-Security-Policy security header or meta tag

Vulnerability description

We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.

Risk description

The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.

Recommendation

Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.

Classification

CWE	CWE-1021
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
AngularJS 1.6.4	JavaScript frameworks
Adobe Experience Platform Identity Service	Customer data platform
Adobe Experience Platform Launch	Tag managers
Hammer.js 2.0.7	JavaScript libraries
Java	Programming languages
jQuery	JavaScript libraries
lit-element 4.1.1	JavaScript libraries
Google Maps	Maps
AOS	JavaScript libraries
Moment.js 2.18.1	JavaScript libraries
Open Graph	Miscellaneous
PWA	Miscellaneous
Adobe Analytics	Analytics
Adobe Experience Manager	CMS
Chart.js	JavaScript graphics
DigiCert	SSL/TLS certificate authorities
reCAPTCHA	Security
OneTrust	Cookie compliance
ServiceNow	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.

Classification

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

Evidence

URL
Missing: https://www.dvv.be/nl/.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

CWE	CWE-1188
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Summary
https://www.dvv.be/nl/verzekeringen/reizen/artikelen/vertraging-annulering-of-verloren-bagage-op-skivakantie-ken-je-rechten.html?deliveryName=DM53887&psiAdb=07761196035&utm_campaign=202602&utm_content=cta_2&utm_medium=email&utm_source=int_news	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: OPTIONS, TRACE, 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

Evidence

Domain Queried	DNS Record Type	Description	Value
www.dvv.be	A	IPv4 address	141.96.1.55

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.