<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl/crypto, branch OpenSSL_1_1_1w</title>
<subtitle>TLS/SSL and crypto library.</subtitle>
<id>http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_1_1w</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_1_1w'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/'/>
<updated>2023-09-11T14:07:52Z</updated>
<entry>
<title>Copyright year updates</title>
<updated>2023-09-11T14:07:52Z</updated>
<author>
<name>Tomas Mraz</name>
<email>tomas@openssl.org</email>
</author>
<published>2023-09-11T14:07:52Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=dabf4696d4101eee8b89e30b009a3531987d4f71'/>
<id>urn:sha1:dabf4696d4101eee8b89e30b009a3531987d4f71</id>
<content type='text'>
Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
Release: yes
</content>
</entry>
<entry>
<title>Fix error handling in CMS_EncryptedData_encrypt</title>
<updated>2023-09-11T08:22:43Z</updated>
<author>
<name>Bernd Edlinger</name>
<email>bernd.edlinger@hotmail.de</email>
</author>
<published>2023-09-07T16:05:44Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=13dd772f61d149628a768d987828aa6dbc72fb31'/>
<id>urn:sha1:13dd772f61d149628a768d987828aa6dbc72fb31</id>
<content type='text'>
That caused several memory leaks in case of error.
Also when the CMS object that is created by CMS_EncryptedData_encrypt
is not used in the normal way, but instead just deleted
by CMS_ContentInfo_free some memory was lost.

Fixes #21985

Reviewed-by: Dmitry Belyavskiy &lt;beldmit@gmail.com&gt;
Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/22008)
</content>
</entry>
<entry>
<title>Fix a possbile memleak in rsa_pub_encode</title>
<updated>2023-09-09T14:37:56Z</updated>
<author>
<name>Bernd Edlinger</name>
<email>bernd.edlinger@hotmail.de</email>
</author>
<published>2023-09-07T17:22:25Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=b13ef5e90a1d9c73f6c548ab5557a939a09744e0'/>
<id>urn:sha1:b13ef5e90a1d9c73f6c548ab5557a939a09744e0</id>
<content type='text'>
That seems to be only an issue for RSA-PSS with parameters.
Spotted by code review, so it looks like there is no test coverage for this.

Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
Reviewed-by: Hugo Landau &lt;hlandau@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/22007)
</content>
</entry>
<entry>
<title>Fix a possible memleak in eckey_priv_encode</title>
<updated>2023-09-09T14:37:55Z</updated>
<author>
<name>Bernd Edlinger</name>
<email>bernd.edlinger@hotmail.de</email>
</author>
<published>2023-09-07T15:38:50Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=7c51c0e56a0f21912f4504c7a06c21eb4bc43c85'/>
<id>urn:sha1:7c51c0e56a0f21912f4504c7a06c21eb4bc43c85</id>
<content type='text'>
Additionally use OPENSSL_clear_free on the private
key data in case of error.

Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
Reviewed-by: Hugo Landau &lt;hlandau@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/22007)
</content>
</entry>
<entry>
<title>Avoid clobbering non-volatile XMM registers</title>
<updated>2023-09-02T08:29:10Z</updated>
<author>
<name>Bernd Edlinger</name>
<email>bernd.edlinger@hotmail.de</email>
</author>
<published>2023-08-22T14:07:30Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=a632d534c73eeb3e3db8c7540d811194ef7c79ff'/>
<id>urn:sha1:a632d534c73eeb3e3db8c7540d811194ef7c79ff</id>
<content type='text'>
This affects some Poly1305 assembler functions
which are only used for certain CPU types.

Remove those functions for Windows targets,
as a simple interim solution.

Fixes #21522

Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
Reviewed-by: Paul Dale &lt;pauli@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/21808)

(cherry picked from commit 7b8e27bc2e02238986d89ef0ece067ec1b48e165)
</content>
</entry>
<entry>
<title>Fix EVP_PKEY_asn1_copy</title>
<updated>2023-08-16T08:54:05Z</updated>
<author>
<name>hangze</name>
<email>hangzegao@gmail.com</email>
</author>
<published>2023-08-03T03:38:29Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=47793328424b4d61956eb7c06d601680c233987d'/>
<id>urn:sha1:47793328424b4d61956eb7c06d601680c233987d</id>
<content type='text'>
Add the copy of the omitted ASN1 public key method and
other members.

