Vulnerability Scan Result
| Title: | No title found |
| Description: | No description found |
| ip_address | 20.2.192.113 |
| country | HK  |
| network_name | Microsoft Corporation |
| asn | AS8075 |
| ip_address | 20.2.146.95 |
| country | HK |
| network_name | Microsoft Corporation |
| asn | AS8075 |
| ip_address | 52.184.69.93 |
| country | HK |
| network_name | Microsoft Corporation |
| asn | AS8075 |
| ip_address | 20.2.161.226 |
| country | HK |
| network_name | Microsoft Corporation |
| asn | AS8075 |
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 |
| Marko | Web frameworks, UI frameworks |
| Node.js | Programming languages |
| React | JavaScript frameworks |
| Lodash 4.17.15 | JavaScript libraries |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2020-8203 | 7.4 | 0.02826 | 0.86028 | Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20. |
| CVE-2021-23337 | 7.2 | 0.00517 | 0.66478 | Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function. |
| CVE-2025-13465 | 6.9 | 0.00028 | 0.07846 | Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes. The issue permits deletion of properties but does not allow overwriting their original behavior. This issue is patched on 4.17.23 |
| CVE-2020-28500 | 5.3 | 0.00245 | 0.47541 | Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions. |
Vulnerability description
Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.
Risk description
The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.
Classification
| CWE | CWE-1035 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Google Cloud | IaaS |
| Google Cloud CDN | CDN |
| Marko | Web frameworks, UI frameworks |
| Node.js | Programming languages |
| React | JavaScript frameworks |
| Lodash 4.17.15 | JavaScript libraries |
| 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 | Evidence |
|---|---|
| https://www.gjty41.vip:21328/ | 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 |
Infrastructure Vulnerabilities
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 |
| 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 |
| 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.gjty41.vip | A | IPv4 address | 20.2.161.226 |
| www.gjty41.vip | A | IPv4 address | 52.184.69.93 |
| www.gjty41.vip | A | IPv4 address | 20.2.146.95 |
| www.gjty41.vip | A | IPv4 address | 20.2.192.113 |
| www.gjty41.vip | CNAME | Canonical name | guanjingtiyu.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.
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 |
| 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 |
| 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 |
| 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.