Vulnerability Scan Result

Target:

https://api.awcloud.org/ (redirect)

Scanned target: https://api.awcloud.org/NewAdmin/login.html

Submitted: May 11, 2026 from AO

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	47.246.46.240
country	IT
network_name	Zhejiang Taobao Network Co., Ltd
asn	AS24429

Open Ports

80/tcp	http	ESA -
443/tcp	https	ESA -
2082/tcp	infowave	- -
2083/tcp	radsec	- -
2086/tcp	gnunet	- -
2087/tcp	eli	- -
8080/tcp	http	ESA -
8443/tcp	https-alt	ESA -

Web Technologies

Software / Version	Category
Google Font API	Font scripts
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://api.awcloud.org/NewAdmin/login.html	acw_tc, cdn_sec_tc	Set-Cookie: acw_tc=a3b5398517785933143366085e843590489a85c471ce9d7522381af969 Set-Cookie: cdn_sec_tc=a3b5398517785933143366085e843590489a85c471ce9d7522381af969

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	Method	Parameters	Evidence
https://api.awcloud.org/NewAdmin/login.html	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: ` ç¨æ·å å¯ç

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

CWE	CWE-598
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://api.awcloud.org/NewAdmin/login.html	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

URL	Evidence
https://api.awcloud.org/NewAdmin/login.html	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

Software / Version	Category
Google Font API	Font scripts
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.

Classification

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

Evidence

URL	Method	Parameters	Evidence
https://api.awcloud.org/NewAdmin/	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: acw_tc=a3b5398b17785933152457439e42204b8d32d86ed765475575c394a52a cdn_sec_tc=a3b5398b17785933152457439e42204b8d32d86ed765475575c394a52a	Possible API endpoint found at `/NewAdmin`

Vulnerability description

We found API endpoints while crawling the given web application.

Risk description

These endpoints may represent an attack surface for malicious actors interested in API-specific vulnerabilities.

Recommendation

Use the API Scanner to perform a more thorough vulnerability check for these endpoints, if an API specification is present.

Evidence

URL	Method	Summary
https://api.awcloud.org/NewAdmin/login.html	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET,HEAD,OPTIONS` Request / Response

Vulnerability description

We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.

Risk description

The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.

Recommendation

We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.

Classification

CWE	CWE-16
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL Evidence

URL	Evidence
https://api.awcloud.org/NewAdmin/login.html	`<input type="text" class="form-control" id="username" name="username" maxlength="50" autocomplete="username" spellcheck="false" placeholder="è¯·è¾å¥ç¨æ·å" required> <input type="password" class="form-control" id="password" name="password" autocomplete="current-password" placeholder="è¯·è¾å¥å¯ç " required> <button type="button" class="btn btn-login-primary" id="loginBtn"> <span class="btn-spinner" aria-hidden="true"></span> <span class="btn-label">ç»å½</span> </button>`

https://api.awcloud.org/NewAdmin/login.html

<input type="text" class="form-control" id="username" name="username" maxlength="50" autocomplete="username" spellcheck="false" placeholder="è¯·è¾å¥ç¨æ·å" required> <input type="password" class="form-control" id="password" name="password" autocomplete="current-password" placeholder="è¯·è¾å¥å¯ç " required> <button type="button" class="btn btn-login-primary" id="loginBtn"> <span class="btn-spinner" aria-hidden="true"></span> <span class="btn-label">ç»å½</span> </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.

Classification

CWE	CWE-287
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://api.awcloud.org/.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.

Classification

CWE	CWE-1188
OWASP Top 10 - 2017
OWASP Top 10 - 2021

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.

Evidence

Domain Queried	DNS Record Type	Description	Value
api.awcloud.org	A	IPv4 address	47.246.46.240

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.