Kritieke kwetsbaarheid OpenSSL versie 3

Pagina: 1
Acties:

Acties:
  • +1 Henk 'm!

  • winux
  • Registratie: April 2003
  • Laatst online: 11:25
OpenSSL heeft aangekondigd dat er een kritieke kwetsbaarheid in versie 3.0.0 en hoger zit. Vandaag 1 november komt er tusen 14:00 en 18:00 een update die de kwetsbaarheid moet oplossen: versie 3.0.7.

Bron: https://mta.openssl.org/p.../2022-October/000238.html
Hello,

The OpenSSL project team would like to announce the forthcoming release
of OpenSSL version 3.0.7.

This release will be made available on Tuesday 1st November 2022 between
1300-1700 UTC.

OpenSSL 3.0.7 is a security-fix release. The highest severity issue
fixed in this release is CRITICAL:

https://www.openssl.org/p...eral/security-policy.html

Yours
The OpenSSL Project Team
Het aandeel OpenSSL versie 3.x zou geschat worden op 1.5% Het merendeel van de OpenSSL versie die gebruikt wordt op internet is versie 1.x

Het NCSC heeft een github pagina gemaakt met een overzicht van leveranciers, welke wel of niet kwetsbaar zijn. Daarnaast zijn er scanning tools beschikbaar om de (interne) infrastructuur te onderzoeken.

https://github.com/NCSC-NL/OpenSSL-2022

Eigen onderzoek wijst uit dat VMware Tools vanaf versie 12 OpenSSL 3.0 gebruikt:
https://docs.vmware.com/e...s-1200-Release-Notes.html
What's New​
OpenSSL version is updated to 3.0.0.
Update
Security advisory 1 november
OpenSSL Security Advisory [01 November 2022]
============================================

X.509 Email Address 4-byte Buffer Overflow (CVE-2022-3602)
==========================================================

Severity: High

A buffer overrun can be triggered in X.509 certificate verification,
specifically in name constraint checking. Note that this occurs
after certificate chain signature verification and requires either a
CA to have signed the malicious certificate or for the application to
continue certificate verification despite failure to construct a path
to a trusted issuer. An attacker can craft a malicious email address
to overflow four attacker-controlled bytes on the stack. This buffer
overflow could result in a crash (causing a denial of service) or
potentially remote code execution.

Many platforms implement stack overflow protections which would mitigate
against the risk of remote code execution. The risk may be further
mitigated based on stack layout for any given platform/compiler.

Pre-announcements of CVE-2022-3602 described this issue as CRITICAL.
Further analysis based on some of the mitigating factors described above
have led this to be downgraded to HIGH. Users are still encouraged to
upgrade to a new version as soon as possible.

In a TLS client, this can be triggered by connecting to a malicious
server. In a TLS server, this can be triggered if the server requests
client authentication and a malicious client connects.

OpenSSL versions 3.0.0 to 3.0.6 are vulnerable to this issue.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.7.

OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.

This issue was reported to OpenSSL on 17th October 2022 by Polar Bear.
The fixes were developed by Dr Paul Dale.

We are not aware of any working exploit that could lead to code execution,
and we have no evidence of this issue being exploited as of the time of
release of this advisory (November 1st 2022).

X.509 Email Address Variable Length Buffer Overflow (CVE-2022-3786)
===================================================================

Severity: High

A buffer overrun can be triggered in X.509 certificate verification,
specifically in name constraint checking. Note that this occurs after
certificate chain signature verification and requires either a CA to
have signed a malicious certificate or for an application to continue
certificate verification despite failure to construct a path to a trusted
issuer. An attacker can craft a malicious email address in a certificate
to overflow an arbitrary number of bytes containing the `.' character
(decimal 46) on the stack. This buffer overflow could result in a crash
(causing a denial of service).

In a TLS client, this can be triggered by connecting to a malicious
server. In a TLS server, this can be triggered if the server requests
client authentication and a malicious client connects.

OpenSSL versions 3.0.0 to 3.0.6 are vulnerable to this issue.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.7.

OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.

This issue was discovered on 18th October 2022 by Viktor Dukhovni while
researching CVE-2022-3602. The fixes were developed by Dr Paul Dale.

We have no evidence of this issue being exploited as of the time of
release of this advisory (November 1st 2022).

References
==========

URL for this Security Advisory:
https://www.openssl.org/news/secadv/20221101.txt

Note: the online version of the advisory may be updated with additional details
over time.

For details of OpenSSL severity classifications please see:
https://www.openssl.org/policies/secpolicy.html

[ Voor 58% gewijzigd door winux op 01-11-2022 17:09 ]


Acties:
  • 0 Henk 'm!

  • Twilkie
  • Registratie: Oktober 2011
  • Laatst online: 15:44
Ubuntu 22.04 LTS heeft OpenSSL 3.0.2 en is dus kwetsbaar

Acties:
  • 0 Henk 'm!

  • winux
  • Registratie: April 2003
  • Laatst online: 11:25
Zojuist is OpenSSL 3.0.7 vrijgegeven en gelijktijdig ook OpenSSL 1.1.1s.

https://www.openssl.org/source/

Acties:
  • 0 Henk 'm!

  • Jazzy
  • Registratie: Juni 2000
  • Nu online

Jazzy

Moderator SSC/PB

Moooooh!

Twilkie schreef op dinsdag 1 november 2022 @ 14:03:
Ubuntu 22.04 LTS heeft OpenSSL 3.0.2 en is dus kwetsbaar
Mmm, inderdaad: https://github.com/NCSC-N...b/main/software/README.md

Vanavond maar even een rondje patchen doen, zou voor Ubuntu niet al te ingewikkeld moeten zijn.

Exchange en Office 365 specialist. Mijn blog.


Acties:
  • 0 Henk 'm!

  • Cyb
  • Registratie: Augustus 2002
  • Niet online

Cyb


Acties:
  • 0 Henk 'm!

  • CH4OS
  • Registratie: April 2002
  • Niet online

CH4OS

It's a kind of magic

Pagina: 1