Raw response
SSH-2.0-OpenSSH_6.0p1 Debian-4+deb7u7
Host
Tags: End-of-life software
As of our latest check on 2026-05-25, 83.223.82.44 (sinma GmbH, AS8875, Germany) had 2 open ports (22, 80) and 51 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-05-25.
CVEs by severity: CRITICAL 2 HIGH 16 MEDIUM 27 LOW 6
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: 54 on a distribution build — the fix may be backported (http_server 2.2.22). See them
Not counted: 1 fixed by the distribution (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.
SSH-2.0-OpenSSH_6.0p1 Debian-4+deb7u7
HTTP/1.1 200 OK Date: Mon, 25 May 2026 09:16:09 GMT Server: Apache/2.2.22 (Debian) Last-Modified: Mon, 31 May 2010 07:48:50 GMT ETag: "3201913-2d-487df1664bc80" Accept-Ranges: bytes Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 56 Content-Type: text/html ���(�ͱ�I�O����0��,Q(�/�.V���l�!�`U\QU�f-
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 23 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-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 |
The distribution's security data says the package revision this service shows already has the fix for these CVEs, or that its build is not affected. They are not counted.
CVEs by severity: MEDIUM 1
| CVE | Software |
|---|---|
| CVE-2012-0883 MEDIUM 6.9 | 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.