- Banner
- 220 FTP Server ready.
Raw response
220 FTP Server ready.
Host
Tags: Hosting End-of-life software
As of our latest check on 2026-07-14, 62.149.5.33 (1 Cloud Lab s.r.o., AS15497, Ukraine) had 3 open ports (21, 22, 80) and 67 known CVEs, 1 known to be exploited.
Open ports and CVEs as of our latest check of this host, 2026-07-14.
CVEs by severity: CRITICAL 4 HIGH 21 MEDIUM 30 LOW 12
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: 55 on a distribution build — the fix may be backported (http_server 2.2.22). See them
Not counted: 2 only affect another platform (http_server 2.2.22). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
220 FTP Server ready.
SSH-2.0-OpenSSH_5.6
HTTP/1.1 200 OK Date: Tue, 14 Jul 2026 23:06:09 GMT Server: Apache/2.2.22 (Fedora) Last-Modified: Fri, 11 Feb 2011 12:25:16 GMT ETag: "14cba73-aa-49c00ca5f0300" Accept-Ranges: bytes Content-Length: 170 Connection: close Content-Type: text/html; charset=utf-8 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <HTML> <HEAD> <TITLE></TITLE> <META http-equiv=Refresh Content="0; Url=http://www.unascu.org.ua"> </HEAD> </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 13 HIGH 17 MEDIUM 24 LOW 1
| CVE | Software |
|---|---|
| CVE-2021-40438 CRITICAL 9.0 known exploited | http_server 2.2.22 · port 80 |
| CVE-2017-3167 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2017-3169 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2017-7679 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2021-39275 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2017-9788 CRITICAL 9.1 | http_server 2.2.22 · port 80 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.2.22 · port 80 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.2.22 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.2.22 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.2.22 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.2.22 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.2.22 · port 80 |
| CVE-2016-5387 HIGH 8.1 | http_server 2.2.22 · port 80 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2016-8743 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2017-9798 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2018-1303 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2021-34798 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.2.22 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.2.22 · port 80 |
| CVE-2012-0883 MEDIUM 6.9 | http_server 2.2.22 · port 80 |
| CVE-2014-0226 MEDIUM 6.8 | http_server 2.2.22 · port 80 |
| CVE-2016-4975 MEDIUM 6.1 | http_server 2.2.22 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.2.22 · port 80 |
| CVE-2018-1301 MEDIUM 5.9 | http_server 2.2.22 · port 80 |
| CVE-2018-1302 MEDIUM 5.9 | http_server 2.2.22 · port 80 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.2.22 · port 80 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.2.22 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.2.22 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.2.22 · port 80 |
| CVE-2013-1862 MEDIUM 5.1 | http_server 2.2.22 · port 80 |
| CVE-2013-5704 MEDIUM 5.0 | http_server 2.2.22 · port 80 |
| CVE-2013-6438 MEDIUM 5.0 | http_server 2.2.22 · port 80 |
| CVE-2014-0098 MEDIUM 5.0 | http_server 2.2.22 · port 80 |
| CVE-2014-0231 MEDIUM 5.0 | http_server 2.2.22 · port 80 |
| CVE-2015-0228 MEDIUM 5.0 | http_server 2.2.22 · port 80 |
| CVE-2015-3183 MEDIUM 5.0 | http_server 2.2.22 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.2.22 · port 80 |
| CVE-2008-0455 MEDIUM 4.3 | http_server 2.2.22 · port 80 |
| CVE-2012-3499 MEDIUM 4.3 | http_server 2.2.22 · port 80 |
| CVE-2012-4558 MEDIUM 4.3 | http_server 2.2.22 · port 80 |
| CVE-2013-1896 MEDIUM 4.3 | http_server 2.2.22 · port 80 |
| CVE-2014-0118 MEDIUM 4.3 | http_server 2.2.22 · port 80 |
| CVE-2016-8612 MEDIUM 4.3 | http_server 2.2.22 · port 80 |
| CVE-2012-2687 LOW 2.6 | http_server 2.2.22 · port 80 |
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 1 MEDIUM 1
| CVE | Software |
|---|---|
| CVE-2024-40898 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.2.22 · port 80 |
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.
1 name · as answered by each domain's own name servers