gnutls: double free in X.509 name constraints deinitialization after failed memory allocation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| GnuTLS Project | GnuTLS | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Gnu | Gnutls |
|
Vendor Solution
Backport upstream commit "x509: make name constraints deinitialization idempotent", or update to GnuTLS 3.8.14.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.376% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gnu
Gnu gnutls |
|
| Vendors & Products |
Gnu
Gnu gnutls |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A double free in the X.509 name constraints enforcement of GnuTLS 3.8.13 on all platforms allows a remote attacker to cause a denial of service (application crash) via a certificate chain containing a NameConstraints extension processed while the application is under memory pressure. When an already populated name constraints object is reinitialized, previously freed list pointers are not cleared, so a memory allocation failure precisely at reinitialization leaves a dangling pointer that is freed again during a later cleanup. | |
| Title | gnutls: double free in X.509 name constraints deinitialization after failed memory allocation | |
| Weaknesses | CWE-415 | |
| References |
| |
| Metrics |
cvssV3_1
|