<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T07:51:37.538941+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/alsa-2023:6615</id>
    <title>ALSA-2023:6615 — Moderate: python-cryptography security update</title>
    <updated>2026-10-03T07:51:38.410103+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:9: python3-cryptography</p>
<p>The python-cryptography packages contain a Python Cryptographic Authority's (PyCA's) cryptography library, which provides cryptographic primitives and recipes to Python developers.</p>
<p>Security Fix(es):</p>
<p>* python-cryptography: memory corruption via immutable objects (CVE-2023-23931)</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>Additional Changes:</p>
<p>For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/alsa-2023:6615"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2023-02656</id>
    <title>bdu:2023-02656</title>
    <updated>2026-10-03T07:51:38.410170+00:00</updated>
    <content>bdu:2023-02656</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2023-02656"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2023-23931</id>
    <title>Withdrawn: BELL-CVE-2023-23931 — CVE-2023-23931 does not affect BellSoft software</title>
    <updated>2026-10-03T07:51:38.410188+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://cve.radiocsirt.org/vuln/bell-cve-2023-23931"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/brew-azure-cli-cve-2023-23931</id>
    <title>BREW-azure-cli-CVE-2023-23931 — Cipher.update_into can corrupt memory if passed an immutable python object as the outbuf</title>
    <updated>2026-10-03T07:51:38.410204+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: azure-cli</p>
<p>Previously, `Cipher.update_into` would accept Python objects which implement the buffer protocol, but provide only immutable buffers:</p>
<p>```pycon
&gt;&gt;&gt; outbuf = b"\x00" * 32
&gt;&gt;&gt; c = ciphers.Cipher(AES(b"\x00" * 32), modes.ECB()).encryptor()
&gt;&gt;&gt; c.update_into(b"\x00" * 16, outbuf)
16
&gt;&gt;&gt; outbuf
b'\xdc\x95\xc0x\xa2@\x89\x89\xadH\xa2\x14\x92\x84 \x87\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'
```</p>
<p>This would allow immutable objects (such as `bytes`) to be mutated, thus violating fundamental rules of Python. This is a soundness bug -- it allows programmers to misuse an API, it cannot be exploited by attacker controlled data alone.</p>
<p>This now correctly raises an exception.</p>
<p>This issue has been present since `update_into` was originally introduced in cryptography 1.8.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-azure-cli-cve-2023-23931"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2023-avi-0238</id>
    <title>certfr-2023-avi-0238 — De multiples vulnérabilités ont été découvertes dans les produits &lt;span
class="textit"&gt;IBM&lt;/span&gt;. Elles permettent à u…</title>
    <updated>2026-10-03T07:51:38.410233+00:00</updated>
    <content>certfr-2023-avi-0238</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2023-avi-0238"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-258384</id>
    <title>EUVD-2026-258384</title>
    <updated>2026-10-03T07:51:38.410250+00:00</updated>
    <content>EUVD-2026-258384</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-258384"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-23931</id>
    <title>fkie_cve-2023-23931</title>
    <updated>2026-10-03T07:51:38.410261+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In affected versions `Cipher.update_into` would accept Python objects which implement the buffer protocol, but provide only immutable buffers. This would allow immutable objects (such as `bytes`) to be mutated, thus violating fundamental rules of Python and resulting in corrupted output. This now correctly raises an exception. This issue has been present since `update_into` was originally introduced in cryptography 1.8.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-23931"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-w7pp-m8wf-vj6r</id>
    <title>GHSA-w7pp-m8wf-vj6r — Cipher.update_into can corrupt memory if passed an immutable python object as the outbuf</title>
    <updated>2026-10-03T07:51:38.410284+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: cryptography</p>
<p>Previously, `Cipher.update_into` would accept Python objects which implement the buffer protocol, but provide only immutable buffers:</p>
<p>```pycon
&gt;&gt;&gt; outbuf = b"\x00" * 32
&gt;&gt;&gt; c = ciphers.Cipher(AES(b"\x00" * 32), modes.ECB()).encryptor()
&gt;&gt;&gt; c.update_into(b"\x00" * 16, outbuf)
16
&gt;&gt;&gt; outbuf
b'\xdc\x95\xc0x\xa2@\x89\x89\xadH\xa2\x14\x92\x84 \x87\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'
```</p>
<p>This would allow immutable objects (such as `bytes`) to be mutated, thus violating fundamental rules of Python. This is a soundness bug -- it allows programmers to misuse an API, it cannot be exploited by attacker controlled data alone.</p>
<p>This now correctly raises an exception.</p>
<p>This issue has been present since `update_into` was originally introduced in cryptography 1.8.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-w7pp-m8wf-vj6r"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2023-23931</id>
    <title>gsd-2023-23931</title>
    <updated>2026-10-03T07:51:38.410311+00:00</updated>
    <content>gsd-2023-23931</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2023-23931"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/icsa-24-046-11</id>
    <title>ICSA-24-046-11 — Siemens SCALANCE XCM-/XRM-300</title>
    <updated>2026-10-03T07:51:38.410323+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>A carefully crafted If: request header can cause a memory read, or write of a single zero byte, in a pool (heap) memory location beyond the header value sent. This could cause the process to crash.</p>
