Re:RegreSSHion: RCE in OpenSSH's server, on glibc-based Linu...
by Arnavion on Monday July 01, 2024 @02:55PM
(#40849138)
>As mentioned elsewhere here, is -D sufficient to avoid exploitation, or is -e necessary as well?
https://github.com/openssh/openssh-portable/blob/V_9_8_P1/ss...
sshd.c handles no_daemon (-D) and log_stderr (-e) independently. log_stderr is what is given to log_init in log.c that gates the call to syslog functions. There is a special case to set log_stderr to true if debug_flag (-d) is set, but nothing for no_daemon.
I can't test it right now though so I may be missing something.
Re:RegreSSHion: RCE in OpenSSH's server, on glibc-based Linu...
by chasil on Monday July 01, 2024 @04:02PM
(#40850002)
I'm on Oracle Linux, and they appear to have already issued a patch for this problem:
openssh-8.7p1-38.0.2.el9.x86_64.rpm
openssh-server-8.7p1-38.0.2.el9.x86_64.rpm
openssh-clients-8.7p1-38.0.2.el9.x86_64.rpm
The changelog addresses the CVE directly. It does not appear that adding the -e directive is necessary with this patch. $ rpm -q --changelog openssh-server | head -3
* Wed Jun 26 2024 Alex Burmashev <[email protected]> - 8.7p1-38.0.2
- Restore dropped earlier ifdef condition for safe _exit(1) call in sshsigdie() [Orabug: 36783468]
Resolves CVE-2024-6387
Re:RegreSSHion: RCE in OpenSSH's server, on glibc-based Linu...
by INTPenis on Tuesday July 02, 2024 @04:33AM
(#40854653)
So in other words, -De is not a workaround. -Dde might be but it will cause more log output than is wanted.
Re:RegreSSHion: RCE in OpenSSH's server, on glibc-based Linu...
by Arnavion on Tuesday July 02, 2024 @04:32PM
(#40860164)
-De is a workaround. -D is not.
Re:RegreSSHion: RCE in OpenSSH's server, on glibc-based Linu...
by babuskov on Tuesday July 02, 2024 @02:30AM
(#40854041)
Speaking of Rocky 9, they suggest to get the new version from the SIG/Security repository:
https://rockylinux.org/news/2024-07-01-rocky-linux-9-cve-202...
"we have started to work on an amd64 exploit, which is much harder because of the stronger ASLR."
On top of writing the exploit to target 32-bit environments, this also requires a DSA key that implements multiple calls to free().
There is a section on "Rocky Linux 9" near the end of the linked advisory where unsuccessful exploit attempts are discussed.