Vulnerability Scan Result

Target:

http://janjitoto5.com/

Scanned target: http://janjitoto5.com/

Submitted: May 30, 2025 from MA

Public Scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

Title:	JANJITOTO: Greatest Games Most Popular 2025
Description:	JanjiToto is the greatest most popular site 2025 in Indonesia. Provides a login link that is sure to win.

IP Information

IP address	92.243.74.2
Country	SG
AS number	-
Net name	-

IP address	92.243.74.3
Country	SG
AS number	-
Net name	-

Open Ports

2082/tcp	http	Cloudflare http proxy -
2083/tcp	https	nginx -
2086/tcp	http	Cloudflare http proxy -
2087/tcp	https	nginx -

Web Technologies

Software / Version	Category
Twitter Ads	Advertising
Animate.css	UI frameworks
Bunny	CDN
cdnjs	CDN
Facebook Pixel 2.9.203	Analytics
Font Awesome	Font scripts
Bootstrap 3.2.0	UI frameworks
core-js 3.32.2	JavaScript libraries
Google Analytics GA4	Analytics
jQuery 2.2.4	JavaScript libraries
Slick 1.8.1	JavaScript libraries
Lightbox	JavaScript libraries
Modernizr 2.6.2	JavaScript libraries
OWL Carousel	JavaScript libraries
Skrollr 0.6.22	JavaScript libraries
Svelte	JavaScript frameworks
Twitter	Widgets
AMP	JavaScript frameworks
Cloudflare	CDN
Cloudflare Bot Management	Security
Google Tag Manager	Tag managers
LiveChat	Live chat

Web Application Vulnerabilities

Evidence

CVSS	CVE	Summary	Affected software
6.4	CVE-2024-6484	A vulnerability has been identified in Bootstrap that exposes users to Cross-Site Scripting (XSS) attacks. The issue is present in the carousel component, where the data-slide and data-slide-to attributes can be exploited through the href attribute of an <a> tag due to inadequate sanitization. This vulnerability could potentially enable attackers to execute arbitrary JavaScript within the victim's browser.	bootstrap 3.2.0
4.3	CVE-2018-14040	In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute.	bootstrap 3.2.0
4.3	CVE-2018-14042	In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.	bootstrap 3.2.0
4.3	CVE-2016-10735	In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute, a different vulnerability than CVE-2018-14041.	bootstrap 3.2.0
4.3	CVE-2018-20676	In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.	bootstrap 3.2.0
4.3	CVE-2015-9251	jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.	jquery 2.2.4
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 2.2.4
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 2.2.4
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 2.2.4

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

Evidence

URL	Response URL	Evidence
http://janjitoto5.com/	http://janjitoto5.com/	Communication is made over unsecure, unencrypted HTTP.

Vulnerability description

We noticed that the communication between the web browser and the server is done using the HTTP protocol, which transmits data unencrypted over the network.

Risk description

The risk is that an attacker who manages to intercept the communication at the network level can read and modify the data transmitted (including passwords, secret tokens, credit card information and other sensitive data).

Recommendation

We recommend you to reconfigure the web server to use HTTPS - which encrypts the communication between the web browser and the server.

Classification

CWE	CWE-311
OWASP Top 10 - 2017	A3 - Sensitive Data Exposure
OWASP Top 10 - 2021	A4 - Insecure Design

Evidence

URL	Cookie Name	Evidence
http://janjitoto5.com/	SRVNAME	Set-Cookie: SRVNAME=71

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

URL	Evidence
http://janjitoto5.com/	Password input detected over insecure HTTP. Login form: <form onsubmit="md5nohash(entered_password, vb_login_md5password, vb_login_md5password_utf, 0)"> <script src="/js/vbulletin_md5.js" type="text/javascript"></script> <div class="form-group col-sm-2" data-0="margin-top: 24px;" data-300="margin-top: 7px;"> <input autocomplete="off" class="form-control" id="navbar_username" name="entered_login" placeholder="Username" tabindex="1" type="text"/> </div> <div class="form-group col-sm-2" data-0="margin-top: 24px;" data-300="margin-top: 7px;"> <input autocomplete="off" class="form-control" id="navbar_password" name="entered_password" placeholder="Password" tabindex="2" type="password"/> </div> <button class="btn btn-theme login" id="submitlogin" name="submitlogin" type="submit" value="1">LOGIN</button> <input id="vb_login_md5password" name="vb_login_md5password" type="hidden"/> <input name="vb_login_md5password_utf" type="hidden"/> <input name="submitlogin" type="hidden" value="1"/> </form>

http://janjitoto5.com/

