public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Cc: Jonathan McNickle <j_mcnickle@hotmail.com>
Subject: Re: OpenSSL Package Upgrade to 1.1.1L
Date: Wed, 1 Sep 2021 15:40:18 -0600	[thread overview]
Message-ID: <73dc7093-53be-f788-531d-f844a0cc1027@SystematicSw.ab.ca> (raw)
In-Reply-To: <VI1PR06MB5918473FFC0A05EAD0002798F2CD9@VI1PR06MB5918.eurprd06.prod.outlook.com>

On 2021-09-01 08:08, Jonathan McNickle wrote:
> I was wondering if plans were in place to update OpenSSL to version 1.1.1l to fix the latest high sev security issue?
> https://www.openssl.org/news/secadv/20210824.txt

[redirected from patches (Cygwin DLL etc.) to apps (Packages)]

SM2 Decryption Buffer Overflow (CVE-2021-3711) Severity: High is 
probably not a huge concern, as not SM2 is not a commonly specified 
cipher suite, except possibly in China; although the Read buffer 
overruns processing ASN.1 strings (CVE-2021-3712) Severity: Moderate is 
fairly serious, as OpenSSL assumes some ASN1 strings with given length 
are also nul terminated when they need not be, allowing DoS and 
disclosures.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

           reply	other threads:[~2021-09-01 21:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <VI1PR06MB5918473FFC0A05EAD0002798F2CD9@VI1PR06MB5918.eurprd06.prod.outlook.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=73dc7093-53be-f788-531d-f844a0cc1027@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-apps@cygwin.com \
    --cc=j_mcnickle@hotmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).