46.0.192.38 — 2 open ports, 6 known CVEs, network JSC "ER-Telecom Holding"

Known CVEs on this host

2open ports

4names pointing here

6known CVEs

0known exploited

Open ports and CVEs as of our latest check of this host, 2026-06-28.

CVEs by severity: HIGH 4 MEDIUM 1 LOW 1

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: 74 on a distribution build — the fix may be backported (http_server 2.4.52). See them

Not counted: 3 only affect another platform (http_server 2.4.52). See them

Network: JSC "ER-Telecom Holding" AS34533
Open ports: 80, 8080 · at our latest check, 2026-06-28
Location: Russia RU
Hostname: 46x0x192x38.static-customer.samara.ertelecom.ru · reverse DNS, checked 2026-10-04
Route: 46.0.0.0/16 · announced by JSC "ER-Telecom Holding" AS34533 no RPKI authorisation
Organisation: JSC "ER-Telecom Holding"
Registry network: ESAMARA-PPPOE-17-NET · 46.0.192.0 - 46.0.199.255 · RIPE
Abuse contact: [email protected] · for ESAMARA-PPPOE-17-NET
First seen: 2026-06-28 02:13 UTC
Last seen alive: 2026-06-28 02:15 UTC
Hosted domains: 4 names point here

Reputation

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

Services (2)

80/tcp HTTP Microsoft-IIS/10.0 first 2026-06-28 · last 2026-06-28

Status: 200 OK
Title: IIS Windows Server
Server: Microsoft-IIS/10.0
Powered by: ASP.NET

Raw response

HTTP/1.1 200 OK
Content-Type: text/html
Content-Encoding: gzip
Last-Modified: Sat, 27 Aug 2022 21:18:09 GMT
Accept-Ranges: bytes
ETag: "e9b7f8815abad81:0"
Vary: Accept-Encoding
Server: Microsoft-IIS/10.0
X-Powered-By: ASP.NET
Date: Sun, 28 Jun 2026 02:13:22 GMT
Content-Length: 609

