Host
Tags: End-of-life software
As of our latest check on 2026-09-11, 95.79.102.82 (JSC "ER-Telecom Holding", AS42682, Russia) had 2 open ports (22, 3128) and 52 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-09-11.
CVEs by severity: CRITICAL 3 HIGH 22 MEDIUM 27
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: 1 possible, version too vague to tell (squid 2.7). See them
Not counted: 65 on a distribution build — the fix may be backported (openssh 5.4p1). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_5.4p1_hpn13v11 FreeBSD-20100308
HTTP/1.0 400 Bad Request Server: squid/2.7.STABLE9 Date: Fri, 17 Apr 2026 06:07:28 GMT Content-Type: text/html Content-Length: 1363 X-Squid-Error: ERR_INVALID_REQ 0 X-Cache: MISS from gw1.rest Via: 1.0 gw1.rest:3128 (squid/2.7.STABLE9) Connection: close
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.
CVEs by severity: CRITICAL 3 HIGH 19 MEDIUM 31 LOW 12
| CVE | Software |
|---|---|
| CVE-2010-4478 CRITICAL 9.8 | openssh 5.4p1 · port 22 |
| CVE-2016-1908 CRITICAL 9.8 | openssh 5.4p1 · port 22 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 5.4p1 · port 22 |
| CVE-2015-5600 HIGH 8.1 | openssh 5.4p1 · port 22 |
| CVE-2016-0778 HIGH 8.1 | openssh 5.4p1 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 5.4p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 5.4p1 · port 22 |
| CVE-2015-8325 HIGH 7.8 | openssh 5.4p1 · port 22 |
| CVE-2016-10012 HIGH 7.8 | openssh 5.4p1 · port 22 |
| CVE-2026-106583 HIGH 7.8 | openssh 5.4p1 · port 22 |
| CVE-2026-60002 HIGH 7.7 | openssh 5.4p1 · port 22 |
| CVE-2010-5107 HIGH 7.5 | openssh 5.4p1 · port 22 |
| CVE-2016-10708 HIGH 7.5 | openssh 5.4p1 · port 22 |
| CVE-2016-6515 HIGH 7.5 | openssh 5.4p1 · port 22 |
| CVE-2026-106553 HIGH 7.5 | openssh 5.4p1 · port 22 |
| CVE-2026-106555 HIGH 7.5 | openssh 5.4p1 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 5.4p1 · port 22 |
| CVE-2020-15778 HIGH 7.4 | openssh 5.4p1 · port 22 |
| CVE-2014-1692 HIGH 7.3 | openssh 5.4p1 · port 22 |
| CVE-2016-10009 HIGH 7.3 | openssh 5.4p1 · port 22 |
| CVE-2015-6564 HIGH 7.0 | openssh 5.4p1 · port 22 |
| CVE-2016-10010 HIGH 7.0 | openssh 5.4p1 · port 22 |
| CVE-2019-6109 MEDIUM 6.8 | openssh 5.4p1 · port 22 |
| CVE-2019-6110 MEDIUM 6.8 | openssh 5.4p1 · port 22 |
| CVE-2012-0814 MEDIUM 6.5 | openssh 5.4p1 · port 22 |
| CVE-2014-2653 MEDIUM 6.5 | openssh 5.4p1 · port 22 |
| CVE-2016-0777 MEDIUM 6.5 | openssh 5.4p1 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 5.4p1 · port 22 |
| CVE-2026-106552 MEDIUM 6.5 | openssh 5.4p1 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 5.4p1 · port 22 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 5.4p1 · port 22 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 5.4p1 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 5.4p1 · port 22 |
| CVE-2015-6563 MEDIUM 6.4 | openssh 5.4p1 · port 22 |
| CVE-2016-3115 MEDIUM 6.4 | openssh 5.4p1 · port 22 |
| CVE-2016-10011 MEDIUM 6.2 | openssh 5.4p1 · port 22 |
| CVE-2016-6210 MEDIUM 5.9 | openssh 5.4p1 · port 22 |
| CVE-2019-6111 MEDIUM 5.9 | openssh 5.4p1 · port 22 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 5.4p1 · port 22 |
| CVE-2026-59999 MEDIUM 5.9 | openssh 5.4p1 · port 22 |
| CVE-2011-4327 MEDIUM 5.5 | openssh 5.4p1 · port 22 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 5.4p1 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 5.4p1 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 5.4p1 · port 22 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 5.4p1 · port 22 |
| CVE-2017-15906 MEDIUM 5.3 | openssh 5.4p1 · port 22 |
| CVE-2018-15473 MEDIUM 5.3 | openssh 5.4p1 · port 22 |
| CVE-2018-20685 MEDIUM 5.3 | openssh 5.4p1 · port 22 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 5.4p1 · port 22 |
| CVE-2015-5352 MEDIUM 4.3 | openssh 5.4p1 · port 22 |
| CVE-2026-106586 MEDIUM 4.3 | openssh 5.4p1 · port 22 |
| CVE-2014-2532 MEDIUM 4.2 | openssh 5.4p1 · port 22 |
| CVE-2010-4755 MEDIUM 4.0 | openssh 5.4p1 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 5.4p1 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 5.4p1 · port 22 |
| CVE-2025-61984 LOW 3.6 | openssh 5.4p1 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 5.4p1 · port 22 |
| CVE-2011-5000 LOW 3.5 | openssh 5.4p1 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 5.4p1 · port 22 |
| CVE-2026-106584 LOW 3.3 | openssh 5.4p1 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 5.4p1 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 5.4p1 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 5.4p1 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 5.4p1 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 5.4p1 · port 22 |
These CVEs were matched on a software version that names only a major release (such as “2”) or no version at all: whether the release running here is affected cannot be told. They are not counted anywhere on this site.
| CVE | Software |
|---|---|
| CVE-2019-12529 MEDIUM 5.9 | squid 2.7 · port 3128 |
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.