Password input detected over insecure HTTP. Login form: <form onsubmit="md5nohash(entered_password, vb_login_md5password, vb_login_md5password_utf, 0)"> <script src="/js/vbulletin_md5.js" type="text/javascript"></script> <div class="form-group col-sm-2" data-0="margin-top: 24px;" data-300="margin-top: 7px;"> <input autocomplete="off" class="form-control" id="navbar_username" name="entered_login" placeholder="Username" tabindex="1" type="text"/> </div> <div class="form-group col-sm-2" data-0="margin-top: 24px;" data-300="margin-top: 7px;"> <input autocomplete="off" class="form-control" id="navbar_password" name="entered_password" placeholder="Password" tabindex="2" type="password"/> </div> <button class="btn btn-theme login" id="submitlogin" name="submitlogin" type="submit" value="1">LOGIN</button> <input id="vb_login_md5password" name="vb_login_md5password" type="hidden"/> <input name="vb_login_md5password_utf" type="hidden"/> <input name="submitlogin" type="hidden" value="1"/> </form>

Vulnerability description

We found that passwords are transmitted over a network without encryption. When users submit their passwords through an application or system, the lack of encryption means that the sensitive information is transmitted in plaintext, making it susceptible to interception and unauthorized access.

Risk description

The risk is that malicious actors could employ various techniques, such as packet sniffing or man-in-the-middle attacks, to capture plaintext passwords. Once intercepted, the attacker gains unauthorized access to user accounts, potentially leading to identity theft, unauthorized data access, or other malicious activities. The risk remains unchanged even if the password's form submission triggers a redirect response to an HTTPS page.

Recommendation

We recommend you to reconfigure the web server so it uses HTTPS - which encrypts the communication between the web browser and the server. This way, the attacker will not be able to obtain the clear-text passwords, even though he manages to intercept the network communication.

Classification

CWE	CWE-523
OWASP Top 10 - 2017	A3 - Sensitive Data Exposure
OWASP Top 10 - 2021	A2 - Cryptographic Failures

Evidence

URL	Cookie Name	Evidence
http://janjitoto5.com/	SRVNAME	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: SRVNAME=71

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	Evidence
http://janjitoto5.com/	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

URL	Evidence
http://janjitoto5.com/	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	Method	Parameters	Evidence
http://janjitoto5.com/	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	The following form sends inputs of type password plainly in the URL: <form onsubmit="md5nohash(entered_password, vb_login_md5password, vb_login_md5password_utf, 0)"> <script src="/js/vbulletin_md5.js" type="text/javascript"> </script> <div class="form-group col-sm-2" data-0="margin-top: 24px;" data-300="margin-top: 7px;"> <input autocomplete="off" class="form-control" id="navbar_username" name="entered_login" placeholder="Username" tabindex="1" type="text"/> </div> <div class="form-group col-sm-2" data-0="margin-top: 24px;" data-300="margin-top: 7px;"> <input autocomplete="off" class="form-control" id="navbar_password" name="entered_password" placeholder="Password" tabindex="2" type="password"/> </div> <button class="btn btn-theme login" id="submitlogin" name="submitlogin" type="submit" value="1"> LOGIN </button> <input id="vb_login_md5password" name="vb_login_md5password" type="hidden"/> <input name="vb_login_md5password_utf" type="hidden"/> <input name="submitlogin" type="hidden" value="1"/> </form>
http://janjitoto5.com/history/	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: SRVNAME=60i __cf_bm=fiBqD5pGA8m3GQX0mbazchoLmqWEXoXDltxScHi0g4A-1748617765-1.0.1.1-5QNKtxg0jO3jQWLgHDxqTHGMYrx72BYgdNxlf1BRPwhCz2GHj8XSpCZD1WL...	The following form sends inputs of type password plainly in the URL: <form onsubmit="md5nohash(entered_password, vb_login_md5password, vb_login_md5password_utf, 0)"> <script src="/js/vbulletin_md5.js" type="text/javascript"> </script> <div class="form-group col-sm-2" data-0="margin-top: 24px;" data-300="margin-top: 7px;"> <input autocomplete="off" class="form-control" id="navbar_username" name="entered_login" placeholder="Username" tabindex="1" type="text"/> </div> <div class="form-group col-sm-2" data-0="margin-top: 24px;" data-300="margin-top: 7px;"> <input autocomplete="off" class="form-control" id="navbar_password" name="entered_password" placeholder="Password" tabindex="2" type="password"/> </div> <button class="btn btn-theme login" id="submitlogin" name="submitlogin" type="submit" value="1"> LOGIN </button> <input id="vb_login_md5password" name="vb_login_md5password" type="hidden"/> <input name="vb_login_md5password_utf" type="hidden"/> <input name="submitlogin" type="hidden" value="1"/> </form>
http://janjitoto5.com/history/number	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: SRVNAME=60i __cf_bm=fiBqD5pGA8m3GQX0mbazchoLmqWEXoXDltxScHi0g4A-1748617765-1.0.1.1-5QNKtxg0jO3jQWLgHDxqTHGMYrx72BYgdNxlf1BRPwhCz2GHj8XSpCZD1WL...	The following form sends inputs of type password plainly in the URL: <form onsubmit="md5nohash(entered_password, vb_login_md5password, vb_login_md5password_utf, 0)"> <script src="/js/vbulletin_md5.js" type="text/javascript"> </script> <div class="form-group col-sm-2" data-0="margin-top: 24px;" data-300="margin-top: 7px;"> <input autocomplete="off" class="form-control" id="navbar_username" name="entered_login" placeholder="Username" tabindex="1" type="text"/> </div> <div class="form-group col-sm-2" data-0="margin-top: 24px;" data-300="margin-top: 7px;"> <input autocomplete="off" class="form-control" id="navbar_password" name="entered_password" placeholder="Password" tabindex="2" type="password"/> </div> <button class="btn btn-theme login" id="submitlogin" name="submitlogin" type="submit" value="1"> LOGIN </button> <input id="vb_login_md5password" name="vb_login_md5password" type="hidden"/> <input name="vb_login_md5password_utf" type="hidden"/> <input name="submitlogin" type="hidden" value="1"/> </form>
http://janjitoto5.com/rules-game	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: SRVNAME=60i __cf_bm=fiBqD5pGA8m3GQX0mbazchoLmqWEXoXDltxScHi0g4A-1748617765-1.0.1.1-5QNKtxg0jO3jQWLgHDxqTHGMYrx72BYgdNxlf1BRPwhCz2GHj8XSpCZD1WL...	The following form sends inputs of type password plainly in the URL: <form onsubmit="md5nohash(entered_password, vb_login_md5password, vb_login_md5password_utf, 0)"> <script src="/js/vbulletin_md5.js" type="text/javascript"> </script> <div class="form-group col-sm-2" data-0="margin-top: 24px;" data-300="margin-top: 7px;"> <input autocomplete="off" class="form-control" id="navbar_username" name="entered_login" placeholder="Username" tabindex="1" type="text"/> </div> <div class="form-group col-sm-2" data-0="margin-top: 24px;" data-300="margin-top: 7px;"> <input autocomplete="off" class="form-control" id="navbar_password" name="entered_password" placeholder="Password" tabindex="2" type="password"/> </div> <button class="btn btn-theme login" id="submitlogin" name="submitlogin" type="submit" value="1"> LOGIN </button> <input id="vb_login_md5password" name="vb_login_md5password" type="hidden"/> <input name="vb_login_md5password_utf" type="hidden"/> <input name="submitlogin" type="hidden" value="1"/> </form>

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
http://janjitoto5.com/	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

