84.201.172.182 — 3 open ports, 121 known CVEs, network Yandex.Cloud LLC

Known CVEs on this host

3open ports

0names pointing here

121known CVEs

2known exploited

Open ports and CVEs as of our latest check of this host, 2026-08-09.

CVEs by severity: CRITICAL 24 HIGH 55 MEDIUM 40 LOW 2

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: 72 on a distribution build — the fix may be backported (openssh 8.0, http_server 2.4.37, openssl 1.1.1k). See them

Not counted: 6 only affect another platform (http_server 2.4.37, php 7.2.24). See them

Earlier software versions of this host and the CVEs they had are kept as its history. See the history

Network: Yandex.Cloud LLC AS200350
Open ports: 22, 80, 443 · at our latest check, 2026-08-09
Location: Russia RU
Route: 84.201.128.0/18 · announced by Yandex.Cloud LLC AS200350 RPKI valid
Organisation: Yandex.Cloud LLC · Enterprise
Registry network: RU-YANDEXCLOUD-20110210 · 84.201.128.0 - 84.201.191.255 · Yandex.Cloud LLC · RIPE
Abuse contact: [email protected] · for RU-YANDEXCLOUD-20110210
First seen: 2026-08-09 18:03 UTC
Last seen alive: 2026-08-09 18:06 UTC
Hosted domains: No host name points here

Reputation

Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.

Services (3)

22/tcp SSH OpenSSH_8.0 first 2026-08-09 · last 2026-08-09

Server: SSH-2.0-OpenSSH_8.0
Host key: ssh-ed25519 136a136b8c6eb06c…

Raw response

SSH-2.0-OpenSSH_8.0

80/tcp HTTP Apache/2.4.37 (centos) OpenSSL/1.1.1k 121 CVEs first 2026-08-09 · last 2026-08-09

Status: 301 Moved Permanently
Server: Apache/2.4.37 (centos) OpenSSL/1.1.1k
Powered by: PHP/7.2.24

Raw response

HTTP/1.1 301 Moved Permanently
Date: Sun, 09 Aug 2026 18:03:41 GMT
Server: Apache/2.4.37 (centos) OpenSSL/1.1.1k
X-Powered-By: PHP/7.2.24
X-Pingback: http://eva-sdo.ru/xmlrpc.php
Expires: Sun, 09 Aug 2026 19:03:41 GMT
Cache-Control: max-age=3600
X-Redirect-By: WordPress
Location: https://eva-sdo.ru/
Content-Length: 0
Content-Type: text/html; charset=UTF-8

443/tcp TLS first 2026-08-09 · last 2026-08-09

TLS: TLSv1.2
Certificate for: wp.ru-central1.internal
Issued by: wp.ru-central1.internal
Valid: 2020-10-25 → 2021-10-30
Note: self-signed certificate

Raw response

HTTP/1.1 400 Bad Request
Date: Sun, 09 Aug 2026 18:03:41 GMT
Server: Apache/2.4.37 (centos) OpenSSL/1.1.1k
Content-Length: 362
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
 Instead use the HTTPS scheme to access this URL, please.<br />
</p>
</body></html>

Vulnerabilities

Distribution build — the fix may be backported (72)

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. 2 of them are known to be exploited.

CVEs by severity: CRITICAL 9 HIGH 27 MEDIUM 24 LOW 12

