Vulnerability Scan Result
| Title: | No title found |
| Description: | No description found |
| ip_address | 213.176.36.59 |
| country | US  |
| network_name | E-Large |
| asn | HongKong |
| ip_address | 213.176.96.191 |
| country | HK  |
| network_name | E-Large |
| asn | HongKong |
| ip_address | 213.176.83.116 |
| country | IR  |
| network_name | E-Large |
| asn | HongKong |
| ip_address | 213.176.101.238 |
| country | HK |
| network_name | E-Large |
| asn | HongKong |
| ip_address | 213.176.50.213 |
| country | US |
| network_name | E-Large |
| asn | HongKong |
| ip_address | 213.176.59.196 |
| country | US |
| network_name | E-Large |
| asn | HongKong |
80/tcp | http | WAF - |
443/tcp | https | WAF - |
1028/tcp | https | nginx - |
1080/tcp | https | nginx - |
6001/tcp | https | nginx - |
8000/tcp | https | nginx - |
8080/tcp | http | WAF - |
8443/tcp | https-alt | WAF - |
20000/tcp | https | nginx - |
27017/tcp | https | nginx - |
| Software / Version | Category |
|---|---|
| Google Cloud | IaaS |
| Google Cloud CDN | CDN |
| Facebook Pixel | Analytics |
| core-js 3.32.2 | JavaScript libraries |
| Marko | Web frameworks, UI frameworks |
| Node.js | Programming languages |
| PWA | Miscellaneous |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://www.leying26.com:30123/ | 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://www.leying26.com:30123/ | 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 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Google Cloud | IaaS |
| Google Cloud CDN | CDN |
| Facebook Pixel | Analytics |
| core-js 3.32.2 | JavaScript libraries |
| Marko | Web frameworks, UI frameworks |
| Node.js | Programming languages |
| PWA | Miscellaneous |
| 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://www.leying26.com:30123/ | 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 | Operating system paths found in the HTTP response: |
Vulnerability description
We found operating system paths returned in a HTTP response.
Risk description
The risk is that path disclosure may help an attacker learn more about the remote server's file system, thus increasing the effectiveness and precision of any future attacks.
Recommendation
Configure the web server to avoid leaking path information by using generic error messages that do not reveal any internal file paths. Make sure no server file is referred with its absolute path in the website code.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Node.js | Programming languages |
| Marko | Web frameworks, UI frameworks |
| Google Cloud | IaaS |
| Facebook Pixel | Analytics |
| HSTS | Security |
| Google Cloud CDN | CDN |
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 |
|---|---|
| Node.js | Programming languages |
| Marko | Web frameworks, UI frameworks |
| Google Cloud | IaaS |
| Facebook Pixel | Analytics |
| HSTS | Security |
| Google Cloud CDN | CDN |
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 |
|---|---|
| Node.js | Programming languages |
| Marko | Web frameworks, UI frameworks |
| Google Cloud | IaaS |
| HSTS | Security |
| Google Cloud CDN | CDN |
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 |
|---|---|
| Node.js | Programming languages |
| Marko | Web frameworks, UI frameworks |
| Google Cloud | IaaS |
| Facebook Pixel | Analytics |
| HSTS | Security |
| Google Cloud CDN | CDN |
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
| Operating System | Accuracy |
|---|---|
| Fortinet FortiGate 100D firewall | 87% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Node.js | Programming languages |
| Marko | Web frameworks, UI frameworks |
| Google Cloud | IaaS |
| Facebook Pixel | Analytics |
| HSTS | Security |
| Google Cloud CDN | CDN |
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 |
|---|---|
| Google Cloud | IaaS |
| HSTS | Security |
| Google Cloud CDN | CDN |
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 |
|---|---|
| Node.js | Programming languages |
| Marko | Web frameworks, UI frameworks |
| Google Cloud | IaaS |
| Facebook Pixel | Analytics |
| HSTS | Security |
| Google Cloud CDN | CDN |
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 |
|---|---|
| Node.js | Programming languages |
| Marko | Web frameworks, UI frameworks |
| Google Cloud | IaaS |
| Facebook Pixel | Analytics |
| HSTS | Security |
| Google Cloud CDN | CDN |
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 |
|---|---|---|---|
| www.leying26.com | A | IPv4 address | 213.176.36.59 |
| www.leying26.com | A | IPv4 address | 213.176.59.196 |
| www.leying26.com | A | IPv4 address | 213.176.50.213 |
| www.leying26.com | A | IPv4 address | 213.176.101.238 |
| www.leying26.com | A | IPv4 address | 213.176.83.116 |
| www.leying26.com | A | IPv4 address | 213.176.96.191 |
| www.leying26.com | CNAME | Canonical name | leying.gtm-cloudflare.net |
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.