Reviewed-by: Bernd Edlinger &lt;bernd.edlinger@hotmail.de&gt;
Reviewed-by: Dmitry Belyavskiy &lt;beldmit@gmail.com&gt;
(Merged from https://github.com/openssl/openssl/pull/21125)
</content>
</entry>
<entry>
<title>Copyright year updates</title>
<updated>2023-08-01T13:51:30Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2023-08-01T13:51:30Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=9c7d3022d633b34c82a0d1e20e8f5cb75e21e64b'/>
<id>urn:sha1:9c7d3022d633b34c82a0d1e20e8f5cb75e21e64b</id>
<content type='text'>
Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
Release: yes
</content>
</entry>
<entry>
<title>DH_check(): Do not try checking q properties if it is obviously invalid</title>
<updated>2023-07-31T13:30:37Z</updated>
<author>
<name>Tomas Mraz</name>
<email>tomas@openssl.org</email>
</author>
<published>2023-07-21T09:39:41Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=91ddeba0f2269b017dc06c46c993a788974b1aa5'/>
<id>urn:sha1:91ddeba0f2269b017dc06c46c993a788974b1aa5</id>
<content type='text'>
If  |q| &gt;= |p| then the q value is obviously wrong as q
is supposed to be a prime divisor of p-1.

We check if p is overly large so this added test implies that
q is not large either when performing subsequent tests using that
q value.

Otherwise if it is too large these additional checks of the q value
such as the primality test can then trigger DoS by doing overly long
computations.

Fixes CVE-2023-3817

Reviewed-by: Paul Dale &lt;pauli@openssl.org&gt;
Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/21551)
</content>
</entry>
<entry>
<title>Make DH_check set some error bits in recently added error</title>
<updated>2023-07-26T11:23:15Z</updated>
<author>
<name>Bernd Edlinger</name>
<email>bernd.edlinger@hotmail.de</email>
</author>
<published>2023-07-23T12:27:54Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=eec805ee71356c06f9a86192fa06507c3bb92b09'/>
<id>urn:sha1:eec805ee71356c06f9a86192fa06507c3bb92b09</id>
<content type='text'>
The pre-existing error cases where DH_check returned zero
are not related to the dh params in any way, but are only
triggered by out-of-memory errors, therefore having *ret
set to zero feels right, but since the new error case is
triggered by too large p values that is something different.
On the other hand some callers of this function might not
be prepared to handle the return value correctly but only
rely on *ret. Therefore we set some error bits in *ret as
additional safety measure.

Reviewed-by: Paul Dale &lt;pauli@openssl.org&gt;
Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/21533)
</content>
</entry>
<entry>
<title>Fix DH_check() excessive time with over sized modulus</title>
<updated>2023-07-19T09:24:06Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2023-07-06T15:36:35Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=8780a896543a654e757db1b9396383f9d8095528'/>
<id>urn:sha1:8780a896543a654e757db1b9396383f9d8095528</id>
<content type='text'>
The DH_check() function checks numerous aspects of the key or parameters
that have been supplied. Some of those checks use the supplied modulus
value even if it is excessively large.

There is already a maximum DH modulus size (10,000 bits) over which
OpenSSL will not generate or derive keys. DH_check() will however still
perform various tests for validity on such a large modulus. We introduce a
new maximum (32,768) over which DH_check() will just fail.

An application that calls DH_check() and supplies a key or parameters
obtained from an untrusted source could be vulnerable to a Denial of
Service attack.

The function DH_check() is itself called by a number of other OpenSSL
functions. An application calling any of those other functions may
similarly be affected. The other functions affected by this are
DH_check_ex() and EVP_PKEY_param_check().

CVE-2023-3446

Reviewed-by: Paul Dale &lt;pauli@openssl.org&gt;
Reviewed-by: Tom Cosgrove &lt;tom.cosgrove@arm.com&gt;
Reviewed-by: Bernd Edlinger &lt;bernd.edlinger@hotmail.de&gt;
Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/21452)
</content>
</entry>
</feed>
