X.509 Name Constraints Read Buffer Overflow
cve-program · CVE-2022-4203
PublishedA 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.
Read the publisher's advisoryeuvd · EUVD-2023-0809
PublishedA 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.
Read the publisher's advisorynvd · CVE-2022-4203
PublishedA 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.
Read the publisher's advisoryosv · GHSA-w67w-mw4j-8qrv
PublishedA 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.
Read the publisher's advisoryosv · RUSTSEC-2023-0008
PublishedA 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.
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2022-4203
PublishedX.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.
- Source published
- 24 Feb 2023 14:53:08 UTC
- Source modified
- 4 Nov 2025 19:14:06 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
euvd · EUVD-2023-0809
PublishedA read buffer overrun can be triggered in X.509 certificate verification,
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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Feb 24, 2023, 2:53:08 PM
dateUpdated: Nov 4, 2025, 7:14:06 PM
13 related source bulletins · separate from aliases
ICSA-25-065-01: Hitachi Energy PCU400
CVE-2023-0286 · CVE-2023-0217 · CVE-2023-0216 · CVE-2023-0401 · CVE-2023-0215 · CVE-2022-4450 · CVE-2022-4304 · CVE-2022-4203
WID-SEC-W-2024-1591: Juniper JUNOS: Mehrere Schwachstellen
CVE-2006-20001 · CVE-2007-5846 · CVE-2008-6123 · CVE-2011-1473 · CVE-2011-5094 · CVE-2012-6151 · CVE-2014-10064 · CVE-2014-2285 · CVE-2014-2310 · CVE-2014-3565 · CVE-2014-7191 · CVE-2014-8882 · CVE-2015-5621 · CVE-2015-8100 · CVE-2015-9262 · CVE-2016-1000232 · CVE-2016-10540 · CVE-2016-4658 · CVE-2017-1000048 · CVE-2017-15010 · CVE-2018-18065 · CVE-2018-20834 · CVE-2018-3737 · CVE-2018-7408 · CVE-2019-10081 · CVE-2019-10082 · CVE-2019-10092 · CVE-2019-10097 · CVE-2019-10098 · CVE-2019-11719 · CVE-2019-11727 · CVE-2019-11756 · CVE-2019-16775 · CVE-2019-16776 · CVE-2019-16777 · CVE-2019-17006 · CVE-2019-17023 · CVE-2019-17567 · CVE-2019-20149 · CVE-2019-20892 · CVE-2019-9517 · CVE-2020-11668 · CVE-2020-11984 · CVE-2020-11993 · CVE-2020-12362 · CVE-2020-12400 · CVE-2020-12401 · CVE-2020-12402 · CVE-2020-12403 · CVE-2020-13938 · CVE-2020-13950 · CVE-2020-14145 · CVE-2020-15861 · CVE-2020-15862 · CVE-2020-1927 · CVE-2020-1934 · CVE-2020-28469 · CVE-2020-28502 · CVE-2020-35452 · CVE-2020-36049 · CVE-2020-6829 · CVE-2020-7660 · CVE-2020-7754 · CVE-2020-7774 · CVE-2020-8648 · CVE-2020-9490 · CVE-2021-22543 · CVE-2021-2342 · CVE-2021-23440 · CVE-2021-2356 · CVE-2021-2372 · CVE-2021-2385 · CVE-2021-2389 · CVE-2021-2390 · CVE-2021-25745 · CVE-2021-25746 · CVE-2021-25748 · CVE-2021-26690 · CVE-2021-26691 · CVE-2021-27290 · CVE-2021-29469 · CVE-2021-30641 · CVE-2021-31535 · CVE-2021-31618 · CVE-2021-3177 · CVE-2021-32803 · CVE-2021-32804 · CVE-2021-33033 · CVE-2021-33034 · CVE-2021-33193 · CVE-2021-3347 · CVE-2021-33909 · CVE-2021-34798 · CVE-2021-35604 · CVE-2021-35624 · CVE-2021-36160 · CVE-2021-37701 · CVE-2021-37712 · CVE-2021-37713 · CVE-2021-3803 · CVE-2021-39275 · CVE-2021-40438 · CVE-2021-41524 · CVE-2021-41773 · CVE-2021-42013 · CVE-2021-43527 · CVE-2021-44224 · CVE-2021-44225 · CVE-2021-44790 · CVE-2021-44906 · CVE-2022-21245 · CVE-2022-21270 · CVE-2022-21303 · CVE-2022-21304 · CVE-2022-21344 · CVE-2022-21367 · CVE-2022-21417 · CVE-2022-21427 · CVE-2022-21444 · CVE-2022-21451 · CVE-2022-21454 · CVE-2022-21460 · CVE-2022-21589 · CVE-2022-21592 · CVE-2022-21595 · CVE-2022-21608 · CVE-2022-21617 · CVE-2022-22719 · CVE-2022-22720 · CVE-2022-22721 · CVE-2022-22822 · CVE-2022-22823 · CVE-2022-22824 · CVE-2022-23471 · CVE-2022-23524 · CVE-2022-23525 · CVE-2022-23526 · CVE-2022-23852 · CVE-2022-23943 · CVE-2022-25147 · CVE-2022-25235 · CVE-2022-25236 · CVE-2022-2526 · CVE-2022-25315 · CVE-2022-26377 · CVE-2022-28330 · CVE-2022-28614 · CVE-2022-28615 · CVE-2022-29167 · CVE-2022-29404 · CVE-2022-30522 · CVE-2022-30556 · CVE-2022-31813 · CVE-2022-3517 · CVE-2022-3564 · CVE-2022-36760 · CVE-2022-37434 · CVE-2022-37436 · CVE-2022-40674 · CVE-2022-41741 · CVE-2022-41742 · CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2022-46663 · CVE-2022-4886 · CVE-2023-0215 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0286 · CVE-2023-0401 · CVE-2023-0464 · CVE-2023-0465 · CVE-2023-0466 · CVE-2023-0767 · CVE-2023-1255 · CVE-2023-2002 · CVE-2023-20593 · CVE-2023-21830 · CVE-2023-21840 · CVE-2023-21843 · CVE-2023-21912 · CVE-2023-21963 · CVE-2023-21980 · CVE-2023-22025 · CVE-2023-22067 · CVE-2023-22081 · CVE-2023-22652 · CVE-2023-24329 · CVE-2023-25153 · CVE-2023-25173 · CVE-2023-25690 · CVE-2023-2700 · CVE-2023-27522 · CVE-2023-2828 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2023-2975 · CVE-2023-30079 · CVE-2023-30630 · CVE-2023-3090 · CVE-2023-32067 · CVE-2023-32360 · CVE-2023-32435 · CVE-2023-32439 · CVE-2023-32732 · CVE-2023-3341 · CVE-2023-3390 · CVE-2023-33953 · CVE-2023-34058 · CVE-2023-34059 · CVE-2023-3446 · CVE-2023-34969 · CVE-2023-35001 · CVE-2023-35788 · CVE-2023-3611 · CVE-2023-37450 · CVE-2023-3776 · CVE-2023-3817 · CVE-2023-4004 · CVE-2023-4206 · CVE-2023-4207 · CVE-2023-4208 · CVE-2023-42753 · CVE-2023-4785 · CVE-2023-4807 · CVE-2023-4863 · CVE-2023-5043 · CVE-2023-5129 · CVE-2023-5363 · CVE-2024-20918 · CVE-2024-20919 · CVE-2024-20921 · CVE-2024-20926 · CVE-2024-20932 · CVE-2024-20945 · CVE-2024-20952 · CVE-2024-39511 · CVE-2024-39512 · CVE-2024-39513 · CVE-2024-39514 · CVE-2024-39517 · CVE-2024-39518 · CVE-2024-39519 · CVE-2024-39520 · CVE-2024-39521 · CVE-2024-39522 · CVE-2024-39523 · CVE-2024-39524 · CVE-2024-39528 · CVE-2024-39529 · CVE-2024-39530 · CVE-2024-39531 · CVE-2024-39532 · CVE-2024-39533 · CVE-2024-39535 · CVE-2024-39536 · CVE-2024-39537 · CVE-2024-39538 · CVE-2024-39539 · CVE-2024-39540 · CVE-2024-39541 · CVE-2024-39542 · CVE-2024-39543 · CVE-2024-39545 · CVE-2024-39546 · CVE-2024-39548 · CVE-2024-39549 · CVE-2024-39550 · CVE-2024-39551 · CVE-2024-39553 · CVE-2024-39554 · CVE-2024-39555 · CVE-2024-39556 · CVE-2024-39557 · CVE-2024-39558 · CVE-2024-39559 · CVE-2024-39560 · CVE-2024-39561 · CVE-2024-39565
ICSA-23-229-01: ICONICS and Mitsubishi Electric Products
CVE-2022-3602 · CVE-2022-3786 · CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2023-0401
WID-SEC-W-2023-1424: Xerox FreeFlow Print Server für Solaris: Mehrere Schwachstellen
CVE-2006-20001 · CVE-2017-12613 · CVE-2018-25032 · CVE-2021-29338 · CVE-2021-30860 · CVE-2021-35940 · CVE-2021-37519 · CVE-2021-37750 · CVE-2022-0718 · CVE-2022-1122 · CVE-2022-1292 · CVE-2022-1705 · CVE-2022-1962 · CVE-2022-21291 · CVE-2022-21349 · CVE-2022-21515 · CVE-2022-2309 · CVE-2022-23521 · CVE-2022-24675 · CVE-2022-24963 · CVE-2022-25147 · CVE-2022-25255 · CVE-2022-27337 · CVE-2022-27536 · CVE-2022-27664 · CVE-2022-27778 · CVE-2022-28131 · CVE-2022-2816 · CVE-2022-2817 · CVE-2022-2819 · CVE-2022-28327 · CVE-2022-28331 · CVE-2022-2845 · CVE-2022-2849 · CVE-2022-2862 · CVE-2022-2874 · CVE-2022-2879 · CVE-2022-2880 · CVE-2022-2889 · CVE-2022-2923 · CVE-2022-2928 · CVE-2022-2929 · CVE-2022-2946 · CVE-2022-29526 · CVE-2022-2980 · CVE-2022-29804 · CVE-2022-3016 · CVE-2022-3037 · CVE-2022-30580 · CVE-2022-30629 · CVE-2022-30630 · CVE-2022-30631 · CVE-2022-30632 · CVE-2022-30633 · CVE-2022-30634 · CVE-2022-30635 · CVE-2022-3094 · CVE-2022-3099 · CVE-2022-3134 · CVE-2022-3153 · CVE-2022-32148 · CVE-2022-32189 · CVE-2022-32190 · CVE-2022-32205 · CVE-2022-32206 · CVE-2022-32207 · CVE-2022-32208 · CVE-2022-32221 · CVE-2022-3234 · CVE-2022-3235 · CVE-2022-3256 · CVE-2022-3278 · CVE-2022-3296 · CVE-2022-3297 · CVE-2022-3324 · CVE-2022-3352 · CVE-2022-3515 · CVE-2022-35252 · CVE-2022-35260 · CVE-2022-36113 · CVE-2022-36114 · CVE-2022-36227 · CVE-2022-36760 · CVE-2022-3705 · CVE-2022-3736 · CVE-2022-37436 · CVE-2022-38171 · CVE-2022-38784 · CVE-2022-3924 · CVE-2022-39253 · CVE-2022-40303 · CVE-2022-40304 · CVE-2022-40898 · CVE-2022-41715 · CVE-2022-41716 · CVE-2022-41903 · CVE-2022-42010 · CVE-2022-42011 · CVE-2022-42012 · CVE-2022-4203 · CVE-2022-4283 · CVE-2022-42898 · CVE-2022-42915 · CVE-2022-42916 · CVE-2022-42919 · CVE-2022-4304 · CVE-2022-4345 · CVE-2022-4450 · CVE-2022-45143 · CVE-2022-45199 · CVE-2022-45939 · CVE-2022-46340 · CVE-2022-46341 · CVE-2022-46342 · CVE-2022-46343 · CVE-2022-46344 · CVE-2022-46871 · CVE-2022-46874 · CVE-2022-46877 · CVE-2022-48281 · CVE-2023-0215 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0286 · CVE-2023-0401 · CVE-2023-0411 · CVE-2023-0412 · CVE-2023-0413 · CVE-2023-0414 · CVE-2023-0415 · CVE-2023-0416 · CVE-2023-0417 · CVE-2023-0430 · CVE-2023-0567 · CVE-2023-0568 · CVE-2023-0616 · CVE-2023-0662 · CVE-2023-0767 · CVE-2023-0795 · CVE-2023-0796 · CVE-2023-0797 · CVE-2023-0798 · CVE-2023-0799 · CVE-2023-0800 · CVE-2023-0801 · CVE-2023-0802 · CVE-2023-0803 · CVE-2023-0804 · CVE-2023-21830 · CVE-2023-21840 · CVE-2023-21843 · CVE-2023-21896 · CVE-2023-21928 · CVE-2023-21984 · CVE-2023-21985 · CVE-2023-22003 · CVE-2023-22490 · CVE-2023-22809 · CVE-2023-23598 · CVE-2023-23599 · CVE-2023-23601 · CVE-2023-23602 · CVE-2023-23603 · CVE-2023-23605 · CVE-2023-23918 · CVE-2023-23919 · CVE-2023-23920 · CVE-2023-23936 · CVE-2023-23946 · CVE-2023-23969 · CVE-2023-24580 · CVE-2023-24807 · CVE-2023-24998 · CVE-2023-25690 · CVE-2023-25728 · CVE-2023-25729 · CVE-2023-25730 · CVE-2023-25732 · CVE-2023-25734 · CVE-2023-25735 · CVE-2023-25737 · CVE-2023-25738 · CVE-2023-25739 · CVE-2023-25742 · CVE-2023-25743 · CVE-2023-25744 · CVE-2023-25746 · CVE-2023-25751 · CVE-2023-25752 · CVE-2023-27522 · CVE-2023-28162 · CVE-2023-28163 · CVE-2023-28164 · CVE-2023-28176 · CVE-2023-28708
RHSA-2023:0946: Red Hat Security Advisory: openssl security and bug fix update
CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2023-0215 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0286 · CVE-2023-0401
SSA-699386: SSA-699386: Multiple Vulnerabilities in SCALANCE XB-200 / XC-200 / XP-200 / XF-200BA / XR-300WG Family before V4.5
CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0401 · CVE-2023-2650 · CVE-2023-44317 · CVE-2023-44319 · CVE-2023-44320 · CVE-2023-44322 · CVE-2023-44373 · CVE-2023-44374
ICSA-24-046-15: Siemens SINEC NMS
CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2023-0215 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0286 · CVE-2023-0401 · CVE-2023-1255 · CVE-2023-2454 · CVE-2023-2455 · CVE-2023-2650 · CVE-2023-2975 · CVE-2023-3446 · CVE-2023-3817 · CVE-2023-25690 · CVE-2023-27522 · CVE-2023-27533 · CVE-2023-27534 · CVE-2023-27535 · CVE-2023-27536 · CVE-2023-27537 · CVE-2023-27538 · CVE-2023-28319 · CVE-2023-28320 · CVE-2023-28321 · CVE-2023-28322 · CVE-2023-28709 · CVE-2023-30581 · CVE-2023-30582 · CVE-2023-30583 · CVE-2023-30584 · CVE-2023-30585 · CVE-2023-30586 · CVE-2023-30587 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-31124 · CVE-2023-31130 · CVE-2023-31147 · CVE-2023-32002 · CVE-2023-32003 · CVE-2023-32004 · CVE-2023-32005 · CVE-2023-32006 · CVE-2023-32067 · CVE-2023-32558 · CVE-2023-32559 · CVE-2023-34035 · CVE-2023-35945 · CVE-2023-38039 · CVE-2023-38199 · CVE-2023-38545 · CVE-2023-38546 · CVE-2023-39417 · CVE-2023-39418 · CVE-2023-41080 · CVE-2023-46120 · CVE-2024-23810 · CVE-2024-23811 · CVE-2024-23812
ICSA-23-320-08: Siemens SCALANCE Family Products
CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0401 · CVE-2023-2650 · CVE-2023-44317 · CVE-2023-44319 · CVE-2023-44320 · CVE-2023-44322 · CVE-2023-44373 · CVE-2023-44374
SUSE-SU-2023:0312-1: Security update for openssl-3
CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2023-0215 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0286 · CVE-2023-0401
RHSA-2023:1199: Red Hat Security Advisory: openssl security and bug fix update
CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2023-0215 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0286 · CVE-2023-0401
WID-SEC-W-2023-0304: OpenSSL: Mehrere Schwachstellen
CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2023-0215 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0286 · CVE-2023-0401
SSA-943925: SSA-943925: Multiple Vulnerabilities in SINEC NMS before V2.0 SP1
CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2023-0215 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0286 · CVE-2023-0401 · CVE-2023-1255 · CVE-2023-2454 · CVE-2023-2455 · CVE-2023-2650 · CVE-2023-2975 · CVE-2023-3446 · CVE-2023-3817 · CVE-2023-25690 · CVE-2023-27522 · CVE-2023-27533 · CVE-2023-27534 · CVE-2023-27535 · CVE-2023-27536 · CVE-2023-27537 · CVE-2023-27538 · CVE-2023-28319 · CVE-2023-28320 · CVE-2023-28321 · CVE-2023-28322 · CVE-2023-28709 · CVE-2023-30581 · CVE-2023-30582 · CVE-2023-30583 · CVE-2023-30584 · CVE-2023-30585 · CVE-2023-30586 · CVE-2023-30587 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-31124 · CVE-2023-31130 · CVE-2023-31147 · CVE-2023-32002 · CVE-2023-32003 · CVE-2023-32004 · CVE-2023-32005 · CVE-2023-32006 · CVE-2023-32067 · CVE-2023-32558 · CVE-2023-32559 · CVE-2023-34035 · CVE-2023-35945 · CVE-2023-38039 · CVE-2023-38199 · CVE-2023-38545 · CVE-2023-38546 · CVE-2023-39417 · CVE-2023-39418 · CVE-2023-41080 · CVE-2023-46120 · CVE-2024-23810 · CVE-2024-23811 · CVE-2024-23812
openSUSE-SU-2024:12716-1: libopenssl-3-devel-3.0.8-1.1 on GA media
CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2023-0215 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0286 · CVE-2023-0401
- Source published
- Feb 24, 2023, 2:53:08 PM (timezone not stated)
- Source modified
- Nov 4, 2025, 7:14:06 PM (timezone not stated)
- Saved here
- 18 Nov 2026 08:31:41 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
nvd · CVE-2022-4203
PublishedA read buffer overrun can be triggered in X.509 certificate verification,
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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-125
Original publisher date fields
published: 2023-02-24T15:15:11.980
lastModified: 2026-06-17T05:20:14.500
1 source CPE criteria · context only
- cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 24 Feb 2023 15:15:11 UTC
- Source modified
- 17 Jun 2026 05:20:14 UTC
- Saved here
- 24 Oct 2026 21:17:16 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Primary · 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary · 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
osv · GHSA-w67w-mw4j-8qrv
Publishedopenssl-src contains Read Buffer Overflow in X.509 Name Constraint
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.
- Source published
- 8 Feb 2023 22:27:42 UTC
- Source modified
- 10 Sep 2026 03:49:52 UTC
- Saved here
- 24 Oct 2026 13:19:54 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Publisher rating · CRITICAL
osv · RUSTSEC-2023-0008
PublishedX.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.
- Source published
- 7 Feb 2023 12:00:00 UTC
- Source modified
- 8 Nov 2023 04:10:37 UTC
- Saved here
- 24 Oct 2026 13:19:54 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.