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

CVE-2023-2650 openssl (libssl1.1) 1.1.1n-0+deb11u4 #195

Closed
vomba opened this issue Jun 2, 2023 · 1 comment
Closed

CVE-2023-2650 openssl (libssl1.1) 1.1.1n-0+deb11u4 #195

vomba opened this issue Jun 2, 2023 · 1 comment

Comments

@vomba
Copy link

vomba commented Jun 2, 2023

https://avd.aquasec.com/nvd/cve-2023-0464

reported 3 days ago, and a fix update is available.

@yosifkit
Copy link
Collaborator

yosifkit commented Jun 5, 2023

https://tracker.debian.org/news/1432726/accepted-openssl-111n-0deb11u5-source-into-stable-security/

It looks like there are 4 different OpenSSL CVEs fixed in openssl 1.1.1n-0+deb11u5 in Debian Bullseye and they all seem relatively harmless. Three of them deal with "X.509 policy", which is disabled by default (a user who knows that they use policies can update early with apt-get update+upgrade). The 4th is "not affected" in OpenSSL 1.1.1 (default in Debian Bullseye and below):

In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects,
such as X.509 certificates. This is assumed to not happen in such a way
that it would cause a Denial of Service, so these versions are considered
not affected by this issue in such a way that it would be cause for concern,
and the severity is therefore considered low.

I understand that we should update as soon as possible, but I think that these can wait for one week. This would be just after the release of Debian Bookworm and so we'd be rebuilding the images for that anyway. I'd rather not update the images (including all dependent Docker Official Images) two weeks in a row and cause extra churn for users.

Happy to change my mind if any of these CVEs are more nefarious than I can see.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants