Vulnerability Scan Result

Target:

http://www.hsxzf.gov.cn/ (redirect)

Scanned target: https://www.hsxzf.gov.cn/

Submitted: Feb 16, 2026 from ML

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	合水县人民政府
Description:	No description found

IP Information

ip_address	117.157.184.131
country	CN
network_name	China Mobile Communications Group Co., Ltd.
asn	AS9808

Open Ports

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

Web Technologies

Software / Version	Category
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://www.hsxzf.gov.cn/	Power::SiteUniqueVisitorKey	Set-Cookie: Power::SiteUniqueVisitorKey=/1/

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

Evidence

Software / Version	Category
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://www.hsxzf.gov.cn/	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' only. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. 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'.

https://www.hsxzf.gov.cn/

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' only. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. 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'.

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	Method	Parameters	Evidence
https://www.hsxzf.gov.cn/	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: ` 手机号码短信验证码 <div class="phonemessagevalidate" data-type="phonemessagevalidate" data-val-basis... (truncated)
https://www.hsxzf.gov.cn/petition/943	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: Power::SiteUniqueVisitorKey=/1/ __RequestVerificationToken=WbzMNO-ff7n2hcSOY4C3MHvOPvsgX6xlrMzYtDfQThNJtlbHiDSJWoz8YUPeYSJD5A7Fnw2	The following form sends inputs of type password plainly in the URL: ` 手机号码短信验证码 <div class="phonemessagevalidate" data-type="phonemessagevalidate" data-val-bas... (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.

Evidence

URL	Method	Parameters	Evidence
https://www.hsxzf.gov.cn/letterbox/	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: Power::SiteUniqueVisitorKey=/1/ __RequestVerificationToken=WbzMNO-ff7n2hcSOY4C3MHvOPvsgX6xlrMzYtDfQThNJtlbHiDSJWoz8YUPeYSJD5A7Fnw2	Response has an internal server error status code: 500

Vulnerability description

We noticed that the target application's website does not properly handle or incorrectly manages exceptional conditions like Internal Server Errors. These errors can reveal sensitive information through their error messages. For instance, an error message could inadvertently disclose system paths or private application details.

Risk description

The risk exists that attackers could utilize information revealed in Internal Server Error messages to mount more targeted and effective attacks. Detailed error messages could, for example, expose a path traversal weakness (CWE-22) or other exploitable system vulnerabilities.

Recommendation

Ensure that error messages only contain minimal details that are useful to the intended audience, and nobody else. The messages need to strike the balance between being too cryptic and not being cryptic enough. They should not necessarily reveal the methods that were used to determine the error. Such detailed information can be used to refine the original attack to increase the chances of success. If errors must be tracked in some detail, capture them in log messages - but consider what could occur if the log messages can be viewed by attackers. Avoid recording highly sensitive information such as passwords in any form. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a username is valid or not.

Classification

CWE	CWE-209
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://www.hsxzf.gov.cn/.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.

Evidence

URL Evidence

URL	Evidence
https://www.hsxzf.gov.cn/	<input id="UserName" class="form-control hiddenfield password-field" data-val-required="用户名字段是必需的。" data-val="true" name="UserName" type="text" value=""> <input id="Password" style="width: 49%" data-val-required="密码字段是必需的。" autocomplete="off" class="form-control hiddenfield password-field phonepassword-field" data-toggle="password" data-ui-ime="inactive" data-val="true" data-val-dangerous="true" data-val-length-max="32" data-val-length-min="6" maxlength="32" name="Password" type="password"> <button type="button" class="login loginBtn">登录</button>

https://www.hsxzf.gov.cn/

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

Software / Version	Category
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.

Operating System	Accuracy
Linux 2.6.32	97%

Evidence

Domain Queried	DNS Record Type	Description	Value
www.hsxzf.gov.cn	A	IPv4 address	117.157.184.131
www.hsxzf.gov.cn	AAAA	IPv6 address	2409:8774:7e7f::7

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.