8/3/2026 at 3:30:51 AM
Hey, is it not just a simple honeypot reverse hack ssh server?People understand that reverse hacking can happen when connecting to random ssh server, right?
by 3dedb728-3f77
8/3/2026 at 9:52:52 AM
People understand that such "reverse hacking" can happen when their browser connects to any site (including all the indirect connections from dependent resources), right? Or when resolving any domain name? Or when even just pinging an IP?The risk is far, far lower than browsing the internet. Unlike the massive surface of a browser and all the libraries and processes it is comprised of, the OpenSSH client is a tiny, with a singular purpose, contained in a small and very well-vetted codebase.
From the perspective of connecting to a foreign network service, the OpenSSH client is about the safest thing you can possibly use. Note the use of relative words here - not claiming it is 100% bug-free.
(The main caveat is that you can manually configure the client to do unsafe things, like writing a configuration by hand that enables X forwarding or agent forwarding by default for any host - but you can also actively disable sandboxing in your web browser or run everything as root, and we will never be able to stop you from actively making things insecure.)
by arghwhat
8/3/2026 at 12:29:46 PM
There's also the terminal to consider, via terminal escape sequences.by jolmg
8/3/2026 at 4:41:30 AM
> People understand that reverse hacking can happen when connecting to random ssh server, right?No, actually, I've never heard of such a vector. How would that work?
by scubbo
8/3/2026 at 5:12:16 AM
An ssh server would exploit a vulnerability in the ssh client when it connects.For example, openssh has both a client and server. There’s been vulnerabilities in openssh, in the client. Those vulnerabilities aren’t reachable unless you’re connecting to a server attempting to exploit you, so the risk is quite low because you know and trust most servers you’re connecting to with ssh.
To sum it up: Connecting to this server is probably fine, but in doing so most people are doing something significantly riskier without realizing it.
by jerrythegerbil
8/3/2026 at 6:10:09 AM
There has never been a real-world OpenSSH exploit that allows a server to RCE a client that connected to it without a bunch of dubious qualifiers. Connecting to a random SSH server is much, much less dangerous than running a random binary or executing a random curl install script, both of which people do all the time, and is probably about on par with the likelihood of a random website escaping your browser's sandbox and RCEing you.by applfanboysbgon
8/3/2026 at 11:05:24 AM
Web browsers are generally built with security in mind. Terminal emulators surely much less so. The OpenSSH client probably sits somewhat in between, generally developed with security in mind, but not necessarily consistently expecting malicious servers.by dinkelberg
8/3/2026 at 8:13:46 AM
Agreed, bugs in the terminal emulator are probably more concerning. The attack surface of those is much larger (there are some pretty wild ANSI escape sequences, and terminal emulators are often granted pretty wide disk access permissions on systems that have them if they're also used for local development).by lxgr
8/3/2026 at 12:06:15 PM
I believe the recent cve-2026-55200 in libssh2 (client-side library) was allowing exactly this. https://nvd.nist.gov/vuln/detail/cve-2026-55200 ("Remote attackers can send crafted SSH packets with excessively large packet_length values to corrupt heap memory and achieve remote code execution.")Of course the other abouts that you whatted (such as random curl install scripts, binaries, etc.) are still more dangerous.
by soblemprolver
8/3/2026 at 1:49:39 PM
OpenSSH doesn't use this library.by fulafel
8/3/2026 at 2:01:30 PM
Good to know, but OpenSSH is not the scope here.by soblemprolver
8/3/2026 at 3:53:26 PM
Per Red Hat:> The integer overflow provides uncontrolled access to the heap, which reliably crashes the client process but is unlikely to achieve remote code execution in practice. Weaponizing the overflow for code execution would require a separate information disclosure vulnerability to defeat ASLR, along with a specific heap layout to place exploitable structures adjacent to the undersized allocation.
---
> abouts that you whatted
"Whataboutism" is perhaps the most infuriating and wildly misused word in the English language. Pointing out that somebody is scaremongering about an action that is significantly less dangerous than other everyday actions people take on their computers is not a fallacy. It is directly relevant to evaluating risk. Yes, technically there could be some critical bug that allows the posited thing to happen, but in reality it just doesn't happen. If it did happen, nobody would blow their once-in-decades exploit on pranking some people on a forum.
by applfanboysbgon
8/3/2026 at 6:54:51 AM
If you properly set up your ssh client (No agent forwarding or X11 forwarding)by Oxodao
8/3/2026 at 7:56:18 AM
Terminal, too; some escape sequences are able to perform attacks in old or buggy terminal emulators.by LoganDark
8/3/2026 at 1:51:50 PM
Even newer ones. Iterm2 had CVE-2026-41253 recently. Or things like Tmux.by tyingq
8/3/2026 at 3:20:09 PM
Yes, I was thinking of iTerm2. "Older" means not the latest release and "buggy" includes well-intentioned vulnerabilities.by LoganDark
8/3/2026 at 4:19:53 PM
Sure. 3.6.9 (which was affected) was the most recent iTerm2 when that CVE came out.by tyingq
8/3/2026 at 4:50:38 PM
Hence "or"by LoganDark
8/3/2026 at 8:28:39 AM
Malicious servers can send malicious terminal escape codes. For example https://www.sentinelone.com/vulnerability-database/cve-2026-...by FooBarWidget
8/3/2026 at 6:05:36 AM
> To sum it up: Connecting to this server is probably fineAnd what are you basing this statement on?
by teiferer
8/3/2026 at 11:35:11 AM
theoretically a browser could have the same vulnerability and has a vastly higher attack surface.has there ever been an example of such a vulnerability in openssh?
by pydry
8/3/2026 at 12:31:05 PM
Here is a recent example. Currently unpatched in Debian stable.https://www.cve.org/CVERecord?id=CVE-2026-60002
As I understood this, a malicious server can change its host key somewhere during key exchange and trigger a use-after-free in the client, which might be exploitable for code execution.
by mr_mitm
8/3/2026 at 5:05:10 AM
Vulnerability in your ssh client (unlikely) or terminal emulator (more common but lower reach).by krautsauer
8/3/2026 at 7:21:25 AM
Terminal emulators have, on occasion, had all kinds of interesting escape codes that I wouldn't want to expose to an attacker. Whether this is even a true "vulnerability" is somewhat a matter of opinion (in the sense that the feature works as designed, but that's maybe a bad thing).by yjftsjthsd-h
8/3/2026 at 7:12:44 AM
Agent forwarding would be pretty big, if it for example pushed your git credentials to the remote host.by bulder
8/3/2026 at 8:16:13 PM
Would like to clarify that all my code is open source at https://github.com/jeninh/ssh.place , even the deployment is triggered through GitHub actions. I'm also a teen and not too familiar with most of these terms, so I might be forgetting something.by jeninh
8/3/2026 at 7:12:56 AM
Prove it, I'll connect to any server you point me to, using default openssh client flags.by neuroticnews25
8/3/2026 at 4:02:27 AM
Is that more likely than getting hacked when visiting a website?by bulbar
8/3/2026 at 9:54:18 AM
Are we all pretending we have no empirical data on this? How many RCEs has there been in popular web browsers over the past two decades (dozens? hundreds?), compared to how many RCEs there has been in the OpenSSH client (perhaps we can make it one if we include xterm in that)?by xorcist
8/3/2026 at 5:13:21 AM
Visiting a random website is the normal use of HTTP. With SSH, there might be assumptions of connecting to a trusted server you have an account with and likely own. It's not very normal to ssh to a random server.by jolmg
8/3/2026 at 6:07:29 AM
> likely ownI don't know how you are using ssh, but most ssh servers that I have connected to in my life, and still do, I don't own. Some of them I barely trust.
by teiferer
8/3/2026 at 6:35:07 AM
The ones I connect to the most often from my personal laptop I don’t physically own but I do pay to rent them and I installed the OS on them myself.by QuantumNomad_
8/3/2026 at 9:58:40 AM
The main ones I don’t own are VPS servers from fairly large providers, or GitHub.by hdgvhicv
8/3/2026 at 2:16:06 PM
When I said "own", I meant more in the sense of personally administering. It's like how you own a domain, but you're really renting it from a registrar. Rented hardware and VPSs count, as well as other servers/hosts you're responsible for.by jolmg
8/3/2026 at 2:52:33 PM
I got that, and I'm not saying that it doesn't apply to you, but it surely does not apply to everybody.by teiferer
8/3/2026 at 2:23:13 PM
This is simply not trueby singpolyma3
8/3/2026 at 3:48:09 AM
What exactly is the mechanism by which you think that an SSH RCE is "simple"?by applfanboysbgon
8/3/2026 at 3:52:00 AM
Not OP, but agent forwarding is a significant concern.by dlgeek
8/3/2026 at 8:05:51 AM
Is it enabled by default though?AFAIK: No
by SXX
8/3/2026 at 9:08:55 AM
It's not, but there is likely a small number people who have something like this configured: Host *
ForwardAgent yes
by jamie0
8/3/2026 at 9:07:44 AM
Try me.by UqWBcuFx6NV4r