<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T00:35:51.667953+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/alsa-2023:0946</id>
    <title>ALSA-2023:0946 — Moderate: openssl security and bug fix update</title>
    <updated>2026-11-21T00:35:51.692103+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:9: openssl, AlmaLinux:9: openssl-devel, AlmaLinux:9: openssl-libs, AlmaLinux:9: openssl-perl</p>
<p>OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.</p>
<p>Security Fix(es):</p>
<p>* openssl: read buffer overflow in X.509 certificate verification (CVE-2022-4203)
* openssl: timing attack in RSA Decryption implementation (CVE-2022-4304)
* openssl: double free after calling PEM_read_bio_ex (CVE-2022-4450)
* openssl: use-after-free following BIO_new_NDEF (CVE-2023-0215)
* openssl: invalid pointer dereference in d2i_PKCS7 functions (CVE-2023-0216)
* openssl: NULL dereference validating DSA public key (CVE-2023-0217)
* openssl: X.400 address type confusion in X.509 GeneralName (CVE-2023-0286)
* openssl: NULL dereference during PKCS7 data verification (CVE-2023-0401)</p>
<p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p>
<p>Bug Fix(es):</p>
<p>* HMAC generation should reject key lengths &lt; 112 bits or provide an indicator in FIPS mode (BZ#2144000)
* In FIPS mode, openssl should set a minimum length for passwords in PBKDF2 (BZ#2144003)
* stunnel consumes high amount of memory when pestered with TCP connections without a TLS handshake (BZ#2144008)
* In FIPS mode, openssl should reject SHAKE as digest for RSA-OAEP or provide an indicator (BZ#2144010)
* In FIPS mode, openssl should reject RSASSA-PSS salt lengths larger than the output size of t…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2023:0946"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2023-0286</id>
    <title>Withdrawn: BELL-CVE-2023-0286 — CVE-2023-0286 does not affect BellSoft software</title>
    <updated>2026-11-21T00:35:51.692204+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
          <strong>Withdrawn by the publisher.</strong>
        </p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2023-0286"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2023-avi-0102</id>
    <title>certfr-2023-avi-0102 — De multiples vulnérabilités ont été découvertes dans OpenSSL. Elles
permettent à un attaquant de provoquer un déni de s…</title>
    <updated>2026-11-21T00:35:51.692220+00:00</updated>
    <content>certfr-2023-avi-0102</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2023-avi-0102"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/cleanstart-2024-fc42191</id>
    <title>CLEANSTART-2024-FC42191 — There is a type confusion vulnerability relating to X</title>
    <updated>2026-11-21T00:35:51.692231+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: openssl1.1-compat</p>
<p>Security vulnerability affects the openssl1.1-compat package. There is a type confusion vulnerability relating to X.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/cleanstart-2024-fc42191"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2023-1092</id>
    <title>OESA-2023-1092 — openssl security update</title>
    <updated>2026-11-21T00:35:51.692245+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: openssl, openEuler:20.03-LTS-SP3: openssl, openEuler:22.03-LTS: openssl</p>
<p>OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.

Security Fix(es):

The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacte…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2023-1092"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rustsec-2023-0006</id>
    <title>RUSTSEC-2023-0006 — X.400 address type confusion in X.509 `GeneralName`</title>
    <updated>2026-11-21T00:35:51.692282+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: openssl-src</p>
<p>There is a type confusion vulnerability relating to X.400 address processing
inside an X.509 `GeneralName`. X.400 addresses were parsed as an `ASN1_STRING` but
the public structure definition for `GENERAL_NAME` incorrectly specified the type
of the `x400Address` field as `ASN1_TYPE`. This field is subsequently interpreted by
the OpenSSL function `GENERAL_NAME_cmp` as an `ASN1_TYPE` rather than an
`ASN1_STRING`.</p>
<p>When CRL checking is enabled (i.e. the application sets the
`X509_V_FLAG_CRL_CHECK` flag), this vulnerability may allow an attacker to pass
arbitrary pointers to a `memcmp` call, enabling them to read memory contents or
enact a denial of service. In most cases, the attack requires the attacker to
provide both the certificate chain and CRL, neither of which need to have a
valid signature. If the attacker only controls one of these inputs, the other
input must already contain an X.400 address as a CRL distribution point, which
is uncommon. As such, this vulnerability is most likely to only affect
applications which have implemented their own functionality for retrieving CRLs
over a network.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rustsec-2023-0006"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2023-0286</id>
    <title>UBUNTU-CVE-2023-0286</title>
    <updated>2026-11-21T00:35:51.692306+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: openssl, Ubuntu:Pro:16.04:LTS: openssl, Ubuntu:Pro:16.04:LTS: edk2, Ubuntu:Pro:FIPS-updates:16.04:LTS: openssl, Ubuntu:Pro:FIPS:16.04:LTS: openssl, Ubuntu:18.04:LTS: openssl, Ubuntu:18.04:LTS: openssl1.0, Ubuntu:Pro:18.04:LTS: edk2, Ubuntu:Pro:FIPS-updates:18.04:LTS: openssl, Ubuntu:Pro:FIPS:18.04:LTS: openssl and 7 more</p>
<p>There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2023-0286"/>
  </entry>
</feed>
