<?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:10:14.912624+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/bell-cve-2019-1547</id>
    <title>Withdrawn: BELL-CVE-2019-1547 — CVE-2019-1547 does not affect BellSoft software</title>
    <updated>2026-11-21T00:10:14.919991+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-2019-1547"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2019-avi-444</id>
    <title>certfr-2019-avi-444 — De multiples vulnérabilités ont été découvertes dans OpenSSL. Elles
permettent à un attaquant de provoquer une atteinte…</title>
    <updated>2026-11-21T00:10:14.920053+00:00</updated>
    <content>certfr-2019-avi-444</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2019-avi-444"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/cleanstart-2024-yu07393</id>
    <title>CLEANSTART-2024-YU07393 — Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths</title>
    <updated>2026-11-21T00:10:14.920106+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. Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/cleanstart-2024-yu07393"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2019-1547</id>
    <title>UBUNTU-CVE-2019-1547</title>
    <updated>2026-11-21T00:10:14.920146+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:16.04:LTS: openssl, Ubuntu:18.04:LTS: openssl, Ubuntu:18.04:LTS: openssl1.0</p>
<p>Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2019-1547"/>
  </entry>
</feed>
