Vulnerability Scan Result

Target:

https://docs.safegate.network/

Scanned target: https://docs.safegate.network/

Submitted: Nov 02, 2025 from BZ

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Giới thiệu \| SafeGate Office
Description:	SafeGate Office là giải pháp bảo vệ toàn diện hệ thống mạng, giúp giám sát, phân vùng mạng và ngăn chặn các mối nguy an ninh, phù hợp với doanh nghiệp, các đơn vị hành chính.

IP Information

ip_address	104.18.40.47
country	-
network_name	Cloudflare Inc
asn	AS13335

ip_address	172.64.147.209
country	-
network_name	Cloudflare Inc
asn	AS13335

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	cloudflare -
2082/tcp	http	Cloudflare http proxy -
2083/tcp	https	nginx -
2086/tcp	http	Cloudflare http proxy -
2087/tcp	https	nginx -
8080/tcp	http	Cloudflare http proxy -
8443/tcp	http	cloudflare -

Web Technologies

Software / Version	Category
HTTP/3	Miscellaneous
Next.js 15.4.0	JavaScript frameworks, Web frameworks, Web servers, Static site generator
Open Graph	Miscellaneous
React	JavaScript frameworks
Vercel	PaaS
Webpack	Miscellaneous
Priority Hints	Performance
Cloudflare	CDN
GitBook	Documentation
HSTS	Security

Web Application Vulnerabilities

Evidence

URL
https://docs.safegate.network/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

Software / Version	Category
HTTP/3	Miscellaneous
Next.js 15.4.0	JavaScript frameworks, Web frameworks, Web servers, Static site generator
Open Graph	Miscellaneous
React	JavaScript frameworks
Vercel	PaaS
Webpack	Miscellaneous
Priority Hints	Performance
Cloudflare	CDN
GitBook	Documentation
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.

Evidence

URL Evidence

URL	Evidence
https://docs.safegate.network/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). script-src: script-src should not allow '*' as source. This may enable execution of malicious JavaScript. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers.

https://docs.safegate.network/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). script-src: script-src should not allow '*' as source. This may enable execution of malicious JavaScript. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers.

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

Evidence

URL
Missing: https://docs.safegate.network/.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.

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Vercel	PaaS
HSTS	Security
Cloudflare	CDN
HTTP/3	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.

Evidence

Software / Version	Category
Vercel	PaaS
HSTS	Security
Cloudflare	CDN
HTTP/3	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.

Evidence

Software / Version	Category
GitBook	Documentation
Vercel	PaaS
HSTS	Security
Cloudflare	CDN
HTTP/3	Miscellaneous
Priority Hints	Performance

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
Vercel	PaaS
HSTS	Security
Cloudflare	CDN
HTTP/3	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.

Operating System	Accuracy
FreeBSD 11.1-STABLE	91%

Evidence

Domain Queried	DNS Record Type	Description	Value
docs.safegate.network	A	IPv4 address	104.18.40.47
docs.safegate.network	A	IPv4 address	172.64.147.209
docs.safegate.network	AAAA	IPv6 address	2606:4700:4407::6812:282f
docs.safegate.network	AAAA	IPv6 address	2606:4700:4402::ac40:93d1
docs.safegate.network	CAA	Certificate Authority Authorization	0 issue "digicert.com"
docs.safegate.network	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
docs.safegate.network	CAA	Certificate Authority Authorization	0 issue "pki.goog"
docs.safegate.network	CNAME	Canonical name	d03d49c248-hosting.gitbook.io

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.