���`I�%&/m�{J�J��t��`$ؐ@�������iG#)�*��eVe]f@�흼��{����{����;�N'���?\fdl��J�ɞ!���?~|?"��O�<y���<M���L_~����I���ݻ߽wr���7O����o�x���w��m]LۻwO_|�~4o�գ�w����W��U}q�ͫ��e����
�3�����~��1>L�-�e�Y��Ç�Ei�g3�\�mF���������>:��m�l��\���ҩ���Gm�������<�����h�탃��w?J�V[�e~tv�:�n��UWM�:�/���]���4�u��-�V�Ӧa|~����8�T�����ɏM�����?���$������r�m�{�w�)�[d�E�|...<truncated>

8080/tcp HTTP Apache/2.4.52 (Ubuntu) 6 CVEs first 2026-06-28 · last 2026-06-28

Status: 200 OK
Title: Custom Tile Server
Server: Apache/2.4.52 (Ubuntu)

Raw response

HTTP/1.1 200 OK
Date: Sun, 28 Jun 2026 02:13:22 GMT
Server: Apache/2.4.52 (Ubuntu)
Last-Modified: Tue, 27 Sep 2022 14:04:27 GMT
ETag: "3c9-5e9a91f4650c0-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 511
Content-Type: text/html

�uS���0��+\��D̶�UHm�[����Ҷ���Ipk0�'�l��+�����g??�G�>=�w�_?��̢�cԢD6�%*H�'��`;��m��`"> ���P�4���	���x�ׂR;��������
��0�3�e
~xL��P�M���.���J���;[6 ���!v��Rk���Y!�&���e�$�2��Y�{��%�c{��{]���o���җ�.߬&`�����B��,�,�B��2Y'��*���F|�q:��d�f2���]�[��a|J-�n�M@�ܥ����od��G������/V��}��d6�3wy7���??��^��<��?RX���Z��{o
D#�'��2�~!U���z���]�H�@�X�%�M���Ң�� ݁6G�$4����"...<truncated>

Vulnerabilities

Distribution build — the fix may be backported (74)

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 18 HIGH 40 MEDIUM 16

CVE	Software
CVE-2024-38475 CRITICAL 9.1 known exploited	http_server 2.4.52 · port 8080
CVE-2022-22720 CRITICAL 9.8	http_server 2.4.52 · port 8080
CVE-2022-23943 CRITICAL 9.8	http_server 2.4.52 · port 8080
CVE-2022-31813 CRITICAL 9.8	http_server 2.4.52 · port 8080
CVE-2023-25690 CRITICAL 9.8	http_server 2.4.52 · port 8080
CVE-2024-38474 CRITICAL 9.8	http_server 2.4.52 · port 8080
CVE-2024-38476 CRITICAL 9.8	http_server 2.4.52 · port 8080
CVE-2026-28780 CRITICAL 9.8	http_server 2.4.52 · port 8080
CVE-2026-29167 CRITICAL 9.8	http_server 2.4.52 · port 8080
CVE-2026-44631 CRITICAL 9.8	http_server 2.4.52 · port 8080
CVE-2026-56154 CRITICAL 9.8	http_server 2.4.52 · port 8080
CVE-2026-57941 CRITICAL 9.8	http_server 2.4.52 · port 8080
CVE-2026-59797 CRITICAL 9.8	http_server 2.4.52 · port 8080
CVE-2022-22721 CRITICAL 9.1	http_server 2.4.52 · port 8080
CVE-2022-28615 CRITICAL 9.1	http_server 2.4.52 · port 8080
CVE-2025-23048 CRITICAL 9.1	http_server 2.4.52 · port 8080
CVE-2026-42535 CRITICAL 9.1	http_server 2.4.52 · port 8080
CVE-2022-36760 CRITICAL 9.0	http_server 2.4.52 · port 8080
CVE-2026-24072 HIGH 8.8	http_server 2.4.52 · port 8080
CVE-2026-93546 HIGH 8.8	http_server 2.4.52 · port 8080
CVE-2025-58098 HIGH 8.3	http_server 2.4.52 · port 8080
CVE-2024-38473 HIGH 8.1	http_server 2.4.52 · port 8080
CVE-2026-73636 HIGH 8.1	http_server 2.4.52 · port 8080
CVE-2006-20001 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2022-22719 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2022-26377 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2022-29404 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2022-30556 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2023-27522 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2023-31122 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2024-27316 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2024-38472 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2024-38477 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2024-39573 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2024-42516 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2024-43204 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2024-47252 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2025-49630 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2025-53020 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2025-55753 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2025-59775 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2026-29169 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2026-34059 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2026-34355 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2026-34356 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2026-42536 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2026-49975 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2026-59685 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2026-63045 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2026-63292 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2026-63686 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2026-63718 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2025-49812 HIGH 7.4	http_server 2.4.52 · port 8080
CVE-2023-38709 HIGH 7.3	http_server 2.4.52 · port 8080
CVE-2026-29168 HIGH 7.3	http_server 2.4.52 · port 8080
CVE-2026-44185 HIGH 7.3	http_server 2.4.52 · port 8080
CVE-2026-44186 HIGH 7.3	http_server 2.4.52 · port 8080
CVE-2026-73637 HIGH 7.3	http_server 2.4.52 · port 8080
CVE-2025-65082 MEDIUM 6.5	http_server 2.4.52 · port 8080
CVE-2026-33523 MEDIUM 6.5	http_server 2.4.52 · port 8080
CVE-2026-43951 MEDIUM 6.5	http_server 2.4.52 · port 8080
CVE-2024-24795 MEDIUM 6.3	http_server 2.4.52 · port 8080
CVE-2026-29170 MEDIUM 6.1	http_server 2.4.52 · port 8080
CVE-2023-45802 MEDIUM 5.9	http_server 2.4.52 · port 8080
CVE-2026-44119 MEDIUM 5.5	http_server 2.4.52 · port 8080
CVE-2025-66200 MEDIUM 5.4	http_server 2.4.52 · port 8080
CVE-2022-28614 MEDIUM 5.3	http_server 2.4.52 · port 8080
CVE-2022-37436 MEDIUM 5.3	http_server 2.4.52 · port 8080
CVE-2026-33007 MEDIUM 5.3	http_server 2.4.52 · port 8080
CVE-2026-33857 MEDIUM 5.3	http_server 2.4.52 · port 8080
CVE-2026-34032 MEDIUM 5.3	http_server 2.4.52 · port 8080
CVE-2026-58415 MEDIUM 5.3	http_server 2.4.52 · port 8080
CVE-2026-79768 MEDIUM 5.3	http_server 2.4.52 · port 8080
CVE-2026-33006 MEDIUM 4.8	http_server 2.4.52 · port 8080

Only affects another platform (3)

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 MEDIUM 1

CVE	Software
CVE-2024-40898 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2024-43394 HIGH 7.5	http_server 2.4.52 · port 8080
CVE-2022-28330 MEDIUM 5.3	http_server 2.4.52 · port 8080

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.

Hostnames pointing to this address

4 names · as answered by each domain's own name servers

log.cloudybus.comfirst seen 2026-10-11

log-test.cloudybus.comfirst seen 2026-10-11

map.cloudybus.comfirst seen 2026-10-11

s3.cloudybus.comfirst seen 2026-10-11

Report an issue with this page