Vulnerability Scan Result
| Title: | No title found |
| Description: | No description found |
| ip_address | 171.4.125.2 |
| country | TH  |
| network_name | Jastel Network |
| asn | AS45629 |
22/tcp | ssh | Dropbear sshd - |
23/tcp | telnet | Huawei Home Gateway telnetd - |
80/tcp | https | - - |
| Software / Version | Category |
|---|---|
| jQuery 3.6.0 | JavaScript libraries |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| http://171.4.125.2/ | Password input detected over insecure HTTP. |
Vulnerability description
We found that passwords are transmitted over a network without encryption. When users submit their passwords through an application or system, the lack of encryption means that the sensitive information is transmitted in plaintext, making it susceptible to interception and unauthorized access.
Risk description
The risk is that malicious actors could employ various techniques, such as packet sniffing or man-in-the-middle attacks, to capture plaintext passwords. Once intercepted, the attacker gains unauthorized access to user accounts, potentially leading to identity theft, unauthorized data access, or other malicious activities. The risk remains unchanged even if the password's form submission triggers a redirect response to an HTTPS page.
Recommendation
We recommend you to reconfigure the web server so it uses HTTPS - which encrypts the communication between the web browser and the server. This way, the attacker will not be able to obtain the clear-text passwords, even though he manages to intercept the network communication.
Classification
| CWE | CWE-523 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Response URL | Evidence |
|---|---|---|
| http://171.4.125.2/ | http://171.4.125.2/ | Communication is made over unsecure, unencrypted HTTP. |
Vulnerability description
We noticed that the communication between the web browser and the server is done using the HTTP protocol, which transmits data unencrypted over the network.
Risk description
The risk is that an attacker who manages to intercept the communication at the network level can read and modify the data transmitted (including passwords, secret tokens, credit card information and other sensitive data).
Recommendation
We recommend you to reconfigure the web server to use HTTPS - which encrypts the communication between the web browser and the server.
Classification
| CWE | CWE-311 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| jQuery 3.6.0 | 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
| URL | Evidence |
|---|---|
| http://171.4.125.2/ | 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 |
|---|---|
| http://171.4.125.2/ | Response headers include the HTTP Content-Security-Policy security header with the following security issues: |
Vulnerability description
We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.
Risk description
For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.
Recommendation
Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| http://171.4.125.2/ | 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
Vulnerability description
Website is accessible.
Evidence
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.
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible Telnet service. Starting Nmap ( https://nmap.org ) at 2025-11-01 02:59 EET Nmap scan report for mx-ll-171.4.125-2.dynamic.3bb.co.th (171.4.125.2) Host is up (0.17s latency).
PORT STATE SERVICE VERSION
23/tcp open telnet
| fingerprint-strings:
| GenericLines, GetRequest, Help, NCP, NULL, RPCCheck, SIPOptions, tn3270:
|_ Command line is locked now, please retry later.
| telnet-encryption:
|_ Telnet server does not support encryption
1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service :
SF-Port23-TCP:V=7.93%I=7%D=11/1%Time=69055B8A%P=x86_64-pc-linux-gnu%r(NULL
SF:,3E,"\xff\xfb\x01\xff\xfb\x03\xff\xfb\x18\r\nCommand\x20line\x20is\x20l
SF:ocked\x20now,\x20please\x20retry\x20later.\r\n\r\n")%r(GenericLines,3E
SF:,"\xff\xfb\x01\xff\xfb\x03\xff\xfb\x18\r\nCommand\x20line\x20is\x20lock
SF:ed\x20now,\x20please\x20retry\x20later.\r\n\r\n")%r(tn3270,3E,"\xff\xf
SF:b\x01\xff\xfb\x03\xff\xfb\x18\r\nCommand\x20line\x20is\x20locked\x20now
SF:,\x20please\x20retry\x20later.\r\n\r\n")%r(GetRequest,3E,"\xff\xfb\x01
SF:\xff\xfb\x03\xff\xfb\x18\r\nCommand\x20line\x20is\x20locked\x20now,\x20
SF:please\x20retry\x20later.\r\n\r\n")%r(RPCCheck,3E,"\xff\xfb\x01\xff\xf
SF:b\x03\xff\xfb\x18\r\nCommand\x20line\x20is\x20locked\x20now,\x20please
SF:x20retry\x20later.\r\n\r\n")%r(Help,3E,"\xff\xfb\x01\xff\xfb\x03\xff\x
SF:fb\x18\r\nCommand\x20line\x20is\x20locked\x20now,\x20please\x20retry\x2
SF:0later.\r\n\r\n")%r(SIPOptions,3E,"\xff\xfb\x01\xff\xfb\x03\xff\xfb\x1
SF:8\r\nCommand\x20line\x20is\x20locked\x20now,\x20please\x20retry\x20late
SF:r.\r\n\r\n")%r(NCP,3E,"\xff\xfb\x01\xff\xfb\x03\xff\xfb\x18\r\nCommand
SF:\x20line\x20is\x20locked\x20now,\x20please\x20retry\x20later.\r\n\r\n"
SF:);
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 42.57 seconds
Vulnerability description
We found that the Telnet service is publicly accessible. Telnet is a protocol leveraged by network administrators for remote management of network devices. However, its main drawback is that it operates exclusively in cleartext, making all traffic communicated through this protocol vulnerable to interception in its unencrypted form.
Risk description
This issue could lead to the exposure of sensitive data such as user credentials and other sensitive information depending on the device being managed remotely since Telnet uses a cleartext transfer of data. If an attacker intercepts these credentials through Telnet, they might gain unauthorized access to the device.
Recommendation
We recommend turning off Telnet access over the Internet. Instead, use SSH for secure remote access and management of network devices. Additionally, even with an alternative remote administration solution in place, we recommend using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA).
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2025-11-01 02:59 EET Nmap scan report for mx-ll-171.4.125-2.dynamic.3bb.in.th (171.4.125.2) Host is up (0.18s latency).
PORT STATE SERVICE VERSION 22/tcp open ssh Dropbear sshd (protocol 2.0) | ssh-auth-methods: | Supported authentication methods: | publickey |_ password Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 2.74 seconds
Vulnerability description
We found that the SSH service with username/password authentication is publicly accessible. Network administrators often use remote administration protocols to control devices like switches, routers, and other essential systems. However, allowing these services to be accessible via the Internet can increase security risks, creating potential opportunities for attacks on the organization.
Risk description
Exposing this service online with username/password authentication can enable attackers to launch authentication attacks, like guessing login credentials, and potentially gaining unauthorized access. Vulnerabilities, such as unpatched software, protocol flaws, or backdoors could also be exploited. An example is the CVE-2024-3094 (XZ Utils Backdoor) vulnerability.
Recommendation
We recommend turning off SSH with username/password authentication access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the SSH service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, it is advisable to utilize SSH Public Key Authentication since it employs a key pair to verify the identity of a user or process.
Evidence
| Operating System | Accuracy |
|---|---|
| HP P2000 G3 NAS device | 91% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| 171.4.125.2 | PTR | Pointer record | mx-ll-171.4.125-2.dynamic.3bb.in.th |
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 |
|---|---|
| jQuery | 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.