- Server
- SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.15
- Host key
- ssh-ed25519 e88969b06c21088a…
Raw response
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.15
Host
217.68.43.40
As of our latest check on 2026-06-08, 217.68.43.40 (GDM Konsult AB, AS39078, Sweden) had 3 open ports (22, 2000, 20080) and 22 known CVEs.
Known CVEs on this host
3open ports
0names pointing here
22known CVEs
0known exploited
Open ports and CVEs as of our latest check of this host, 2026-06-08.
CVEs by severity: HIGH 5 MEDIUM 10 LOW 7
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: 91 from an older observation (http_server 2.4.18; matched 2026-06-08). See them
Not counted: 14 fixed by the distribution (openssh 8.9p1). See them
- Network
- GDM Konsult AB AS39078
- Open ports
- 22, 2000, 20080 · at our latest check, 2026-06-08
- Location
- Sweden SE
- Route
- 217.68.32.0/20 · announced by GDM Konsult AB AS39078 RPKI valid
- Organisation
- GDM Konsult AB
- Registry network
- kund · 217.68.40.0 - 217.68.47.255 · RIPE
- Abuse contact
- [email protected] · for kund
- First seen
- 2026-06-08 08:37 UTC
- Last seen alive
- 2026-06-08 08:37 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 (1)
Vulnerabilities
Fixed by the distribution (14)
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: CRITICAL 2 HIGH 3 MEDIUM 5 LOW 4
| CVE | Software |
|---|---|
| CVE-2023-28531 CRITICAL 9.8 | openssh 8.9p1 · port 22 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 8.9p1 · port 22 |
| CVE-2024-6387 HIGH 8.1 | openssh 8.9p1 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 8.9p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 8.9p1 · port 22 |
| CVE-2025-26465 MEDIUM 6.8 | openssh 8.9p1 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 8.9p1 · port 22 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 8.9p1 · port 22 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 8.9p1 · port 22 |
| CVE-2023-51384 MEDIUM 5.5 | openssh 8.9p1 · port 22 |
| CVE-2025-32728 LOW 3.8 | openssh 8.9p1 · port 22 |
| CVE-2025-61984 LOW 3.6 | openssh 8.9p1 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 8.9p1 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 8.9p1 · port 22 |
From an older observation (91)
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-06-08). They are not counted above; 3 of them are known to be exploited.
CVEs by severity: CRITICAL 21 HIGH 41 MEDIUM 29
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.18 |
| CVE-2021-40438 CRITICAL 9.0 known exploited | http_server 2.4.18 |
| CVE-2019-0211 HIGH 7.8 known exploited | http_server 2.4.18 |
| CVE-2017-3167 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2017-3169 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2017-7679 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2018-1312 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2021-26691 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2021-39275 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2022-23943 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.18 |
| CVE-2017-9788 CRITICAL 9.1 | http_server 2.4.18 |
| CVE-2019-10082 CRITICAL 9.1 | http_server 2.4.18 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.4.18 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.4.18 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4.18 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.18 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.18 |
| CVE-2021-44224 HIGH 8.2 | http_server 2.4.18 |
| CVE-2016-5387 HIGH 8.1 | http_server 2.4.18 |
| CVE-2017-15715 HIGH 8.1 | http_server 2.4.18 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.18 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4.18 |
| CVE-2016-4979 HIGH 7.5 | http_server 2.4.18 |
| CVE-2016-8740 HIGH 7.5 | http_server 2.4.18 |
| CVE-2016-8743 HIGH 7.5 | http_server 2.4.18 |
| CVE-2017-15710 HIGH 7.5 | http_server 2.4.18 |
| CVE-2017-9798 HIGH 7.5 | http_server 2.4.18 |
| CVE-2018-1303 HIGH 7.5 | http_server 2.4.18 |
| CVE-2018-1333 HIGH 7.5 | http_server 2.4.18 |
| CVE-2018-17199 HIGH 7.5 | http_server 2.4.18 |
| CVE-2019-0217 HIGH 7.5 | http_server 2.4.18 |
| CVE-2021-26690 HIGH 7.5 | http_server 2.4.18 |
| CVE-2021-33193 HIGH 7.5 | http_server 2.4.18 |
| CVE-2021-34798 HIGH 7.5 | http_server 2.4.18 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.4.18 |
| CVE-2022-26377 HIGH 7.5 | http_server 2.4.18 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.4.18 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.4.18 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.18 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.18 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.18 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.18 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.18 |
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.18 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.18 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.18 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.18 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.18 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.18 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.18 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.18 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.18 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.18 |
| CVE-2020-35452 HIGH 7.3 | http_server 2.4.18 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.18 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.18 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.18 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.18 |
| CVE-2016-4975 MEDIUM 6.1 | http_server 2.4.18 |
| CVE-2019-10092 MEDIUM 6.1 | http_server 2.4.18 |
| CVE-2019-10098 MEDIUM 6.1 | http_server 2.4.18 |
| CVE-2020-1927 MEDIUM 6.1 | http_server 2.4.18 |
| CVE-2016-1546 MEDIUM 5.9 | http_server 2.4.18 |
| CVE-2018-11763 MEDIUM 5.9 | http_server 2.4.18 |
| CVE-2018-1301 MEDIUM 5.9 | http_server 2.4.18 |
| CVE-2018-1302 MEDIUM 5.9 | http_server 2.4.18 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.18 |
| CVE-2020-13938 MEDIUM 5.5 | http_server 2.4.18 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.18 |
| CVE-2018-1283 MEDIUM 5.3 | http_server 2.4.18 |
| CVE-2018-17189 MEDIUM 5.3 | http_server 2.4.18 |
| CVE-2019-0196 MEDIUM 5.3 | http_server 2.4.18 |
| CVE-2019-0220 MEDIUM 5.3 | http_server 2.4.18 |
| CVE-2019-17567 MEDIUM 5.3 | http_server 2.4.18 |
| CVE-2020-11985 MEDIUM 5.3 | http_server 2.4.18 |
| CVE-2020-1934 MEDIUM 5.3 | http_server 2.4.18 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.4.18 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.4.18 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4.18 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.18 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.18 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.18 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.18 |
| CVE-2016-8612 MEDIUM 4.3 | http_server 2.4.18 |
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.