- Server
- SSH-2.0-OpenSSH_4.3
- Host key
- ssh-rsa d092e0d7d21012fb…
Raw response
SSH-2.0-OpenSSH_4.3
Host
Tags: End-of-life software
As of our latest check on 2026-05-14, 193.46.84.35 (UAB Bartus pro, AS51107, Lithuania) had 2 open ports (22, 80) and 72 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-05-14.
CVEs by severity: CRITICAL 3 HIGH 23 MEDIUM 33 LOW 13
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
1 of them on a software version from an earlier observation: a service of that kind is open now.
Not counted: 94 from an older observation (exim 4.69, bind 9.3.6-p1, proftpd 1.3.1; matched 2026-06-08). See them
Not counted: 2 only affect a particular platform; this host's is not known (openssh 4.3). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_4.3
HTTP/1.1 200 OK Date: Thu, 14 May 2026 08:24:02 GMT Server: Apache/2 Last-Modified: Wed, 06 Jan 2010 16:06:49 GMT ETag: "6ca137c-2c-47c812454b840" Accept-Ranges: bytes Vary: Accept-Encoding,User-Agent Content-Encoding: gzip Content-Length: 61 Content-Type: text/html ���(�ͱs,HL�HU�,VH+�K.�����KW��/�M�ɩ��+��j,
These CVEs only apply when the software runs on a particular platform (for example Windows), and this host's platform is not known. They are not counted.
CVEs by severity: MEDIUM 2
| CVE | Software |
|---|---|
| CVE-2009-2904 MEDIUM 6.9 | openssh 4.3 · port 22 |
| CVE-2008-4109 MEDIUM 5.0 | openssh 4.3 · port 22 |
These CVEs were matched on software this host reported in an earlier observation (matched 2026-06-08), not on a port that is open now, and no service of that kind was open at the latest check (2026-05-14). They are not counted above; 4 of them are known to be exploited.
CVEs by severity: CRITICAL 17 HIGH 46 MEDIUM 29 LOW 2
| CVE | Software |
|---|---|
| CVE-2010-4344 CRITICAL 9.8 known exploited | exim 4.69 |
| CVE-2018-6789 CRITICAL 9.8 known exploited | exim 4.69 |
| CVE-2010-4345 HIGH 7.8 known exploited | exim 4.69 |
| CVE-2015-5477 HIGH 7.8 known exploited | bind 9.3.6-p1 |
| CVE-2008-0122 HIGH 10.0 | bind 9.3.6-p1 |
| CVE-2019-12815 CRITICAL 9.8 | proftpd 1.3.1 |
| CVE-2019-15846 CRITICAL 9.8 | exim 4.69 |
| CVE-2020-28017 CRITICAL 9.8 | exim 4.69 |
| CVE-2020-28020 CRITICAL 9.8 | exim 4.69 |
| CVE-2020-28022 CRITICAL 9.8 | exim 4.69 |
| CVE-2020-28024 CRITICAL 9.8 | exim 4.69 |
| CVE-2020-28026 CRITICAL 9.8 | exim 4.69 |
| CVE-2021-25216 CRITICAL 9.8 | bind 9.3.6-p1 |
| CVE-2022-37452 CRITICAL 9.8 | exim 4.69 |
| CVE-2023-42115 CRITICAL 9.8 | exim 4.69 |
| CVE-2023-42116 CRITICAL 9.8 | exim 4.69 |
| CVE-2023-42117 CRITICAL 9.8 | exim 4.69 |
| CVE-2025-67896 CRITICAL 9.8 | exim 4.69 |
| CVE-2026-40685 CRITICAL 9.8 | exim 4.69 |
| CVE-2026-40687 CRITICAL 9.1 | exim 4.69 |
| CVE-2011-4130 HIGH 9.0 | proftpd 1.3.1 |
| CVE-2020-28021 HIGH 8.8 | exim 4.69 |
| CVE-2016-1286 HIGH 8.6 | bind 9.3.6-p1 |
| CVE-2020-8616 HIGH 8.6 | bind 9.3.6-p1 |
| CVE-2015-5722 HIGH 7.8 | bind 9.3.6-p1 |
| CVE-2020-28007 HIGH 7.8 | exim 4.69 |
| CVE-2020-28008 HIGH 7.8 | exim 4.69 |
| CVE-2020-28009 HIGH 7.8 | exim 4.69 |
| CVE-2020-28010 HIGH 7.8 | exim 4.69 |
| CVE-2020-28011 HIGH 7.8 | exim 4.69 |
| CVE-2020-28012 HIGH 7.8 | exim 4.69 |
| CVE-2020-28013 HIGH 7.8 | exim 4.69 |
| CVE-2020-28015 HIGH 7.8 | exim 4.69 |
| CVE-2020-28016 HIGH 7.8 | exim 4.69 |
| CVE-2009-0265 HIGH 7.5 | bind 9.3.6-p1 |
| CVE-2011-1764 HIGH 7.5 | exim 4.69 |
| CVE-2016-2776 HIGH 7.5 | bind 9.3.6-p1 |
| CVE-2016-3125 HIGH 7.5 | proftpd 1.3.1 |
| CVE-2016-8864 HIGH 7.5 | bind 9.3.6-p1 |
| CVE-2016-9131 HIGH 7.5 | bind 9.3.6-p1 |
| CVE-2019-18217 HIGH 7.5 | proftpd 1.3.1 |
| CVE-2019-19270 HIGH 7.5 | proftpd 1.3.1 |
| CVE-2019-19271 HIGH 7.5 | proftpd 1.3.1 |
| CVE-2019-19272 HIGH 7.5 | proftpd 1.3.1 |
| CVE-2020-12783 HIGH 7.5 | exim 4.69 |
| CVE-2020-28023 HIGH 7.5 | exim 4.69 |
| CVE-2020-28025 HIGH 7.5 | exim 4.69 |
| CVE-2020-9272 HIGH 7.5 | proftpd 1.3.1 |
| CVE-2021-25215 HIGH 7.5 | bind 9.3.6-p1 |
| CVE-2021-38371 HIGH 7.5 | exim 4.69 |
| CVE-2021-46854 HIGH 7.5 | proftpd 1.3.1 |
| CVE-2022-3559 HIGH 7.5 | exim 4.69 |
| CVE-2022-37451 HIGH 7.5 | exim 4.69 |
| CVE-2023-3341 HIGH 7.5 | bind 9.3.6-p1 |
| CVE-2023-4408 HIGH 7.5 | bind 9.3.6-p1 |
| CVE-2023-50387 HIGH 7.5 | bind 9.3.6-p1 |
| CVE-2023-50868 HIGH 7.5 | bind 9.3.6-p1 |
| CVE-2023-51713 HIGH 7.5 | proftpd 1.3.1 |
| CVE-2026-3039 HIGH 7.5 | bind 9.3.6-p1 |
| CVE-2026-40684 HIGH 7.5 | exim 4.69 |
| CVE-2010-3867 HIGH 7.1 | proftpd 1.3.1 |
| CVE-2015-5986 HIGH 7.1 | bind 9.3.6-p1 |
| CVE-2016-1531 HIGH 7.0 | exim 4.69 |
| CVE-2011-0017 MEDIUM 6.9 | exim 4.69 |
| CVE-2009-0543 MEDIUM 6.8 | proftpd 1.3.1 |
| CVE-2010-4652 MEDIUM 6.8 | proftpd 1.3.1 |
| CVE-2014-2957 MEDIUM 6.8 | exim 4.69 |
| CVE-2016-1285 MEDIUM 6.8 | bind 9.3.6-p1 |
| CVE-2016-6170 MEDIUM 6.5 | bind 9.3.6-p1 |
| CVE-2018-5741 MEDIUM 6.5 | bind 9.3.6-p1 |
| CVE-2020-8622 MEDIUM 6.5 | bind 9.3.6-p1 |
| CVE-2021-27216 MEDIUM 6.3 | exim 4.69 |
| CVE-2020-28014 MEDIUM 6.1 | exim 4.69 |
| CVE-2016-2775 MEDIUM 5.9 | bind 9.3.6-p1 |
| CVE-2016-9963 MEDIUM 5.9 | exim 4.69 |
| CVE-2020-8617 MEDIUM 5.9 | bind 9.3.6-p1 |
| CVE-2009-3639 MEDIUM 5.8 | proftpd 1.3.1 |
| CVE-2017-7418 MEDIUM 5.5 | proftpd 1.3.1 |
| CVE-2024-39929 MEDIUM 5.4 | exim 4.69 |
| CVE-2021-25219 MEDIUM 5.3 | bind 9.3.6-p1 |
| CVE-2022-2795 MEDIUM 5.3 | bind 9.3.6-p1 |
| CVE-2023-42114 MEDIUM 5.3 | exim 4.69 |
| CVE-2023-51766 MEDIUM 5.3 | exim 4.69 |
| CVE-2026-40686 MEDIUM 5.3 | exim 4.69 |
| CVE-2011-1137 MEDIUM 5.0 | proftpd 1.3.1 |
| CVE-2019-19269 MEDIUM 4.9 | proftpd 1.3.1 |
| CVE-2014-2972 MEDIUM 4.6 | exim 4.69 |
| CVE-2010-2023 MEDIUM 4.4 | exim 4.69 |
| CVE-2010-2024 MEDIUM 4.4 | exim 4.69 |
| CVE-2010-3762 MEDIUM 4.3 | bind 9.3.6-p1 |
| CVE-2008-7265 MEDIUM 4.0 | proftpd 1.3.1 |
| CVE-2017-1000369 MEDIUM 4.0 | exim 4.69 |
| CVE-2023-42119 LOW 3.1 | exim 4.69 |
| CVE-2012-6095 LOW 1.2 | proftpd 1.3.1 |
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.
2 names · as answered by each domain's own name servers