Software / Version	Category
Twitter Ads	Advertising
Animate.css	UI frameworks
Bunny	CDN
cdnjs	CDN
Facebook Pixel 2.9.203	Analytics
Font Awesome	Font scripts
Bootstrap 3.2.0	UI frameworks
core-js 3.32.2	JavaScript libraries
Google Analytics GA4	Analytics
jQuery 2.2.4	JavaScript libraries
Slick 1.8.1	JavaScript libraries
Lightbox	JavaScript libraries
Modernizr 2.6.2	JavaScript libraries
OWL Carousel	JavaScript libraries
Skrollr 0.6.22	JavaScript libraries
Svelte	JavaScript frameworks
Twitter	Widgets
AMP	JavaScript frameworks
Cloudflare	CDN
Cloudflare Bot Management	Security
Google Tag Manager	Tag managers
LiveChat	Live chat

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
http://janjitoto5.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).

Classification

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

Evidence

URL	Evidence
http://janjitoto5.com/	`<input autocomplete="off" class="form-control" id="navbar_username" name="entered_login" placeholder="Username" tabindex="1" type="text"/> <input autocomplete="off" class="form-control" id="navbar_password" name="entered_password" placeholder="Password" tabindex="2" type="password"/> <button class="btn btn-theme login" id="submitlogin" name="submitlogin" type="submit" value="1">LOGIN</button>`

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.

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
janjitoto5.com	A	IPv4 address	92.243.74.2
janjitoto5.com	A	IPv4 address	92.243.74.3
janjitoto5.com	NS	Name server	fish.ns.cloudflare.com
janjitoto5.com	NS	Name server	malcolm.ns.cloudflare.com
janjitoto5.com	SOA	Start of Authority	fish.ns.cloudflare.com. dns.cloudflare.com. 2373559582 10000 2400 604800 1800

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
Crestron XPanel control system	92%

Evidence

Software / Version	Category
Cloudflare Browser Insights	Analytics, RUM
Cloudflare Bot Management	Security
Cloudflare	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.

Evidence

Software / Version	Category
Cloudflare Browser Insights	Analytics, RUM
Cloudflare Bot Management	Security
Cloudflare	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.

Evidence

Software / Version	Category
Cloudflare Browser Insights	Analytics, RUM
Cloudflare Bot Management	Security
Cloudflare	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.

Evidence

Software / Version	Category
Cloudflare Browser Insights	Analytics, RUM
Cloudflare Bot Management	Security
Cloudflare	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.