- Banner
- 220 ProFTPD Server (AclimaNAS FTP Server) [::ffff:95.67.9.170]
Raw response
220 ProFTPD Server (AclimaNAS FTP Server) [::ffff:95.67.9.170]
Host
As of our latest check on 2026-08-13, 95.67.9.170 (Cosmonova LLC, AS34867, Ukraine) had 3 open ports (21, 22, 8080) and 35 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-08-13.
CVEs by severity: CRITICAL 1 HIGH 5 MEDIUM 13 LOW 16
A match is an indication, not proof: it is based on the software version a service reported, and fixes are often backported without changing the version. See the list
Not counted: 84 on a distribution build — the fix may be backported (http_server 2.4.57, openssl 1.1.1o). See them
Not counted: 2 only affect another platform (http_server 2.4.57). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
220 ProFTPD Server (AclimaNAS FTP Server) [::ffff:95.67.9.170]
SSH-2.0-OpenSSH_8.8-hpn14v15
HTTP/1.1 401 Unauthorized Date: Thu, 13 Aug 2026 18:23:52 GMT Server: Apache/2.4.57 (FreeBSD) OpenSSL/1.1.1o-freebsd WWW-Authenticate: Basic realm="webdav" Content-Length: 381 Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Unauthorized</title> </head><body> <h1>Unauthorized</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> </body></html>
These CVEs were matched on software built by an operating-system distribution whose package revision the service does not show. Distributions often fix a flaw without changing the upstream version number, so whether this build is affected cannot be told from its version. They are not counted. 1 of them is known to be exploited.
CVEs by severity: CRITICAL 11 HIGH 47 MEDIUM 25 LOW 1
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.57 · port 8080 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.57 · port 8080 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.57 · port 8080 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.57 · port 8080 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.57 · port 8080 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.57 · port 8080 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.57 · port 8080 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.57 · port 8080 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.57 · port 8080 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.57 · port 8080 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.57 · port 8080 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.57 · port 8080 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.57 · port 8080 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.57 · port 8080 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.57 · port 8080 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.57 · port 8080 |
| CVE-2023-4807 HIGH 7.8 | openssl 1.1.1o · port 8080 |
| CVE-2022-4450 HIGH 7.5 | openssl 1.1.1o · port 8080 |
| CVE-2023-0215 HIGH 7.5 | openssl 1.1.1o · port 8080 |
| CVE-2023-0464 HIGH 7.5 | openssl 1.1.1o · port 8080 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2023-43622 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2024-4741 HIGH 7.5 | openssl 1.1.1o · port 8080 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2023-0286 HIGH 7.4 | openssl 1.1.1o · port 8080 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.57 · port 8080 |
| CVE-2022-2068 HIGH 7.3 | openssl 1.1.1o · port 8080 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.57 · port 8080 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.57 · port 8080 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.57 · port 8080 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.57 · port 8080 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.57 · port 8080 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.57 · port 8080 |
| CVE-2023-2650 MEDIUM 6.5 | openssl 1.1.1o · port 8080 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.57 · port 8080 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.57 · port 8080 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.57 · port 8080 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.57 · port 8080 |
| CVE-2022-4304 MEDIUM 5.9 | openssl 1.1.1o · port 8080 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.57 · port 8080 |
| CVE-2024-2511 MEDIUM 5.9 | openssl 1.1.1o · port 8080 |
| CVE-2024-0727 MEDIUM 5.5 | openssl 1.1.1o · port 8080 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.57 · port 8080 |
| CVE-2024-36387 MEDIUM 5.4 | http_server 2.4.57 · port 8080 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.57 · port 8080 |
| CVE-2022-2097 MEDIUM 5.3 | openssl 1.1.1o · port 8080 |
| CVE-2023-0465 MEDIUM 5.3 | openssl 1.1.1o · port 8080 |
| CVE-2023-0466 MEDIUM 5.3 | openssl 1.1.1o · port 8080 |
| CVE-2023-3817 MEDIUM 5.3 | openssl 1.1.1o · port 8080 |
| CVE-2023-5678 MEDIUM 5.3 | openssl 1.1.1o · port 8080 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.57 · port 8080 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.57 · port 8080 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.57 · port 8080 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.57 · port 8080 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.57 · port 8080 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.57 · port 8080 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.57 · port 8080 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.57 · port 8080 |
These CVEs need a platform this host visibly does not run (for example a flaw of the Windows build on a Linux host). They are not counted.
CVEs by severity: HIGH 2
| CVE | Software |
|---|---|
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.57 · port 8080 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.57 · port 8080 |
Every port that has answered a connection on this address, and when. A port is listed as open above only when a service was identified on it. Times are UTC.