Vulnerability Scan Result
| Title: | ETH钱包app下载|ETH钱包官网|以太坊app免费下载安卓|以太坊钱包下载入口|以太坊官网app下载注册|以太坊电子钱包下载|你的通用数字钱包 |
| Description: | 以太坊钱包是一种专门用于存储、管理、转账以太坊(ETH)及其代币的数字工具,它通过生成私钥让用户拥有对资产的完全控制权,并支持ERC-20(代币)、ERC-721(NFT)、ERC-1155(多资产标准)等协议,使其可用于DeFi、NFT交易、GameFi等Web3生态.以太坊钱包可分为热钱包(如MetaMask、TrustWallet、TokenPocket),适用于日常交易、DApp交互;以及冷钱包(如Ledger、Trezor),采用离线存储私钥方式,提供更高的安全性,适合长期资产存储.钱包通常具备助记词备份、智能合约账户、多重签名(Multisig)、生物识别、硬件加密等安全机制,并提供Staking质押、跨链桥、DApp访问、NFT交易、去中心化身份(DID)等功能,确保用户可以在Web3世界中安全便捷地管理和使用自己的数字资产. |
| IP address | 156.245.69.34 |
| Country | HK  |
| AS number | AS142062 |
| Net name | Apnic ASN Block |
80/tcp | http | nginx - |
443/tcp | https | nginx - |
| Software / Version | Category |
|---|---|
| Bootstrap | UI frameworks |
| HTTP/3 | Miscellaneous |
| jQuery | JavaScript libraries |
| Modernizr | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| PHP | Programming languages |
| Popper | Miscellaneous |
| Baidu Analytics (百度统计) | Analytics |
| Chart.js | JavaScript graphics |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://zjcontainer.com/ | PHPSESSID | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: PHPSESSID=71moi4vhatd85tk09r3da36c7g |
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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://zjcontainer.com/ | PHPSESSID | Set-Cookie: PHPSESSID=71moi4vhatd85tk09r3da36c7g |
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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| https://zjcontainer.com/ | Response headers do not include the Referrer-Policy HTTP security header as well as the |
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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| https://zjcontainer.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-693 |
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| https://zjcontainer.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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| Software / Version | Category |
|---|---|
| Bootstrap | UI frameworks |
| HTTP/3 | Miscellaneous |
| jQuery | JavaScript libraries |
| Modernizr | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| PHP | Programming languages |
| Popper | Miscellaneous |
| Baidu Analytics (百度统计) | Analytics |
| Chart.js | JavaScript graphics |
| 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
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
Vulnerability description
Website is accessible.
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
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| zjcontainer.com | A | IPv4 address | 156.245.69.34 |
| zjcontainer.com | NS | Name server | a.share-dns.com |
| zjcontainer.com | NS | Name server | b.share-dns.net |
| zjcontainer.com | SOA | Start of Authority | a.share-dns.com. master.share-dns.com. 1747807722 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
| Operating System | Accuracy |
|---|---|
| Linux 2.6.32 - 3.13 | 100% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| PHP | Programming languages |
| Chart.js | JavaScript graphics |
| Bootstrap | UI frameworks |
| Nginx | Web servers, Reverse proxies |
| Modernizr | JavaScript libraries |
| jQuery | JavaScript libraries |
| Baidu Analytics (百度统计) | Analytics |
| HSTS | Security |
| Popper | Miscellaneous |
| 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 |
|---|---|
| PHP | Programming languages |
| Chart.js | JavaScript graphics |
| Bootstrap | UI frameworks |
| Nginx | Web servers, Reverse proxies |
| Modernizr | JavaScript libraries |
| jQuery | JavaScript libraries |
| Baidu Analytics (百度统计) | Analytics |
| HSTS | Security |
| Popper | Miscellaneous |
| 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.