Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[<Debian GNU/Linux 10 (buster)>] <Vulnerability in OpenSSH server (CVE-2024-6387)> #1580

Closed
brookerrj opened this issue Jul 2, 2024 · 6 comments
Assignees
Labels
how-to How to issues reported by users solved stale 15 days without activity triage Triage is needed

Comments

@brookerrj
Copy link

Describe your issue as much as you can

I'm assuming that the OpenSSH server vulnerability (CVE-2024-6387) is present in Debian GNU/Linux 10 (buster)?
How can I get fixes for this version? Will there be a fix available in the unattended-upgrades for this version?

Versions on my server:

bitnami@wordpress-1-vm:~$ sudo dpkg -l | grep ssh
ii libssh2-1:amd64 1.8.0-2.1+deb10u1 amd64 SSH2 client-side library
ii openssh-client 1:7.9p1-10+deb10u4 amd64 secure shell (SSH) client, for secure access to remote machines

ii openssh-server 1:7.9p1-10+deb10u4 amd64 secure shell (SSH) server, for secure access from remote machines
ii openssh-sftp-server 1:7.9p1-10+deb10u4 amd64 secure shell (SSH) sftp server module, for SFTP access from remote machines
ii ssh 1:7.9p1-10+deb10u4 all secure shell client and server (metapackage)

bitnami@wordpress-1-vm:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster

@brookerrj brookerrj added the how-to How to issues reported by users label Jul 2, 2024
@github-actions github-actions bot added the triage Triage is needed label Jul 2, 2024
@gongomgra
Copy link
Collaborator

Hi @brookerrj,

Thanks for using Bitnami. According to the official Debian website, Debian Buster stopped receiving security updates as of June 30th, 2022. I'm afraid I don't know if Debian Buster is affected by CVE-2024-6387 because it is not listed in the CVE description webpage either. You will need to ask in a more specialized forum for further help on this.

@florence0239
Copy link

florence0239 commented Jul 4, 2024

Describe your issue as much as you can

I'm assuming that the OpenSSH server vulnerability (CVE-2024-6387) is present in Debian GNU/Linux 10 (buster)? How can I get fixes for this version? Will there Official Site be a fix available in the unattended-upgrades for this version?

Versions on my server:

bitnami@wordpress-1-vm:~$ sudo dpkg -l | grep ssh ii libssh2-1:amd64 1.8.0-2.1+deb10u1 amd64 SSH2 client-side library ii openssh-client 1:7.9p1-10+deb10u4 amd64 secure shell (SSH) client, for secure access to remote machines

ii openssh-server 1:7.9p1-10+deb10u4 amd64 secure shell (SSH) server, for secure access from remote machines ii openssh-sftp-server 1:7.9p1-10+deb10u4 amd64 secure shell (SSH) sftp server module, for SFTP access from remote machines ii ssh 1:7.9p1-10+deb10u4 all secure shell client and server (metapackage)

bitnami@wordpress-1-vm:~$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster

Hello,

The OpenSSH server vulnerability (CVE-2024-6387) is a critical issue that affects OpenSSH’s server (sshd) due to a race condition, allowing remote attackers to execute arbitrary code without authentication12.

For Debian GNU/Linux 10 (buster), here are the steps to address this vulnerability:

Check for Updates:
Regularly check the Debian security tracker for updates related to CVE-2024-63871.
Use the following command to update your package list and upgrade your packages
sudo apt update && sudo apt upgrade

Unattended Upgrades:
Ensure that unattended-upgrades is configured to automatically apply security updates. You can install and configure it using:
sudo apt install unattended-upgrades sudo dpkg-reconfigure --priority=low unattended

Best Regards,
florence023

Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Jul 20, 2024
@brookerrj
Copy link
Author

@florence0239 Thank you for your feedback. I shall try to implement your solution in the next few days. I just need to make sure all is properly backed up first.

@github-actions github-actions bot removed the stale 15 days without activity label Jul 26, 2024
Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Aug 10, 2024
Copy link

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
how-to How to issues reported by users solved stale 15 days without activity triage Triage is needed
Projects
None yet
Development

No branches or pull requests

4 participants