CVE	Software
CVE-2021-40438 CRITICAL 9.0 known exploited	http_server 2.4.37 · port 80
CVE-2019-0211 HIGH 7.8 known exploited	http_server 2.4.37 · port 80
CVE-2020-11984 CRITICAL 9.8	http_server 2.4.37 · port 80
CVE-2021-26691 CRITICAL 9.8	http_server 2.4.37 · port 80
CVE-2021-3711 CRITICAL 9.8	openssl 1.1.1k · port 80
CVE-2021-39275 CRITICAL 9.8	http_server 2.4.37 · port 80
CVE-2021-44790 CRITICAL 9.8	http_server 2.4.37 · port 80
CVE-2023-38408 CRITICAL 9.8	openssh 8.0 · port 22
CVE-2026-60002 CRITICAL 9.4	openssh 8.0 · port 22
CVE-2019-10082 CRITICAL 9.1	http_server 2.4.37 · port 80
CVE-2021-44224 HIGH 8.2	http_server 2.4.37 · port 80
CVE-2026-35385 HIGH 8.1	openssh 8.0 · port 22
CVE-2026-35414 HIGH 8.1	openssh 8.0 · port 22
CVE-2019-16905 HIGH 7.8	openssh 8.0 · port 22
CVE-2026-106583 HIGH 7.8	openssh 8.0 · port 22
CVE-2018-17199 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2019-0190 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2019-0215 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2019-0217 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2019-10081 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2019-9517 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2020-11993 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2020-9490 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2021-26690 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2021-33193 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2021-34798 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2021-36160 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2026-106553 HIGH 7.5	openssh 8.0 · port 22
CVE-2026-106555 HIGH 7.5	openssh 8.0 · port 22
CVE-2026-59999 HIGH 7.5	openssh 8.0 · port 22
CVE-2026-60000 HIGH 7.5	openssh 8.0 · port 22
CVE-2020-15778 HIGH 7.4	openssh 8.0 · port 22
CVE-2021-3712 HIGH 7.4	openssl 1.1.1k · port 80
CVE-2020-35452 HIGH 7.3	http_server 2.4.37 · port 80
CVE-2019-10097 HIGH 7.2	http_server 2.4.37 · port 80
CVE-2021-41617 HIGH 7.0	openssh 8.0 · port 22
CVE-2025-26465 MEDIUM 6.8	openssh 8.0 · port 22
CVE-2023-51385 MEDIUM 6.5	openssh 8.0 · port 22
CVE-2026-106552 MEDIUM 6.5	openssh 8.0 · port 22
CVE-2026-106585 MEDIUM 6.5	openssh 8.0 · port 22
CVE-2026-35387 MEDIUM 6.5	openssh 8.0 · port 22
CVE-2026-59998 MEDIUM 6.5	openssh 8.0 · port 22
CVE-2026-60001 MEDIUM 6.5	openssh 8.0 · port 22
CVE-2019-10092 MEDIUM 6.1	http_server 2.4.37 · port 80
CVE-2019-10098 MEDIUM 6.1	http_server 2.4.37 · port 80
CVE-2020-1927 MEDIUM 6.1	http_server 2.4.37 · port 80
CVE-2020-14145 MEDIUM 5.9	openssh 8.0 · port 22
CVE-2023-48795 MEDIUM 5.9	openssh 8.0 · port 22
CVE-2026-59995 MEDIUM 5.4	openssh 8.0 · port 22
CVE-2026-59996 MEDIUM 5.4	openssh 8.0 · port 22
CVE-2026-59997 MEDIUM 5.4	openssh 8.0 · port 22
CVE-2016-20012 MEDIUM 5.3	openssh 8.0 · port 22
CVE-2018-17189 MEDIUM 5.3	http_server 2.4.37 · port 80
CVE-2019-0196 MEDIUM 5.3	http_server 2.4.37 · port 80
CVE-2019-0220 MEDIUM 5.3	http_server 2.4.37 · port 80
CVE-2019-17567 MEDIUM 5.3	http_server 2.4.37 · port 80
CVE-2020-1934 MEDIUM 5.3	http_server 2.4.37 · port 80
CVE-2026-73282 MEDIUM 4.8	openssh 8.0 · port 22
CVE-2026-106586 MEDIUM 4.3	openssh 8.0 · port 22
CVE-2019-0197 MEDIUM 4.2	http_server 2.4.37 · port 80
CVE-2025-32728 LOW 3.8	openssh 8.0 · port 22
CVE-2021-36368 LOW 3.7	openssh 8.0 · port 22
CVE-2026-106582 LOW 3.7	openssh 8.0 · port 22
CVE-2025-61984 LOW 3.6	openssh 8.0 · port 22
CVE-2025-61985 LOW 3.6	openssh 8.0 · port 22
CVE-2026-73281 LOW 3.5	openssh 8.0 · port 22
CVE-2026-106584 LOW 3.3	openssh 8.0 · port 22
CVE-2026-106587 LOW 3.3	openssh 8.0 · port 22
CVE-2026-106588 LOW 3.1	openssh 8.0 · port 22
CVE-2026-106589 LOW 2.9	openssh 8.0 · port 22
CVE-2026-35388 LOW 2.5	openssh 8.0 · port 22
CVE-2026-73283 LOW 2.5	openssh 8.0 · port 22

Only affects another platform (6)

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: CRITICAL 2 HIGH 2 MEDIUM 2

CVE	Software
CVE-2024-3566 CRITICAL 9.8	php 7.2.24 · port 80
CVE-2020-7061 CRITICAL 9.1	php 7.2.24 · port 80
CVE-2024-40898 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2024-43394 HIGH 7.5	http_server 2.4.37 · port 80
CVE-2020-13938 MEDIUM 5.5	http_server 2.4.37 · port 80
CVE-2022-28330 MEDIUM 5.3	http_server 2.4.37 · port 80

CVE history

Software versions this host showed earlier, when we saw each, why it no longer applies, and the CVEs matched on it then. None of them is counted.

Port history

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.

Report an issue with this page