Vulnerability Scan Result

Target:

http://ajiemz.com/ (redirect)

Scanned target: https://ajiemz.com/

Submitted: Jun 18, 2026 from SV

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	阿街免税化妆品代购-全球进口品牌化妆品代购商
Description:	阿街免税化妆品代购，十年免税代购团队，只做正品。主营进口大牌免税化妆品、免税彩妆和免税香水等。所有商品均从海外正规渠道精心采购，严格把关，欢迎咨询～

IP Information

ip_address	59.108.140.6
country	CN
network_name	China Networks Inter-Exchange
asn	AS4847

ip_address	59.108.140.7
country	CN
network_name	China Networks Inter-Exchange
asn	AS4847

ip_address	59.108.140.8
country	CN
network_name	China Networks Inter-Exchange
asn	AS4847

ip_address	59.108.140.9
country	CN
network_name	China Networks Inter-Exchange
asn	AS4847

ip_address	59.108.140.10
country	CN
network_name	China Networks Inter-Exchange
asn	AS4847

ip_address	59.108.140.11
country	CN
network_name	China Networks Inter-Exchange
asn	AS4847

ip_address	59.108.140.12
country	CN
network_name	China Networks Inter-Exchange
asn	AS4847

ip_address	59.108.140.13
country	CN
network_name	China Networks Inter-Exchange
asn	AS4847

Open Ports

80/tcp	http	Tengine httpd -
443/tcp	https	Tengine httpd -

Web Technologies

Software / Version	Category
parallax.js	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
Tengine	Web servers
CNZZ	Analytics
Microsoft ASP.NET	Web frameworks

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://ajiemz.com/	SERVERID	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: SERVERID=4a2375aeee55ea6c8047110ce11098fc\|1782816914\|1782816914

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	Cookie Name	Evidence
https://ajiemz.com/	ASP.NET_SessionId, __RequestVerificationToken, SERVERID	Set-Cookie: ASP.NET_SessionId=4bowla3ggja0cbn4zaxtktq5 Set-Cookie: __RequestVerificationToken=ULYESIo7m41jU5yuLUncYlZBNvrnaCiBBNgXZe9XdA8GP--zARURmuC0TgYl68OKvtZahPOrqu3mrQZXmGflWIIN4m359kDIsCUmU9TRG2U1 Set-Cookie: SERVERID=4a2375aeee55ea6c8047110ce11098fc\|1782816914\|1782816914

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	Evidence
https://ajiemz.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
OWASP Top 10 - 2021

Evidence

URL
https://ajiemz.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).

Evidence

URL	Evidence
https://ajiemz.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-1021
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
parallax.js	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
Tengine	Web servers
CNZZ	Analytics
Microsoft ASP.NET	Web frameworks

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

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://ajiemz.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
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://ajiemz.com/	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

Evidence

URL	Method	Parameters	Evidence
https://ajiemz.com/lxwm	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: ASP.NET_SessionId=jadbxgznp5m4t42vg0ekygzg SERVERID=4a2375aeee55ea6c8047110ce11098fc\|1782816918\|1782816916 __RequestVerificationToken=cRxuzUO6...	Email Address: 752924772@qq.com

Vulnerability description

We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.

Risk description

The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.

Recommendation

Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
ajiemz.com	A	IPv4 address	59.108.140.12
ajiemz.com	A	IPv4 address	59.108.140.13
ajiemz.com	A	IPv4 address	59.108.140.6
ajiemz.com	A	IPv4 address	59.108.140.7
ajiemz.com	A	IPv4 address	59.108.140.8
ajiemz.com	A	IPv4 address	59.108.140.9
ajiemz.com	A	IPv4 address	59.108.140.10
ajiemz.com	A	IPv4 address	59.108.140.11
ajiemz.com	NS	Name server	dns32.hichina.com
ajiemz.com	NS	Name server	dns31.hichina.com
ajiemz.com	SOA	Start of Authority	dns31.hichina.com. hostmaster.hichina.com. 2026060413 3600 1200 86400 600

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
Microsoft ASP.NET	Web frameworks
Tengine	Web servers
parallax.js	JavaScript libraries
CNZZ	Analytics
jQuery 3.7.1	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.

Evidence

Software / Version	Category
Microsoft ASP.NET	Web frameworks
Tengine	Web servers
parallax.js	JavaScript libraries
CNZZ	Analytics
jQuery 3.7.1	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.