Vulnerability Scan Result

Target:

https://josephinebakerstraat3.nl/

Scanned target: https://josephinebakerstraat3.nl/

Submitted: May 23, 2025 from PE

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	Te koop: Josephine Bakerstraat 3, Almere \| Online Bedrijfsmakelaar \| Home
Description:	Bezichtig Josephine Bakerstraat 3, Almere - Online Bedrijfsmakelaar nu online!

IP Information

IP address	87.253.157.63
Country	NL
AS number	AS20857
Net name	Signet B.V

Open Ports

80/tcp	http	nginx 1.26.2
443/tcp	https	nginx 1.26.2

Web Technologies

Software / Version	Category
cdnjs	CDN
Font Awesome 6.5.1	Font scripts
Google Analytics	Analytics
Google Font API	Font scripts
Inertia.js	JavaScript frameworks
jQuery 3.3.1	JavaScript libraries
Leaflet 1.7.1	Maps
lit-element 4.2.0	JavaScript libraries
Livefyre 1.7.1	Comment systems
Marko	Web frameworks, UI frameworks
PDF.js	Miscellaneous
Nginx 1.26.2	Web servers, Reverse proxies
Node.js	Programming languages
Open Graph	Miscellaneous
React	JavaScript frameworks
Sentry	Issue trackers
Webpack	Miscellaneous
Chart.js	JavaScript graphics
Cloudflare	CDN
reCAPTCHA	Security
Google Tag Manager	Tag managers
Lodash 4.17.21	JavaScript libraries

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://josephinebakerstraat3.nl/	gary_session	Set-Cookie: gary_session=eyJpdiI6InRYYnpEM2V3blg4OFYzRWx0RmZoZkE9PSIsInZhbHVlIjoiYytNM3p5dnNnVVh5NzJBTzBYT2toME9vbk40dzJRTnYwTFE3V0VxQTVsbEdManVubEJwdEpyRklnSmVVOE1wR0U1M0l2QWJLUGtxbmZPWkE1SGJ3THZ2eU9JNzRMK0hTSWpjekJubWNhd0x1aFk0RUM0cXczc3ZVQ0pNL1VJYzUiLCJtYWMiOiJmNzRiMmI5OTBlNzdkOTcwN2UwNjU1Y2Y1YzAxNmFkZjdhM2E5MmE4MzVjZWYyZmEzNzgyNjVmMTlkY2JkZmVlIiwidGFnIjoiIn0%3D

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

CVSS	CVE	Summary	Affected software
4.3	CVE-2019-11358	jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.	jquery 3.3.1
4.3	CVE-2020-11023	In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.	jquery 3.3.1
4.3	CVE-2020-11022	In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.	jquery 3.3.1

Vulnerability description

We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.

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.

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-1026
OWASP Top 10 - 2017	A9 - Using Components with Known Vulnerabilities
OWASP Top 10 - 2021	A6 - Vulnerable and Outdated Components

Evidence

URL	Evidence
https://josephinebakerstraat3.nl/	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://josephinebakerstraat3.nl/	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
https://josephinebakerstraat3.nl/	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-693
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://josephinebakerstraat3.nl/	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

Software / Version	Category
cdnjs	CDN
Font Awesome 6.5.1	Font scripts
Google Analytics	Analytics
Google Font API	Font scripts
Inertia.js	JavaScript frameworks
jQuery 3.3.1	JavaScript libraries
Leaflet 1.7.1	Maps
lit-element 4.2.0	JavaScript libraries
Livefyre 1.7.1	Comment systems
Marko	Web frameworks, UI frameworks
PDF.js	Miscellaneous
Nginx 1.26.2	Web servers, Reverse proxies
Node.js	Programming languages
Open Graph	Miscellaneous
React	JavaScript frameworks
Sentry	Issue trackers
Webpack	Miscellaneous
Chart.js	JavaScript graphics
Cloudflare	CDN
reCAPTCHA	Security
Google Tag Manager	Tag managers
Lodash 4.17.21	JavaScript libraries

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://josephinebakerstraat3.nl/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
Missing: https://josephinebakerstraat3.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

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

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
josephinebakerstraat3.nl	A	IPv4 address	87.253.157.63
josephinebakerstraat3.nl	NS	Name server	ns0.transip.net
josephinebakerstraat3.nl	NS	Name server	ns1.transip.nl
josephinebakerstraat3.nl	NS	Name server	ns2.transip.eu
josephinebakerstraat3.nl	SOA	Start of Authority	ns0.transip.net. hostmaster.transip.nl. 2025052300 86400 1800 2419200 300
josephinebakerstraat3.nl	AAAA	IPv6 address	2a01:7c8:bb07:91:5054:ff:fe99:e43d
josephinebakerstraat3.nl	TXT	Text record	"\"v=spf1 include:_spf.transip.email a mx ip4:185.182.56.120 ip4:185.232.250.222 ip4:185.232.250.186 ~all\""
josephinebakerstraat3.nl	CAA	Certificate Authority Authorization	0 issuewild "letsencrypt.org"

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.