mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2025-12-30 16:24:05 +01:00
Add CVE-2022-4203 for openssl-src (#1577)
This commit is contained in:
31
crates/openssl-src/RUSTSEC-0000-0000.md
Normal file
31
crates/openssl-src/RUSTSEC-0000-0000.md
Normal file
@@ -0,0 +1,31 @@
|
||||
```toml
|
||||
[advisory]
|
||||
id = "RUSTSEC-0000-0000"
|
||||
package = "openssl-src"
|
||||
aliases = ["CVE-2022-4203"]
|
||||
categories = ["denial-of-service", "memory-exposure"]
|
||||
date = "2023-02-07"
|
||||
url = "https://www.openssl.org/news/secadv/20230207.txt"
|
||||
[versions]
|
||||
patched = [">= 300.0.12"]
|
||||
unaffected = ["< 300.0.0"]
|
||||
```
|
||||
|
||||
# X.509 Name Constraints Read Buffer Overflow
|
||||
|
||||
A read 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.
|
||||
|
||||
The read buffer overrun might result in a crash which could lead to
|
||||
a denial of service attack. In theory it could also result in the disclosure
|
||||
of private memory contents (such as private keys, or sensitive plaintext)
|
||||
although we are not aware of any working exploit leading to memory
|
||||
contents disclosure as of the time of release of this advisory.
|
||||
|
||||
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.
|
||||
Reference in New Issue
Block a user