<p>This issue affects Apache HTTP Server 2.4.54 and earlier. A flaw was found in python. In algorithms with quadratic time complexity using non-binary bases, when using int("text"), a system could take 50ms to parse an int string with 100,000 digits and 5s for 1,000,000 digits (float, decimal, int.from_bytes(), and int() for binary bases 2, 4, 8, 16, and 32 are not affected). The highest threat from this vulnerability is to system availability. A flaw was found in libdnf's signature verification functionality in versions before 0.60.1. This flaw allows an attacker to achieve code execution if they can alter the header information of an RPM package and then trick a user or system into installing it. The highest risk of this vulnerability is to confidentiality, integrity, as well as system availability. An out-of-bounds memory access flaw was found in the ATI VGA device emulation of QEMU. This flaw occurs in the ati_2d_blt() routine while handling MMIO write operations when the guest provides invalid values for the destination display parameters. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service. A vulnerability was found in the fs/inode.c:inode_init_owner() function logic of the LInux kernel that allows local users to create…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/icsa-24-046-11"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2023-23931</id>
    <title>msrc_CVE-2023-23931 — Cipher.update_into can corrupt memory in pyca cryptography</title>
    <updated>2026-10-03T07:51:38.410810+00:00</updated>
    <content>msrc_CVE-2023-23931</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2023-23931"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2023-1085</id>
    <title>OESA-2023-1085 — python-cryptography security update</title>
    <updated>2026-10-03T07:51:38.410828+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: python-cryptography</p>
<p>cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.

Security Fix(es):

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In affected versions `Cipher.update_into` would accept Python objects which implement the buffer protocol, but provide only immutable buffers. This would allow immutable objects (such as `bytes`) to be mutated, thus violating fundamental rules of Python and resulting in corrupted output. This now correctly raises an exception. This issue has been present since `update_into` was originally introduced in cryptography 1.8.(CVE-2023-23931)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2023-1085"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2024:12681-1</id>
    <title>openSUSE-SU-2024:12681-1 — python310-cryptography-39.0.1-1.1 on GA media</title>
    <updated>2026-10-03T07:51:38.410852+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>python310-cryptography-39.0.1-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2024:12681-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2023-11</id>
    <title>PYSEC-2023-11</title>
    <updated>2026-10-03T07:51:38.410868+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: cryptography</p>
<p>cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In affected versions `Cipher.update_into` would accept Python objects which implement the buffer protocol, but provide only immutable buffers. This would allow immutable objects (such as `bytes`) to be mutated, thus violating fundamental rules of Python and resulting in corrupted output. This now correctly raises an exception. This issue has been present since `update_into` was originally introduced in cryptography 1.8.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2023-11"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2023:4693</id>
    <title>RHSA-2023:4693 — Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.4 Product Security and Bug Fix Update</title>
    <updated>2026-10-03T07:51:38.410888+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>platform: token exposed at importing project python-cryptography: memory corruption via immutable objects python-requests: Unintended leak of Proxy-Authorization header python-django: Potential regular expression denial of service vulnerability in EmailValidator/URLValidator</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2023:4693"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2023:0722-2</id>
    <title>SUSE-SU-2023:0722-2 — Security update for python-cryptography</title>
    <updated>2026-10-03T07:51:38.410908+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for python-cryptography</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2023:0722-2"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-23931</id>
    <title>UBUNTU-CVE-2023-23931</title>
    <updated>2026-10-03T07:51:38.410923+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:18.04:LTS: python-cryptography, Ubuntu:20.04:LTS: python-cryptography, Ubuntu:22.04:LTS: python-cryptography</p>
<p>cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In affected versions `Cipher.update_into` would accept Python objects which implement the buffer protocol, but provide only immutable buffers. This would allow immutable objects (such as `bytes`) to be mutated, thus violating fundamental rules of Python and resulting in corrupted output. This now correctly raises an exception. This issue has been present since `update_into` was originally introduced in cryptography 1.8.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-23931"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1021</id>
    <title>WID-SEC-W-2023-1021 — Oracle Communications: Mehrere Schwachstellen</title>
    <updated>2026-10-03T07:51:38.410946+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1021"/>
  </entry>
</feed>
