Vulnerability Scan Result

Target:

https://liu.lqclu.cn/

Scanned target: https://liu.lqclu.cn/

Submitted: Jul 17, 2025 from BT

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	No title found
Description:	小鹅通，为内容创业者提供技术支持，一分钟搭建自己的知识变现平台。服务自媒体、传统媒体、出版社、在线教育机构、线下培训机构以及知识盈余的个人。

IP Information

ip_address	43.152.190.45
country	SG
network_name	Aceville PTE
asn	AS139341

Open Ports

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

Web Technologies

Software / Version	Category
web-vitals	JavaScript libraries, RUM
core-js 2.6.12	JavaScript libraries
Nginx	Web servers, Reverse proxies
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
OpenResty	Web servers
Vue.js 2.6.12	JavaScript frameworks
Webpack	Miscellaneous
Priority Hints	Performance
Sensors Data	Analytics

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://liu.lqclu.cn/	with_app_id, app_id, anony_token, shop_version_type	Set-Cookie: with_app_id=appybxipc9l6317 Set-Cookie: app_id=appybxipc9l6317 Set-Cookie: anony_token=5007fdb2061613fcdcff4bce5e7c6606 Set-Cookie: shop_version_type=4

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

URL	Cookie Name	Evidence
https://liu.lqclu.cn/	with_app_id, app_id, shop_version_type	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: with_app_id=appybxipc9l6317 Set-Cookie: app_id=appybxipc9l6317 Set-Cookie: shop_version_type=4

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://liu.lqclu.cn/	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

URL	Evidence
https://liu.lqclu.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(). 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. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. 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://liu.lqclu.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(). 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. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. 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	Evidence
https://liu.lqclu.cn/	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

Software / Version	Category
web-vitals	JavaScript libraries, RUM
core-js 2.6.12	JavaScript libraries
Nginx	Web servers, Reverse proxies
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
OpenResty	Web servers
Vue.js 2.6.12	JavaScript frameworks
Webpack	Miscellaneous
Priority Hints	Performance
Sensors Data	Analytics

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	Method	Parameters	Evidence
https://liu.lqclu.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	`1 : <img class="xe-category-nav--icon" src="http://wechatapppro-1252524126.cdn.xiaoeknow.com/appAKLWLitn7978/image/b_u_5b2225aa46488_oGKN7IvA/kowloki60ulm.png?imageMogr2/thumbnail/200x/quality/80%7CimageMogr2/ignore-error/1"/>`

Vulnerability description

We noticed that the target application is serving mixed content. This occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS.

Risk description

The risk is that the insecurely loaded resources (HTTP) on an otherwise secure page (HTTPS) can be intercepted or manipulated by attackers, potentially leading to eavesdropping or content tampering.

Recommendation

Ensure that all external resources the page references are loaded using HTTPS.

Classification

CWE	CWE-311
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://liu.lqclu.cn/	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

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
Nginx	Web servers, Reverse proxies
Vue.js	JavaScript frameworks
OpenResty	Web servers
Sensors Data	Analytics
Priority Hints	Performance
web-vitals	JavaScript libraries, RUM

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

Domain Queried	DNS Record Type	Description	Value
liu.lqclu.cn	A	IPv4 address	43.152.190.45
liu.lqclu.cn	CNAME	Canonical name	liu.lqclu.cn.cdn.dnsv1.com

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.

Evidence

Software / Version	Category
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
Nginx	Web servers, Reverse proxies
Vue.js	JavaScript frameworks
OpenResty	Web servers
Sensors Data	Analytics
web-vitals	JavaScript libraries, RUM

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.