Add CVE-2023-4807 fix to CHANGES.md and NEWS.md
Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Hugo Landau <hlandau@openssl.org> Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from https://github.com/openssl/openssl/pull/22033)
This commit is contained in:
parent
02f84b02e8
commit
0be7510f49
23
CHANGES.md
23
CHANGES.md
@ -457,7 +457,27 @@ OpenSSL 3.1
|
|||||||
|
|
||||||
### Changes between 3.1.2 and 3.1.3 [xx XXX xxxx]
|
### Changes between 3.1.2 and 3.1.3 [xx XXX xxxx]
|
||||||
|
|
||||||
* none yet
|
* Fix POLY1305 MAC implementation corrupting XMM registers on Windows.
|
||||||
|
|
||||||
|
The POLY1305 MAC (message authentication code) implementation in OpenSSL
|
||||||
|
does not save the contents of non-volatile XMM registers on Windows 64
|
||||||
|
platform when calculating the MAC of data larger than 64 bytes. Before
|
||||||
|
returning to the caller all the XMM registers are set to zero rather than
|
||||||
|
restoring their previous content. The vulnerable code is used only on newer
|
||||||
|
x86_64 processors supporting the AVX512-IFMA instructions.
|
||||||
|
|
||||||
|
The consequences of this kind of internal application state corruption can
|
||||||
|
be various - from no consequences, if the calling application does not
|
||||||
|
depend on the contents of non-volatile XMM registers at all, to the worst
|
||||||
|
consequences, where the attacker could get complete control of the
|
||||||
|
application process. However given the contents of the registers are just
|
||||||
|
zeroized so the attacker cannot put arbitrary values inside, the most likely
|
||||||
|
consequence, if any, would be an incorrect result of some application
|
||||||
|
dependent calculations or a crash leading to a denial of service.
|
||||||
|
|
||||||
|
([CVE-2023-4807])
|
||||||
|
|
||||||
|
*Bernd Edlinger*
|
||||||
|
|
||||||
### Changes between 3.1.1 and 3.1.2 [1 Aug 2023]
|
### Changes between 3.1.1 and 3.1.2 [1 Aug 2023]
|
||||||
|
|
||||||
@ -20253,6 +20273,7 @@ ndif
|
|||||||
|
|
||||||
<!-- Links -->
|
<!-- Links -->
|
||||||
|
|
||||||
|
[CVE-2023-4807]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-4807
|
||||||
[CVE-2023-3817]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-3817
|
[CVE-2023-3817]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-3817
|
||||||
[CVE-2023-3446]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-3446
|
[CVE-2023-3446]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-3446
|
||||||
[CVE-2023-2975]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-2975
|
[CVE-2023-2975]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-2975
|
||||||
|
4
NEWS.md
4
NEWS.md
@ -54,7 +54,8 @@ OpenSSL 3.1
|
|||||||
|
|
||||||
### Major changes between OpenSSL 3.1.2 and OpenSSL 3.1.3 [under development]
|
### Major changes between OpenSSL 3.1.2 and OpenSSL 3.1.3 [under development]
|
||||||
|
|
||||||
* none
|
* Fix POLY1305 MAC implementation corrupting XMM registers on Windows
|
||||||
|
([CVE-2023-4807])
|
||||||
|
|
||||||
### Major changes between OpenSSL 3.1.1 and OpenSSL 3.1.2 [1 Aug 2023]
|
### Major changes between OpenSSL 3.1.1 and OpenSSL 3.1.2 [1 Aug 2023]
|
||||||
|
|
||||||
@ -1501,6 +1502,7 @@ OpenSSL 0.9.x
|
|||||||
|
|
||||||
<!-- Links -->
|
<!-- Links -->
|
||||||
|
|
||||||
|
[CVE-2023-4807]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-4807
|
||||||
[CVE-2023-3817]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-3817
|
[CVE-2023-3817]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-3817
|
||||||
[CVE-2023-3446]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-3446
|
[CVE-2023-3446]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-3446
|
||||||
[CVE-2023-2975]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-2975
|
[CVE-2023-2975]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-2975
|
||||||
|
Loading…
x
Reference in New Issue
Block a user