https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 07:57:07 +0000 https://cve.radiocsirt.org/vuln/bdu:2023-01662 bdu:2023-01662 https://cve.radiocsirt.org/vuln/bdu:2023-01662 https://cve.radiocsirt.org/vuln/bell-cve-2020-14382 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2020-14382 https://cve.radiocsirt.org/vuln/euvd-2026-42431 EUVD-2026-42431 https://cve.radiocsirt.org/vuln/euvd-2026-42431 https://cve.radiocsirt.org/vuln/fkie_cve-2020-14382 <p>A vulnerability was found in upstream release cryptsetup-2.2.0 where, there&#39;s a bug in LUKS2 format validation code, that is effectively invoked on every device/image presenting itself as LUKS2 container. The bug is in segments validation code in file &#39;lib/luks2/luks2_json_metadata.c&#39; in function hdr_validate_segments(struct crypt_device *cd, json_object *hdr_jobj) where the code does not check for possible overflow on memory allocation used for intervals array (see statement &#34;intervals = malloc(first_backup * sizeof(*intervals));&#34;). Due to the bug, library can be *tricked* to expect such allocation was successful but for far less memory then originally expected. Later it may read data FROM image crafted by an attacker and actually write such data BEYOND allocated memory.</p> <p>A vulnerability was found in upstream release cryptsetup-2.2.0 where, there&#39;s a bug in LUKS2 format validation code, that is effectively invoked on every device/image presenting itself as LUKS2 container. The bug is in segments validation code in file &#39;lib/luks2/luks2_json_metadata.c&#39; in function hdr_validate_segments(struct crypt_device *cd, json_object *hdr_jobj) where the code does not check for possible overflow on memory allocation used for intervals array (see statement &#34;intervals = malloc(first_backup * sizeof(*intervals));&#34;). Due to the bug, library can be *tricked* to expect such allocation was successful but for far less memory then originally expected. Later it may read data FROM image crafted by an attacker and actually write such data BEYOND allocated memory.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-14382 https://cve.radiocsirt.org/vuln/ghsa-v8mw-xqhr-2vqp <p>A vulnerability was found in upstream release cryptsetup-2.2.0 where, there&#39;s a bug in LUKS2 format validation code, that is effectively invoked on every device/image presenting itself as LUKS2 container. The bug is in segments validation code in file &#39;lib/luks2/luks2_json_metadata.c&#39; in function hdr_validate_segments(struct crypt_device *cd, json_object *hdr_jobj) where the code does not check for possible overflow on memory allocation used for intervals array (see statement &#34;intervals = malloc(first_backup * sizeof(*intervals));&#34;). Due to the bug, library can be *tricked* to expect such allocation was successful but for far less memory then originally expected. Later it may read data FROM image crafted by an attacker and actually write such data BEYOND allocated memory.</p> <p>A vulnerability was found in upstream release cryptsetup-2.2.0 where, there&#39;s a bug in LUKS2 format validation code, that is effectively invoked on every device/image presenting itself as LUKS2 container. The bug is in segments validation code in file &#39;lib/luks2/luks2_json_metadata.c&#39; in function hdr_validate_segments(struct crypt_device *cd, json_object *hdr_jobj) where the code does not check for possible overflow on memory allocation used for intervals array (see statement &#34;intervals = malloc(first_backup * sizeof(*intervals));&#34;). Due to the bug, library can be *tricked* to expect such allocation was successful but for far less memory then originally expected. Later it may read data FROM image crafted by an attacker and actually write such data BEYOND allocated memory.</p> https://cve.radiocsirt.org/vuln/ghsa-v8mw-xqhr-2vqp https://cve.radiocsirt.org/vuln/gsd-2020-14382 gsd-2020-14382 https://cve.radiocsirt.org/vuln/gsd-2020-14382 https://cve.radiocsirt.org/vuln/opensuse-su-2024:10704-1 <p>cryptsetup-2.4.1-1.1 on GA media</p> <p>cryptsetup-2.4.1-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:10704-1 https://cve.radiocsirt.org/vuln/rhsa-2020:4900 <p>cryptsetup: Out-of-bounds write when validating segments</p> <p>cryptsetup: Out-of-bounds write when validating segments</p> https://cve.radiocsirt.org/vuln/rhsa-2020:4900 https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-14382 <p><strong>Affected:</strong> Ubuntu:20.04:LTS: cryptsetup</p> <p>A vulnerability was found in upstream release cryptsetup-2.2.0 where, there&#39;s a bug in LUKS2 format validation code, that is effectively invoked on every device/image presenting itself as LUKS2 container. The bug is in segments validation code in file &#39;lib/luks2/luks2_json_metadata.c&#39; in function hdr_validate_segments(struct crypt_device *cd, json_object *hdr_jobj) where the code does not check for possible overflow on memory allocation used for intervals array (see statement &#34;intervals = malloc(first_backup * sizeof(*intervals));&#34;). Due to the bug, library can be *tricked* to expect such allocation was successful but for far less memory then originally expected. Later it may read data FROM image crafted by an attacker and actually write such data BEYOND allocated memory.</p> <p><strong>Affected:</strong> Ubuntu:20.04:LTS: cryptsetup</p> <p>A vulnerability was found in upstream release cryptsetup-2.2.0 where, there&#39;s a bug in LUKS2 format validation code, that is effectively invoked on every device/image presenting itself as LUKS2 container. The bug is in segments validation code in file &#39;lib/luks2/luks2_json_metadata.c&#39; in function hdr_validate_segments(struct crypt_device *cd, json_object *hdr_jobj) where the code does not check for possible overflow on memory allocation used for intervals array (see statement &#34;intervals = malloc(first_backup * sizeof(*intervals));&#34;). Due to the bug, library can be *tricked* to expect such allocation was successful but for far less memory then originally expected. Later it may read data FROM image crafted by an attacker and actually write such data BEYOND allocated memory.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-14382 https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0193 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux ausnutzen, um die Verfügbarkeit, Integrität und Vertraulichkeit zu gefährden.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux ausnutzen, um die Verfügbarkeit, Integrität und Vertraulichkeit zu gefährden.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0193