Описание
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.
Релиз | Статус | Примечание |
---|---|---|
bionic | not-affected | code not present |
devel | not-affected | code not present |
esm-apps/bionic | not-affected | code not present |
esm-apps/xenial | not-affected | code not present |
esm-infra/focal | not-affected | code not present |
focal | not-affected | code not present |
jammy | not-affected | code not present |
kinetic | not-affected | code not present |
lunar | not-affected | code not present |
mantic | not-affected | code not present |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | not-affected | uses system openssl1.0 |
devel | not-affected | uses system openssl |
esm-apps/bionic | not-affected | uses system openssl1.0 |
esm-apps/focal | not-affected | uses system openssl |
esm-apps/jammy | not-affected | code not present |
esm-apps/xenial | not-affected | code not present |
esm-infra-legacy/trusty | not-affected | uses system openssl |
focal | not-affected | uses system openssl |
jammy | not-affected | code not present |
kinetic | not-affected | uses system openssl |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | not-affected | 3.x only |
devel | released | 3.0.8-1ubuntu1 |
esm-infra-legacy/trusty | not-affected | 3.x only |
esm-infra/bionic | not-affected | 3.x only |
esm-infra/focal | not-affected | 3.x only |
esm-infra/xenial | not-affected | 3.x only |
fips-updates/bionic | not-affected | 3.x only |
fips-updates/focal | not-affected | 3.x only |
fips-updates/xenial | not-affected | 3.x only |
fips/bionic | not-affected | 3.x only |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | not-affected | 3.x only |
esm-infra/bionic | not-affected | 3.x only |
esm-infra/focal | DNE | |
focal | DNE | |
jammy | DNE | |
kinetic | DNE | |
trusty | DNE | |
upstream | needs-triage | |
xenial | DNE |
Показывать по
EPSS
4.9 Medium
CVSS3
Связанные уязвимости
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.
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.
A read buffer overrun can be triggered in X.509 certificate verificati ...
openssl-src contains Read Buffer Overflow in X.509 Name Constraint
Уязвимость компонента X509_V_FLAG_CRL_CHECK криптографической библиотеки OpenSSL, позволяющая нарушителю вызвать отказ в обслуживании
EPSS
4.9 Medium
CVSS3