Docker python:latest
Vulnerabilities |
211 via 782 paths |
---|---|
Dependencies |
429 |
Source |
Docker |
Target OS |
debian:12 |
critical severity
- Vulnerable module: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.2.13.dfsg-1 and zlib/zlib1g-dev@1:1.2.13.dfsg-1
Detailed paths
-
Introduced through: python@latest › zlib/zlib1g@1:1.2.13.dfsg-1
-
Introduced through: python@latest › zlib/zlib1g-dev@1:1.2.13.dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream zlib
package and not the zlib
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. NOTE: MiniZip is not a supported part of the zlib product. NOTE: pyminizip through 0.2.6 is also vulnerable because it bundles an affected zlib version, and exposes the applicable MiniZip code through its compress API.
Remediation
There is no fixed version for Debian:12
zlib
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-45853
- http://www.openwall.com/lists/oss-security/2023/10/20/9
- http://www.openwall.com/lists/oss-security/2024/01/24/10
- https://chromium.googlesource.com/chromium/src/+/d709fb23806858847131027da95ef4c548813356
- https://chromium.googlesource.com/chromium/src/+/de29dd6c7151d3cd37cb4cf0036800ddfb1d8b61
- https://github.com/madler/zlib/blob/ac8f12c97d1afd9bafa9c710f827d40a407d3266/contrib/README.contrib#L1-L4
- https://github.com/madler/zlib/pull/843
- https://lists.debian.org/debian-lts-announce/2023/11/msg00026.html
- https://pypi.org/project/pyminizip/#history
- https://security.gentoo.org/glsa/202401-18
- https://security.netapp.com/advisory/ntap-20231130-0009/
- https://www.winimage.com/zLibDll/minizip.html
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1 and libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: python@latest › libxml2@2.9.14+dfsg-1.3~deb12u1
-
Introduced through: python@latest › libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2
package and not the libxml2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a NULL pointer dereference in xmlPatMatch in pattern.c.
Remediation
There is no fixed version for Debian:12
libxml2
.
References
high severity
new
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1 and libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: python@latest › libxml2@2.9.14+dfsg-1.3~deb12u1
-
Introduced through: python@latest › libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2
package and not the libxml2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In libxml2 before 2.13.8 and 2.14.x before 2.14.2, xmlSchemaIDCFillNodeTables in xmlschemas.c has a heap-based buffer under-read. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used.
Remediation
There is no fixed version for Debian:12
libxml2
.
References
medium severity
new
- Vulnerable module: krb5/krb5-multidev
- Introduced through: krb5/krb5-multidev@1.20.1-2+deb12u2, krb5/libgssapi-krb5-2@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › krb5/krb5-multidev@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libgssrpc4@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkadm5clnt-mit12@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkadm5srv-mit12@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkdb5-10@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5-dev@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5support0@1.20.1-2+deb12u2
…and 7 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5
package and not the krb5
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability in the MIT Kerberos implementation allows GSSAPI-protected messages using RC4-HMAC-MD5 to be spoofed due to weaknesses in the MD5 checksum design. If RC4 is preferred over stronger encryption types, an attacker could exploit MD5 collisions to forge message integrity codes. This may lead to unauthorized message tampering.
Remediation
There is no fixed version for Debian:12
krb5
.
References
low severity
- Vulnerable module: aom/libaom3
- Introduced through: aom/libaom3@3.6.0-1+deb12u1
Detailed paths
-
Introduced through: python@latest › aom/libaom3@3.6.0-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream aom
package and not the aom
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Increasing the resolution of video frames, while performing a multi-threaded encode, can result in a heap overflow in av1_loop_restoration_dealloc().
Remediation
There is no fixed version for Debian:12
aom
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-6879
- https://aomedia.googlesource.com/aom/+/refs/tags/v3.7.1
- https://crbug.com/aomedia/3491
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AYONA2XSNFMXLAW4IHLFI5UVV3QRNG5K/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/D6C2HN4T2S6GYNTAUXLH45LQZHK7QPHP/
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u10, glibc/libc-dev-bin@2.36-9+deb12u10 and others
Detailed paths
-
Introduced through: python@latest › glibc/libc-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc-dev-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6-dev@2.36-9+deb12u10
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc
package and not the glibc
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass stack guard protection. The component is: nptl. The attack vector is: Exploit stack buffer overflow vulnerability and use this bypass vulnerability to bypass stack guard. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
Remediation
There is no fixed version for Debian:12
glibc
.
References
low severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6+deb12u2
…and 10 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick
package and not the imagemagick
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability was found in ImageMagick. This security flaw cause a remote code execution vulnerability in OpenBlob with --enable-pipes configured.
Remediation
There is no fixed version for Debian:12
imagemagick
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-34152
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/
- https://access.redhat.com/security/cve/CVE-2023-34152
- https://bugzilla.redhat.com/show_bug.cgi?id=2210659
- https://github.com/ImageMagick/ImageMagick/issues/6339
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In OpenJPEG 2.3.0, a stack-based buffer overflow was discovered in the pgxtoimage function in jpwl/convert.c. The vulnerability causes an out-of-bounds write, which may lead to remote denial of service or possibly remote code execution.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1.2+deb12u1
Detailed paths
-
Introduced through: python@latest › tar@1.34+dfsg-1.2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream tar
package and not the tar
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.
Remediation
There is no fixed version for Debian:12
tar
.
References
- https://security-tracker.debian.org/tracker/CVE-2005-2541
- http://marc.info/?l=bugtraq&m=112327628230258&w=2
- https://lists.apache.org/thread.html/rc713534b10f9daeee2e0990239fa407e2118e4aa9e88a7041177497c@%3Cissues.guacamole.apache.org%3E
- https://lists.apache.org/thread.html/rc713534b10f9daeee2e0990239fa407e2118e4aa9e88a7041177497c%40%3Cissues.guacamole.apache.org%3E
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6+deb12u2, tiff/libtiff6@4.5.0-6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › tiff/libtiff-dev@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiff6@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiffxx6@4.5.0-6+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff
package and not the tiff
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In LibTIFF 4.0.6 and possibly other versions, the program processes BMP images without verifying that biWidth and biHeight in the bitmap-information header match the actual input, as demonstrated by a heap-based buffer over-read in bmp2tiff. NOTE: mentioning bmp2tiff does not imply that the activation point is in the bmp2tiff.c file (which was removed before the 4.0.7 release).
Remediation
There is no fixed version for Debian:12
tiff
.
References
low severity
- Vulnerable module: openexr/libopenexr-3-1-30
- Introduced through: openexr/libopenexr-3-1-30@3.1.5-5 and openexr/libopenexr-dev@3.1.5-5
Detailed paths
-
Introduced through: python@latest › openexr/libopenexr-3-1-30@3.1.5-5
-
Introduced through: python@latest › openexr/libopenexr-dev@3.1.5-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openexr
package and not the openexr
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Due to a failure in validating the number of scanline samples of a OpenEXR file containing deep scanline data, Academy Software Foundation OpenEX image parsing library version 3.2.1 and prior is susceptible to a heap-based buffer overflow vulnerability. This issue was resolved as of versions v3.2.2 and v3.1.12 of the affected library.
Remediation
There is no fixed version for Debian:12
openexr
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-5841
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LSB6DB5LAKGPLRXEF5HDNGUMT7GIFT2C/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XWMINVKQLSUHECXBSQMZFCSDRIHFOJJI/
- https://takeonme.org/cves/CVE-2023-5841.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u10, glibc/libc-dev-bin@2.36-9+deb12u10 and others
Detailed paths
-
Introduced through: python@latest › glibc/libc-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc-dev-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6-dev@2.36-9+deb12u10
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc
package and not the glibc
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
Remediation
There is no fixed version for Debian:12
glibc
.
References
- https://security-tracker.debian.org/tracker/CVE-2019-1010023
- https://support.f5.com/csp/article/K11932200?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22851
- http://www.securityfocus.com/bid/109167
- https://ubuntu.com/security/CVE-2019-1010023
- https://support.f5.com/csp/article/K11932200?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: libheif/libheif1
- Introduced through: libheif/libheif1@1.15.1-1+deb12u1
Detailed paths
-
Introduced through: python@latest › libheif/libheif1@1.15.1-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libheif
package and not the libheif
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libheif v1.17.5 was discovered to contain a segmentation violation via the function find_exif_tag at /libheif/exif.cc.
Remediation
There is no fixed version for Debian:12
libheif
.
References
low severity
- Vulnerable module: libwmf/libwmf-0.2-7
- Introduced through: libwmf/libwmf-0.2-7@0.2.12-5.1, libwmf/libwmf-dev@0.2.12-5.1 and others
Detailed paths
-
Introduced through: python@latest › libwmf/libwmf-0.2-7@0.2.12-5.1
-
Introduced through: python@latest › libwmf/libwmf-dev@0.2.12-5.1
-
Introduced through: python@latest › libwmf/libwmflite-0.2-7@0.2.12-5.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libwmf
package and not the libwmf
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The _gdGetColors function in gd_gd.c in PHP 5.2.11 and 5.3.x before 5.3.1, and the GD Graphics Library 2.x, does not properly verify a certain colorsTotal structure member, which might allow remote attackers to conduct buffer overflow or buffer over-read attacks via a crafted GD file, a different vulnerability than CVE-2009-3293. NOTE: some of these details are obtained from third party information.
Remediation
There is no fixed version for Debian:12
libwmf
.
References
- https://security-tracker.debian.org/tracker/CVE-2009-3546
- http://marc.info/?l=oss-security&m=125562113503923&w=2
- http://svn.php.net/viewvc?view=revision&revision=289557
- http://www.vupen.com/english/advisories/2009/2929
- http://www.vupen.com/english/advisories/2009/2930
- http://www.openwall.com/lists/oss-security/2009/11/20/5
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11199
- http://secunia.com/advisories/37069
- http://secunia.com/advisories/37080
- http://secunia.com/advisories/38055
- http://www.securityfocus.com/bid/36712
- https://access.redhat.com/errata/RHSA-2010:0003
- https://access.redhat.com/errata/RHSA-2010:0040
- https://access.redhat.com/security/cve/CVE-2009-3546
- https://bugzilla.redhat.com/show_bug.cgi?id=529213
- http://www.mandriva.com/security/advisories?name=MDVSA-2009:285
- http://www.redhat.com/support/errata/RHSA-2010-0003.html
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An integer overflow vulnerability was found in tiftoimage function in openjpeg 2.1.2, resulting in heap buffer overflow.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
- https://security-tracker.debian.org/tracker/CVE-2016-9580
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9580
- https://security.gentoo.org/glsa/201710-26
- https://github.com/szukw000/openjpeg/commit/cadff5fb6e73398de26a92e96d3d7cac893af255
- https://github.com/uclouvain/openjpeg/issues/871
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-9580
- http://www.securityfocus.com/bid/94822
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An infinite loop vulnerability in tiftoimage that results in heap buffer overflow in convert_32s_C1P1 was found in openjpeg 2.1.2.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
- https://security-tracker.debian.org/tracker/CVE-2016-9581
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9581
- https://security.gentoo.org/glsa/201710-26
- https://github.com/szukw000/openjpeg/commit/cadff5fb6e73398de26a92e96d3d7cac893af255
- https://github.com/uclouvain/openjpeg/issues/872
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-9581
- http://www.securityfocus.com/bid/94822
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in OpenJPEG 2.3.0. Missing checks for header_info.height and header_info.width in the function pnmtoimage in bin/jpwl/convert.c can lead to a heap-based buffer overflow.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in OpenJPEG 2.3.0. A heap-based buffer overflow was discovered in the function t2_encode_packet in lib/openmj2/t2.c. The vulnerability causes an out-of-bounds write, which may lead to remote denial of service or possibly unspecified other impact.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6+deb12u2, tiff/libtiff6@4.5.0-6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › tiff/libtiff-dev@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiff6@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiffxx6@4.5.0-6+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff
package and not the tiff
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
LibTIFF version 4.0.7 is vulnerable to a heap-based buffer over-read in tif_lzw.c resulting in DoS or code execution via a crafted bmp image to tools/bmp2tiff.
Remediation
There is no fixed version for Debian:12
tiff
.
References
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6+deb12u2, tiff/libtiff6@4.5.0-6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › tiff/libtiff-dev@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiff6@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiffxx6@4.5.0-6+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff
package and not the tiff
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In LibTIFF 4.0.8, there is a heap-based use-after-free in the t2p_writeproc function in tiff2pdf.c. NOTE: there is a third-party report of inability to reproduce this issue
Remediation
There is no fixed version for Debian:12
tiff
.
References
low severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u2, perl/libperl5.36@5.36.0-7+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › perl@5.36.0-7+deb12u2
-
Introduced through: python@latest › perl/libperl5.36@5.36.0-7+deb12u2
-
Introduced through: python@latest › perl/perl-base@5.36.0-7+deb12u2
-
Introduced through: python@latest › perl/perl-modules-5.36@5.36.0-7+deb12u2
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl
package and not the perl
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
HTTP::Tiny before 0.083, a Perl core module since 5.13.9 and available standalone on CPAN, has an insecure default TLS configuration where users must opt in to verify certificates.
Remediation
There is no fixed version for Debian:12
perl
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-31486
- https://security.netapp.com/advisory/ntap-20241129-0011/
- http://www.openwall.com/lists/oss-security/2023/04/29/1
- http://www.openwall.com/lists/oss-security/2023/05/03/3
- http://www.openwall.com/lists/oss-security/2023/05/03/5
- http://www.openwall.com/lists/oss-security/2023/05/07/2
- https://blog.hackeriet.no/perl-http-tiny-insecure-tls-default-affects-cpan-modules/
- https://github.com/chansen/p5-http-tiny/pull/153
- https://hackeriet.github.io/cpan-http-tiny-overview/
- https://www.openwall.com/lists/oss-security/2023/04/18/14
- https://www.openwall.com/lists/oss-security/2023/05/03/4
- https://www.reddit.com/r/perl/comments/111tadi/psa_httptiny_disabled_ssl_verification_by_default/
low severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u2, perl/libperl5.36@5.36.0-7+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › perl@5.36.0-7+deb12u2
-
Introduced through: python@latest › perl/libperl5.36@5.36.0-7+deb12u2
-
Introduced through: python@latest › perl/perl-base@5.36.0-7+deb12u2
-
Introduced through: python@latest › perl/perl-modules-5.36@5.36.0-7+deb12u2
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl
package and not the perl
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
CPAN.pm before 2.35 does not verify TLS certificates when downloading distributions over HTTPS.
Remediation
There is no fixed version for Debian:12
perl
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-31484
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BM6UW55CNFUTNGD5ZRKGUKKKFDJGMFHL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LEGCEOKFJVBJ2QQ6S2H4NAEWTUERC7SB/
- http://www.openwall.com/lists/oss-security/2023/04/29/1
- http://www.openwall.com/lists/oss-security/2023/05/03/3
- http://www.openwall.com/lists/oss-security/2023/05/03/5
- http://www.openwall.com/lists/oss-security/2023/05/07/2
- https://blog.hackeriet.no/perl-http-tiny-insecure-tls-default-affects-cpan-modules/
- https://github.com/andk/cpanpm/pull/175
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BM6UW55CNFUTNGD5ZRKGUKKKFDJGMFHL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LEGCEOKFJVBJ2QQ6S2H4NAEWTUERC7SB/
- https://metacpan.org/dist/CPAN/changes
- https://security.netapp.com/advisory/ntap-20240621-0007/
- https://www.openwall.com/lists/oss-security/2023/04/18/14
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u5
Detailed paths
-
Introduced through: python@latest › openssh/openssh-client@1:9.2p1-2+deb12u5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh
package and not the openssh
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
scp in OpenSSH through 8.3p1 allows command injection in the scp.c toremote function, as demonstrated by backtick characters in the destination argument. NOTE: the vendor reportedly has stated that they intentionally omit validation of "anomalous argument transfers" because that could "stand a great chance of breaking existing workflows."
Remediation
There is no fixed version for Debian:12
openssh
.
References
- https://security-tracker.debian.org/tracker/CVE-2020-15778
- https://security.netapp.com/advisory/ntap-20200731-0007/
- https://github.com/cpandya2909/CVE-2020-15778/
- https://news.ycombinator.com/item?id=25005567
- https://www.openssh.com/security.html
- https://github.com/cpandya2909/CVE-2020-15778#example
- https://access.redhat.com/errata/RHSA-2024:3166
- https://security.gentoo.org/glsa/202212-06
low severity
- Vulnerable module: tcl8.6
- Introduced through: tcl8.6@8.6.13+dfsg-2, tcl8.6/libtcl8.6@8.6.13+dfsg-2 and others
Detailed paths
-
Introduced through: python@latest › tcl8.6@8.6.13+dfsg-2
-
Introduced through: python@latest › tcl8.6/libtcl8.6@8.6.13+dfsg-2
-
Introduced through: python@latest › tcl8.6/tcl8.6-dev@8.6.13+dfsg-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tcl8.6
package and not the tcl8.6
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In Tcl 8.6.11, a format string vulnerability in nmakehlp.c might allow code execution via a crafted file. NOTE: multiple third parties dispute the significance of this finding
Remediation
There is no fixed version for Debian:12
tcl8.6
.
References
low severity
- Vulnerable module: aom/libaom3
- Introduced through: aom/libaom3@3.6.0-1+deb12u1
Detailed paths
-
Introduced through: python@latest › aom/libaom3@3.6.0-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream aom
package and not the aom
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
AOMedia v3.0.0 to v3.5.0 was discovered to contain an invalid read memory access via the component assign_frame_buffer_p in av1/common/av1_common_int.h.
Remediation
There is no fixed version for Debian:12
aom
.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability, which was classified as problematic, was found in GNU Binutils up to 2.43. This affects the function disassemble_bytes of the file binutils/objdump.c. The manipulation of the argument buf leads to stack-based buffer overflow. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. Upgrading to version 2.44 is able to address this issue. The identifier of the patch is baac6c221e9d69335bf41366a1c7d87d8ab2f893. It is recommended to upgrade the affected component.
Remediation
There is no fixed version for Debian:12
binutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-0840
- https://sourceware.org/bugzilla/attachment.cgi?id=15882
- https://sourceware.org/bugzilla/show_bug.cgi?id=32560
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=baac6c221e9d69335bf41366a1c7d87d8ab2f893
- https://vuldb.com/?ctiid.293997
- https://vuldb.com/?id.293997
- https://vuldb.com/?submit.485255
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been rated as critical. Affected by this issue is the function bfd_putl64 of the file bfd/libbfd.c of the component ld. The manipulation leads to memory corruption. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. Upgrading to version 2.44 is able to address this issue. It is recommended to upgrade the affected component. The code maintainer explains, that "[t]his bug has been fixed at some point between the 2.43 and 2.44 releases".
Remediation
There is no fixed version for Debian:12
binutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1179
- https://sourceware.org/bugzilla/attachment.cgi?id=15915
- https://sourceware.org/bugzilla/show_bug.cgi?id=32640
- https://sourceware.org/bugzilla/show_bug.cgi?id=32640#c1
- https://vuldb.com/?ctiid.295082
- https://vuldb.com/?id.295082
- https://vuldb.com/?submit.495376
- https://www.gnu.org/
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In BlueZ 5.42, a buffer overflow was observed in "read_n" function in "tools/hcidump.c" source file. This issue can be triggered by processing a corrupted dump file and will result in hcidump crash.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In BlueZ 5.42, an out-of-bounds read was identified in "packet_hexdump" function in "monitor/packet.c" source file. This issue can be triggered by processing a corrupted dump file and will result in btmon crash.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1 and expat/libexpat1-dev@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@latest › expat/libexpat1@2.5.0-1+deb12u1
-
Introduced through: python@latest › expat/libexpat1-dev@2.5.0-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat
package and not the expat
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libexpat through 2.6.1 allows an XML Entity Expansion attack when there is isolated use of external parsers (created via XML_ExternalEntityParserCreate).
Remediation
There is no fixed version for Debian:12
expat
.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28757
- http://www.openwall.com/lists/oss-security/2024/03/15/1
- https://github.com/libexpat/libexpat/issues/839
- https://github.com/libexpat/libexpat/pull/842
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FPLC6WDSRDUYS7F7JWAOVOHFNOUQ43DD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LKJ7V5F6LJCEQJXDBWGT27J7NAP3E3N7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VK2O34GH43NTHBZBN7G5Y6YKJKPUCTBE/
- https://security.netapp.com/advisory/ntap-20240322-0001/
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1 and expat/libexpat1-dev@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@latest › expat/libexpat1@2.5.0-1+deb12u1
-
Introduced through: python@latest › expat/libexpat1-dev@2.5.0-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat
package and not the expat
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libexpat through 2.5.0 allows a denial of service (resource consumption) because many full reparsings are required in the case of a large token for which multiple buffer fills are needed.
Remediation
There is no fixed version for Debian:12
expat
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-52425
- http://www.openwall.com/lists/oss-security/2024/03/20/5
- https://github.com/libexpat/libexpat/pull/789
- https://lists.debian.org/debian-lts-announce/2024/04/msg00006.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WNUBSGZFEZOBHJFTAD42SAN4ATW2VEMV/
- https://security.netapp.com/advisory/ntap-20240614-0003/
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1 and expat/libexpat1-dev@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@latest › expat/libexpat1@2.5.0-1+deb12u1
-
Introduced through: python@latest › expat/libexpat1-dev@2.5.0-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat
package and not the expat
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A stack overflow vulnerability exists in the libexpat library due to the way it handles recursive entity expansion in XML documents. When parsing an XML document with deeply nested entity references, libexpat can be forced to recurse indefinitely, exhausting the stack space and causing a crash. This issue could lead to denial of service (DoS) or, in some cases, exploitable memory corruption, depending on the environment and library usage.
Remediation
There is no fixed version for Debian:12
expat
.
References
- https://security-tracker.debian.org/tracker/CVE-2024-8176
- https://access.redhat.com/security/cve/CVE-2024-8176
- https://bugzilla.redhat.com/show_bug.cgi?id=2310137
- https://github.com/libexpat/libexpat/issues/893
- http://www.openwall.com/lists/oss-security/2025/03/15/1
- https://blog.hartwork.org/posts/expat-2-7-0-released/
- https://bugzilla.suse.com/show_bug.cgi?id=1239618
- https://github.com/libexpat/libexpat/blob/R_2_7_0/expat/Changes#L40-L52
- https://gitlab.alpinelinux.org/alpine/aports/-/commit/d068c3ff36fc6f4789988a09c69b434db757db53
- https://ubuntu.com/security/CVE-2024-8176
- https://security.netapp.com/advisory/ntap-20250328-0009/
- https://access.redhat.com/errata/RHSA-2025:3531
- https://access.redhat.com/errata/RHSA-2025:3734
- https://access.redhat.com/errata/RHSA-2025:3913
- https://access.redhat.com/errata/RHSA-2025:4048
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.5-0+deb12u2 and git/git-man@1:2.39.5-0+deb12u2
Detailed paths
-
Introduced through: python@latest › git@1:2.39.5-0+deb12u2
-
Introduced through: python@latest › git/git-man@1:2.39.5-0+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream git
package and not the git
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The --mirror documentation for Git through 2.35.1 does not mention the availability of deleted content, aka the "GitBleed" issue. This could present a security risk if information-disclosure auditing processes rely on a clone operation without the --mirror option. Note: This has been disputed by multiple 3rd parties who believe this is an intended feature of the git binary and does not pose a security risk.
Remediation
There is no fixed version for Debian:12
git
.
References
- https://security-tracker.debian.org/tracker/CVE-2022-24975
- https://lore.kernel.org/git/xmqq4k14qe9g.fsf%40gitster.g/
- https://github.com/git/git/blob/2dc94da3744bfbbf145eca587a0f5ff480cc5867/Documentation/git-clone.txt#L185-L191
- https://www.aquasec.com/blog/undetected-hard-code-secrets-expose-corporations/
- https://wwws.nightwatchcybersecurity.com/2022/02/11/gitbleed/
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u10, glibc/libc-dev-bin@2.36-9+deb12u10 and others
Detailed paths
-
Introduced through: python@latest › glibc/libc-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc-dev-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6-dev@2.36-9+deb12u10
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc
package and not the glibc
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(\227|)(\1\1|t1|\\2537)+' in grep.
Remediation
There is no fixed version for Debian:12
glibc
.
References
- https://security-tracker.debian.org/tracker/CVE-2018-20796
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&utm_medium=RSS
- https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34141
- https://lists.gnu.org/archive/html/bug-gnulib/2019-01/msg00108.html
- https://security.netapp.com/advisory/ntap-20190315-0002/
- http://www.securityfocus.com/bid/107160
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-20796
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u10, glibc/libc-dev-bin@2.36-9+deb12u10 and others
Detailed paths
-
Introduced through: python@latest › glibc/libc-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc-dev-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6-dev@2.36-9+deb12u10
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc
package and not the glibc
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(|)(\1\1)*' in grep, a different issue than CVE-2018-20796. NOTE: the software maintainer disputes that this is a vulnerability because the behavior occurs only with a crafted pattern
Remediation
There is no fixed version for Debian:12
glibc
.
References
- https://security-tracker.debian.org/tracker/CVE-2019-9192
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=24269
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2019-9192
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: harfbuzz/libharfbuzz0b
- Introduced through: harfbuzz/libharfbuzz0b@6.0.0+dfsg-3
Detailed paths
-
Introduced through: python@latest › harfbuzz/libharfbuzz0b@6.0.0+dfsg-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream harfbuzz
package and not the harfbuzz
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
hb-ot-layout-gsubgpos.hh in HarfBuzz through 6.0.0 allows attackers to trigger O(n^2) growth via consecutive marks during the process of looking back for base glyphs when attaching marks.
Remediation
There is no fixed version for Debian:12
harfbuzz
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-25193
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KWCHWSICWVZSAXP2YAXM65JC2GR53547/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YZ5M2GSAIHFPLHYJXUPQ2QDJCLWXUGO3/
- https://chromium.googlesource.com/chromium/src/+/e1f324aa681af54101c1f2d173d92adb80e37088/DEPS#361
- https://github.com/harfbuzz/harfbuzz/blob/2822b589bc837fae6f66233e2cf2eef0f6ce8470/src/hb-ot-layout-gsubgpos.hh
- https://github.com/harfbuzz/harfbuzz/commit/85be877925ddbf34f74a1229f3ca1716bb6170dc
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KWCHWSICWVZSAXP2YAXM65JC2GR53547/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YZ5M2GSAIHFPLHYJXUPQ2QDJCLWXUGO3/
- https://security.netapp.com/advisory/ntap-20230725-0006/
low severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6+deb12u2
…and 10 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick
package and not the imagemagick
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A flaw was found in ImageMagick in versions before 7.0.11, where a division by zero in sRGBTransformImage() in the MagickCore/colorspace.c may trigger undefined behavior via a crafted image file that is submitted by an attacker processed by an application using ImageMagick. The highest threat from this vulnerability is to system availability.
Remediation
There is no fixed version for Debian:12
imagemagick
.
References
low severity
- Vulnerable module: jansson/libjansson4
- Introduced through: jansson/libjansson4@2.14-2
Detailed paths
-
Introduced through: python@latest › jansson/libjansson4@2.14-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream jansson
package and not the jansson
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in Jansson through 2.13.1. Due to a parsing error in json_loads, there's an out-of-bounds read-access bug. NOTE: the vendor reports that this only occurs when a programmer fails to follow the API specification
Remediation
There is no fixed version for Debian:12
jansson
.
References
low severity
- Vulnerable module: krb5/krb5-multidev
- Introduced through: krb5/krb5-multidev@1.20.1-2+deb12u2, krb5/libgssapi-krb5-2@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › krb5/krb5-multidev@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libgssrpc4@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkadm5clnt-mit12@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkadm5srv-mit12@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkdb5-10@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5-dev@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5support0@1.20.1-2+deb12u2
…and 7 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5
package and not the krb5
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.
Remediation
There is no fixed version for Debian:12
krb5
.
References
- https://security-tracker.debian.org/tracker/CVE-2018-5709
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5709
- https://github.com/poojamnit/Kerberos-V5-1.16-Vulnerabilities/tree/master/Integer%20Overflow
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-5709
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.10.1-3
Detailed paths
-
Introduced through: python@latest › libgcrypt20@1.10.1-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libgcrypt20
package and not the libgcrypt20
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.
Remediation
There is no fixed version for Debian:12
libgcrypt20
.
References
- https://security-tracker.debian.org/tracker/CVE-2018-6829
- https://github.com/weikengchen/attack-on-libgcrypt-elgamal
- https://github.com/weikengchen/attack-on-libgcrypt-elgamal/wiki
- https://lists.gnupg.org/pipermail/gcrypt-devel/2018-February/004394.html
- https://www.oracle.com/security-alerts/cpujan2020.html
low severity
new
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1 and libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: python@latest › libxml2@2.9.14+dfsg-1.3~deb12u1
-
Introduced through: python@latest › libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2
package and not the libxml2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In libxml2 before 2.13.8 and 2.14.x before 2.14.2, out-of-bounds memory access can occur in the Python API (Python bindings) because of an incorrect return value. This occurs in xmlPythonFileRead and xmlPythonFileReadRaw because of a difference between bytes and characters.
Remediation
There is no fixed version for Debian:12
libxml2
.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1 and libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: python@latest › libxml2@2.9.14+dfsg-1.3~deb12u1
-
Introduced through: python@latest › libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2
package and not the libxml2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in libxml2 before 2.11.7 and 2.12.x before 2.12.5. When using the XML Reader interface with DTD validation and XInclude expansion enabled, processing crafted XML documents can lead to an xmlValidatePopElement use-after-free.
Remediation
There is no fixed version for Debian:12
libxml2
.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
There is a NULL Pointer Access in function imagetopnm of convert.c:1943(jp2) of OpenJPEG 2.1.2. image->comps[compno].data is not assigned a value after initialization(NULL). Impact is Denial of Service.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
There is a NULL pointer dereference in function imagetobmp of convertbmp.c:980 of OpenJPEG 2.1.2. image->comps[0].data is not assigned a value after initialization(NULL). Impact is Denial of Service.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: python@latest › openldap/libldap-2.5-0@2.5.13+dfsg-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap
package and not the openldap
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors.
Remediation
There is no fixed version for Debian:12
openldap
.
References
- https://security-tracker.debian.org/tracker/CVE-2015-3276
- http://www.oracle.com/technetwork/topics/security/linuxbulletinoct2015-2719645.html
- https://bugzilla.redhat.com/show_bug.cgi?id=1238322
- http://rhn.redhat.com/errata/RHSA-2015-2131.html
- http://www.securitytracker.com/id/1034221
- https://access.redhat.com/errata/RHSA-2015:2131
- https://access.redhat.com/security/cve/CVE-2015-3276
low severity
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: python@latest › openldap/libldap-2.5-0@2.5.13+dfsg-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap
package and not the openldap
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability was found in openldap. This security flaw causes a null pointer dereference in ber_memalloc_x() function.
Remediation
There is no fixed version for Debian:12
openldap
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-2953
- http://seclists.org/fulldisclosure/2023/Jul/47
- http://seclists.org/fulldisclosure/2023/Jul/48
- http://seclists.org/fulldisclosure/2023/Jul/52
- https://access.redhat.com/security/cve/CVE-2023-2953
- https://bugs.openldap.org/show_bug.cgi?id=9904
- https://security.netapp.com/advisory/ntap-20230703-0005/
- https://support.apple.com/kb/HT213843
- https://support.apple.com/kb/HT213844
- https://support.apple.com/kb/HT213845
low severity
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: python@latest › openldap/libldap-2.5-0@2.5.13+dfsg-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap
package and not the openldap
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation.
Remediation
There is no fixed version for Debian:12
openldap
.
References
- https://security-tracker.debian.org/tracker/CVE-2017-17740
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17740
- http://www.openldap.org/its/index.cgi/Incoming?id=8759
- http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00053.html
- http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00058.html
- https://kc.mcafee.com/corporate/index?page=content&id=SB10365
- https://www.oracle.com/security-alerts/cpuapr2022.html
low severity
- Vulnerable module: patch
- Introduced through: patch@2.7.6-7
Detailed paths
-
Introduced through: python@latest › patch@2.7.6-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream patch
package and not the patch
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A double free exists in the another_hunk function in pch.c in GNU patch through 2.7.6.
Remediation
There is no fixed version for Debian:12
patch
.
References
- https://security-tracker.debian.org/tracker/CVE-2018-6952
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6952
- https://security.gentoo.org/glsa/201904-17
- https://savannah.gnu.org/bugs/index.php?53133
- https://access.redhat.com/errata/RHSA-2019:2033
- http://www.securityfocus.com/bid/103047
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-6952
low severity
- Vulnerable module: patch
- Introduced through: patch@2.7.6-7
Detailed paths
-
Introduced through: python@latest › patch@2.7.6-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream patch
package and not the patch
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in GNU patch through 2.7.6. There is a segmentation fault, associated with a NULL pointer dereference, leading to a denial of service in the intuit_diff_type function in pch.c, aka a "mangled rename" issue.
Remediation
There is no fixed version for Debian:12
patch
.
References
- https://security-tracker.debian.org/tracker/CVE-2018-6951
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6951
- https://security.gentoo.org/glsa/201904-17
- https://git.savannah.gnu.org/cgit/patch.git/commit/?id=f290f48a621867084884bfff87f8093c15195e6a
- https://savannah.gnu.org/bugs/index.php?53132
- http://www.securityfocus.com/bid/103044
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-6951
- https://usn.ubuntu.com/3624-1/
low severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7+deb12u2, perl/libperl5.36@5.36.0-7+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › perl@5.36.0-7+deb12u2
-
Introduced through: python@latest › perl/libperl5.36@5.36.0-7+deb12u2
-
Introduced through: python@latest › perl/perl-base@5.36.0-7+deb12u2
-
Introduced through: python@latest › perl/perl-modules-5.36@5.36.0-7+deb12u2
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl
package and not the perl
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
_is_safe in the File::Temp module for Perl does not properly handle symlinks.
Remediation
There is no fixed version for Debian:12
perl
.
References
- https://security-tracker.debian.org/tracker/CVE-2011-4116
- https://github.com/Perl-Toolchain-Gang/File-Temp/issues/14
- https://rt.cpan.org/Public/Bug/Display.html?id=69106
- https://seclists.org/oss-sec/2011/q4/238
- http://www.openwall.com/lists/oss-security/2011/11/04/2
- http://www.openwall.com/lists/oss-security/2011/11/04/4
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6+deb12u2, tiff/libtiff6@4.5.0-6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › tiff/libtiff-dev@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiff6@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiffxx6@4.5.0-6+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff
package and not the tiff
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
LibTIFF 4.0.8 has multiple memory leak vulnerabilities, which allow attackers to cause a denial of service (memory consumption), as demonstrated by tif_open.c, tif_lzw.c, and tif_aux.c. NOTE: Third parties were unable to reproduce the issue
Remediation
There is no fixed version for Debian:12
tiff
.
References
- https://security-tracker.debian.org/tracker/CVE-2017-16232
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16232
- http://packetstormsecurity.com/files/150896/LibTIFF-4.0.8-Memory-Leak.html
- http://lists.opensuse.org/opensuse-security-announce/2018-01/msg00036.html
- http://lists.opensuse.org/opensuse-security-announce/2018-01/msg00041.html
- http://www.openwall.com/lists/oss-security/2017/11/01/11
- http://www.openwall.com/lists/oss-security/2017/11/01/3
- http://www.openwall.com/lists/oss-security/2017/11/01/7
- http://www.openwall.com/lists/oss-security/2017/11/01/8
- http://seclists.org/fulldisclosure/2018/Dec/32
- http://seclists.org/fulldisclosure/2018/Dec/47
- http://www.securityfocus.com/bid/101696
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6+deb12u2, tiff/libtiff6@4.5.0-6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › tiff/libtiff-dev@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiff6@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiffxx6@4.5.0-6+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff
package and not the tiff
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An out-of-memory flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFRasterScanlineSize64() API. This flaw allows a remote attacker to cause a denial of service via a crafted input with a size smaller than 379 KB.
Remediation
There is no fixed version for Debian:12
tiff
.
References
low severity
- Vulnerable module: m4
- Introduced through: m4@1.4.19-3
Detailed paths
-
Introduced through: python@latest › m4@1.4.19-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream m4
package and not the m4
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The (1) maketemp and (2) mkstemp builtin functions in GNU m4 before 1.4.11 do not quote their output when a file is created, which might allow context-dependent attackers to trigger a macro expansion, leading to unspecified use of an incorrect filename.
Remediation
There is no fixed version for Debian:12
m4
.
References
- https://security-tracker.debian.org/tracker/CVE-2008-1687
- http://slackware.com/security/viewer.php?l=slackware-security&y=2008&m=slackware-security.510612
- http://www.vupen.com/english/advisories/2008/1151/references
- http://xforce.iss.net/xforce/xfdb/41706
- http://www.openwall.com/lists/oss-security/2008/04/07/1
- http://www.openwall.com/lists/oss-security/2008/04/07/12
- http://www.openwall.com/lists/oss-security/2008/04/07/3
- http://www.openwall.com/lists/oss-security/2008/04/07/4
- http://secunia.com/advisories/29671
- http://secunia.com/advisories/29729
- http://www.securityfocus.com/bid/28688
- https://exchange.xforce.ibmcloud.com/vulnerabilities/41706
low severity
- Vulnerable module: m4
- Introduced through: m4@1.4.19-3
Detailed paths
-
Introduced through: python@latest › m4@1.4.19-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream m4
package and not the m4
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Unspecified vulnerability in GNU m4 before 1.4.11 might allow context-dependent attackers to execute arbitrary code, related to improper handling of filenames specified with the -F option. NOTE: it is not clear when this issue crosses privilege boundaries.
Remediation
There is no fixed version for Debian:12
m4
.
References
- https://security-tracker.debian.org/tracker/CVE-2008-1688
- http://osvdb.org/44272
- http://slackware.com/security/viewer.php?l=slackware-security&y=2008&m=slackware-security.510612
- http://www.vupen.com/english/advisories/2008/1151/references
- http://xforce.iss.net/xforce/xfdb/41704
- http://www.openwall.com/lists/oss-security/2008/04/07/1
- http://www.openwall.com/lists/oss-security/2008/04/07/3
- http://secunia.com/advisories/29671
- http://secunia.com/advisories/29729
- http://www.securityfocus.com/bid/28688
- https://exchange.xforce.ibmcloud.com/vulnerabilities/41704
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u5
Detailed paths
-
Introduced through: python@latest › openssh/openssh-client@1:9.2p1-2+deb12u5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh
package and not the openssh
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
OpenSSH through 9.6, when common types of DRAM are used, might allow row hammer attacks (for authentication bypass) because the integer value of authenticated in mm_answer_authpassword does not resist flips of a single bit. NOTE: this is applicable to a certain threat model of attacker-victim co-location in which the attacker has user privileges.
Remediation
There is no fixed version for Debian:12
openssh
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-51767
- https://access.redhat.com/security/cve/CVE-2023-51767
- https://arxiv.org/abs/2309.02545
- https://bugzilla.redhat.com/show_bug.cgi?id=2255850
- https://github.com/openssh/openssh-portable/blob/8241b9c0529228b4b86d88b1a6076fb9f97e4a99/auth-passwd.c#L77
- https://github.com/openssh/openssh-portable/blob/8241b9c0529228b4b86d88b1a6076fb9f97e4a99/monitor.c#L878
- https://security.netapp.com/advisory/ntap-20240125-0006/
- https://ubuntu.com/security/CVE-2023-51767
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u5
Detailed paths
-
Introduced through: python@latest › openssh/openssh-client@1:9.2p1-2+deb12u5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh
package and not the openssh
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In OpenSSH 7.9, due to accepting and displaying arbitrary stderr output from the server, a malicious server (or Man-in-The-Middle attacker) can manipulate the client output, for example to use ANSI control codes to hide additional files being transferred.
Remediation
There is no fixed version for Debian:12
openssh
.
References
- https://security-tracker.debian.org/tracker/CVE-2019-6110
- https://www.exploit-db.com/exploits/46193/
- https://security.gentoo.org/glsa/201903-16
- https://cvsweb.openbsd.org/src/usr.bin/ssh/progressmeter.c
- https://cvsweb.openbsd.org/src/usr.bin/ssh/scp.c
- https://sintonen.fi/advisories/scp-client-multiple-vulnerabilities.txt
- https://security.netapp.com/advisory/ntap-20190213-0001/
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2019-6110
- https://cert-portal.siemens.com/productcert/pdf/ssa-412672.pdf
- https://www.exploit-db.com/exploits/46516
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A heap-based buffer over-read exists in the function d_expression_1 in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31.1. A crafted input can cause segmentation faults, leading to denial-of-service, as demonstrated by c++filt.
Remediation
There is no fixed version for Debian:12
binutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2018-20712
- https://support.f5.com/csp/article/K38336243
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20712
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88629
- https://sourceware.org/bugzilla/show_bug.cgi?id=24043
- http://www.securityfocus.com/bid/106563
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-20712
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A potential heap based buffer overflow was found in _bfd_elf_slurp_version_tables() in bfd/elf.c. This may lead to loss of availability.
Remediation
There is no fixed version for Debian:12
binutils
.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in GNU libiberty, as distributed in GNU Binutils 2.36. It is a stack-overflow issue in demangle_type in rust-demangle.c.
Remediation
There is no fixed version for Debian:12
binutils
.
References
low severity
- Vulnerable module: cairo/libcairo-gobject2
- Introduced through: cairo/libcairo-gobject2@1.16.0-7, cairo/libcairo-script-interpreter2@1.16.0-7 and others
Detailed paths
-
Introduced through: python@latest › cairo/libcairo-gobject2@1.16.0-7
-
Introduced through: python@latest › cairo/libcairo-script-interpreter2@1.16.0-7
-
Introduced through: python@latest › cairo/libcairo2@1.16.0-7
-
Introduced through: python@latest › cairo/libcairo2-dev@1.16.0-7
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream cairo
package and not the cairo
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in cairo 1.16.0. There is an infinite loop in the function _arc_error_normalized in the file cairo-arc.c, related to _arc_max_angle_for_tolerance_normalized.
Remediation
There is no fixed version for Debian:12
cairo
.
References
- https://security-tracker.debian.org/tracker/CVE-2019-6462
- https://github.com/TeamSeri0us/pocs/tree/master/gerbv
- https://gitlab.freedesktop.org/cairo/cairo/issues/353
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2019-6462
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: cairo/libcairo-gobject2
- Introduced through: cairo/libcairo-gobject2@1.16.0-7, cairo/libcairo-script-interpreter2@1.16.0-7 and others
Detailed paths
-
Introduced through: python@latest › cairo/libcairo-gobject2@1.16.0-7
-
Introduced through: python@latest › cairo/libcairo-script-interpreter2@1.16.0-7
-
Introduced through: python@latest › cairo/libcairo2@1.16.0-7
-
Introduced through: python@latest › cairo/libcairo2-dev@1.16.0-7
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream cairo
package and not the cairo
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
cairo through 1.15.14 has an out-of-bounds stack-memory write during processing of a crafted document by WebKitGTK+ because of the interaction between cairo-rectangular-scan-converter.c (the generate and render_rows functions) and cairo-image-compositor.c (the _cairo_image_spans_and_zero function).
Remediation
There is no fixed version for Debian:12
cairo
.
References
- https://security-tracker.debian.org/tracker/CVE-2018-18064
- https://gitlab.freedesktop.org/cairo/cairo/issues/341
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-18064
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: cairo/libcairo-gobject2
- Introduced through: cairo/libcairo-gobject2@1.16.0-7, cairo/libcairo-script-interpreter2@1.16.0-7 and others
Detailed paths
-
Introduced through: python@latest › cairo/libcairo-gobject2@1.16.0-7
-
Introduced through: python@latest › cairo/libcairo-script-interpreter2@1.16.0-7
-
Introduced through: python@latest › cairo/libcairo2@1.16.0-7
-
Introduced through: python@latest › cairo/libcairo2-dev@1.16.0-7
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream cairo
package and not the cairo
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in cairo 1.16.0. There is an assertion problem in the function _cairo_arc_in_direction in the file cairo-arc.c.
Remediation
There is no fixed version for Debian:12
cairo
.
References
- https://security-tracker.debian.org/tracker/CVE-2019-6461
- https://github.com/TeamSeri0us/pocs/tree/master/gerbv
- https://gitlab.freedesktop.org/cairo/cairo/issues/352
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2019-6461
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: python@latest › coreutils@9.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream coreutils
package and not the coreutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.
Remediation
There is no fixed version for Debian:12
coreutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2016-2781
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://www.openwall.com/lists/oss-security/2016/02/28/2
- http://www.openwall.com/lists/oss-security/2016/02/28/3
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2016-2781
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: djvulibre/libdjvulibre-dev
- Introduced through: djvulibre/libdjvulibre-dev@3.5.28-2+b1, djvulibre/libdjvulibre-text@3.5.28-2 and others
Detailed paths
-
Introduced through: python@latest › djvulibre/libdjvulibre-dev@3.5.28-2+b1
-
Introduced through: python@latest › djvulibre/libdjvulibre-text@3.5.28-2
-
Introduced through: python@latest › djvulibre/libdjvulibre21@3.5.28-2+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream djvulibre
package and not the djvulibre
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered IW44EncodeCodec.cpp in djvulibre 3.5.28 in allows attackers to cause a denial of service via divide by zero.
Remediation
There is no fixed version for Debian:12
djvulibre
.
References
- https://security-tracker.debian.org/tracker/CVE-2021-46312
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4APFAWR7QE27GXQMRKR6XKNZWWUJ5YMH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HN4JOIBNMJMW2NQSGT6DCDCQZJ2ROFM7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XEEGAR4WUF6LTOJEHSON7I2MBTPFTVR5/
- https://sourceforge.net/p/djvu/bugs/344/
low severity
- Vulnerable module: djvulibre/libdjvulibre-dev
- Introduced through: djvulibre/libdjvulibre-dev@3.5.28-2+b1, djvulibre/libdjvulibre-text@3.5.28-2 and others
Detailed paths
-
Introduced through: python@latest › djvulibre/libdjvulibre-dev@3.5.28-2+b1
-
Introduced through: python@latest › djvulibre/libdjvulibre-text@3.5.28-2
-
Introduced through: python@latest › djvulibre/libdjvulibre21@3.5.28-2+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream djvulibre
package and not the djvulibre
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered IW44Image.cpp in djvulibre 3.5.28 in allows attackers to cause a denial of service via divide by zero.
Remediation
There is no fixed version for Debian:12
djvulibre
.
References
- https://security-tracker.debian.org/tracker/CVE-2021-46310
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4APFAWR7QE27GXQMRKR6XKNZWWUJ5YMH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HN4JOIBNMJMW2NQSGT6DCDCQZJ2ROFM7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XEEGAR4WUF6LTOJEHSON7I2MBTPFTVR5/
- https://sourceforge.net/p/djvu/bugs/345/
low severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6+deb12u2
…and 10 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick
package and not the imagemagick
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The WritePICONImage function in coders/xpm.c in ImageMagick 7.0.6-4 allows remote attackers to cause a denial of service (memory leak) via a crafted file that is mishandled in an AcquireSemaphoreInfo call.
Remediation
There is no fixed version for Debian:12
imagemagick
.
References
low severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6+deb12u2
…and 10 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick
package and not the imagemagick
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The WritePICONImage function in coders/xpm.c in ImageMagick 7.0.6-4 allows remote attackers to cause a denial of service (memory leak) via a crafted file that is mishandled in an OpenPixelCache call.
Remediation
There is no fixed version for Debian:12
imagemagick
.
References
low severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6+deb12u2
…and 10 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick
package and not the imagemagick
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In ImageMagick 7.0.8-11 Q16, a tiny input file 0x50 0x36 0x36 0x36 0x36 0x4c 0x36 0x38 0x36 0x36 0x36 0x36 0x36 0x36 0x1f 0x35 0x50 0x00 can result in a hang of several minutes during which CPU and memory resources are consumed until ultimately an attempted large memory allocation fails. Remote attackers could leverage this vulnerability to cause a denial of service via a crafted file.
Remediation
There is no fixed version for Debian:12
imagemagick
.
References
- https://security-tracker.debian.org/tracker/CVE-2018-15607
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15607
- https://github.com/ImageMagick/ImageMagick/issues/1255
- http://www.securityfocus.com/bid/105137
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-15607
- https://usn.ubuntu.com/4034-1/
low severity
- Vulnerable module: jbigkit/libjbig-dev
- Introduced through: jbigkit/libjbig-dev@2.1-6.1 and jbigkit/libjbig0@2.1-6.1
Detailed paths
-
Introduced through: python@latest › jbigkit/libjbig-dev@2.1-6.1
-
Introduced through: python@latest › jbigkit/libjbig0@2.1-6.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream jbigkit
package and not the jbigkit
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In LibTIFF 4.0.8, there is a memory malloc failure in tif_jbig.c. A crafted TIFF document can lead to an abort resulting in a remote denial of service attack.
Remediation
There is no fixed version for Debian:12
jbigkit
.
References
- https://security-tracker.debian.org/tracker/CVE-2017-9937
- http://bugzilla.maptools.org/show_bug.cgi?id=2707
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://www.securityfocus.com/bid/99304
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2017-9937
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1 and libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: python@latest › libxml2@2.9.14+dfsg-1.3~deb12u1
-
Introduced through: python@latest › libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2
package and not the libxml2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Xmlsoft Libxml2 v2.11.0 was discovered to contain an out-of-bounds read via the xmlSAX2StartElement() function at /libxml2/SAX2.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via supplying a crafted XML file. NOTE: the vendor's position is that the product does not support the legacy SAX1 interface with custom callbacks; there is a crash even without crafted input.
Remediation
There is no fixed version for Debian:12
libxml2
.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1 and libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: python@latest › libxml2@2.9.14+dfsg-1.3~deb12u1
-
Introduced through: python@latest › libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2
package and not the libxml2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails. This occurs in xmlUnlinkNode in tree.c. NOTE: the vendor's position is "I don't think these issues are critical enough to warrant a CVE ID ... because an attacker typically can't control when memory allocations fail."
Remediation
There is no fixed version for Debian:12
libxml2
.
References
low severity
- Vulnerable module: ncurses/libncurses-dev
- Introduced through: ncurses/libncurses-dev@6.4-4, ncurses/libncurses5-dev@6.4-4 and others
Detailed paths
-
Introduced through: python@latest › ncurses/libncurses-dev@6.4-4
-
Introduced through: python@latest › ncurses/libncurses5-dev@6.4-4
-
Introduced through: python@latest › ncurses/libncurses6@6.4-4
-
Introduced through: python@latest › ncurses/libncursesw5-dev@6.4-4
-
Introduced through: python@latest › ncurses/libncursesw6@6.4-4
-
Introduced through: python@latest › ncurses/libtinfo6@6.4-4
-
Introduced through: python@latest › ncurses/ncurses-base@6.4-4
-
Introduced through: python@latest › ncurses/ncurses-bin@6.4-4
…and 5 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses
package and not the ncurses
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
NCurse v6.4-20230418 was discovered to contain a segmentation fault via the component _nc_wrap_entry().
Remediation
There is no fixed version for Debian:12
ncurses
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-50495
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/
- https://lists.gnu.org/archive/html/bug-ncurses/2023-04/msg00020.html
- https://lists.gnu.org/archive/html/bug-ncurses/2023-04/msg00029.html
- https://security.netapp.com/advisory/ntap-20240119-0008/
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in OpenJPEG 2.3.0. It allows remote attackers to cause a denial of service (attempted excessive memory allocation) in opj_calloc in openjp2/opj_malloc.c, when called from opj_tcd_init_tile in openjp2/tcd.c, as demonstrated by the 64-bit opj_decompress.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Out-of-bounds accesses in the functions pi_next_lrcp, pi_next_rlcp, pi_next_rpcl, pi_next_pcrl, pi_next_rpcl, and pi_next_cprl in openmj2/pi.c in OpenJPEG through 2.3.0 allow remote attackers to cause a denial of service (application crash).
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
NULL Pointer Access in function imagetopnm of convert.c:2226(jp2) in OpenJPEG 2.1.2. Impact is Denial of Service. Someone must open a crafted j2k file.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
NULL pointer dereference vulnerabilities in the imagetopnm function in convert.c, sycc444_to_rgb function in color.c, color_esycc_to_rgb function in color.c, and sycc422_to_rgb function in color.c in OpenJPEG before 2.2.0 allow remote attackers to cause a denial of service (application crash) via crafted j2k files.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
NULL Pointer Access in function imagetopnm of convert.c(jp2):1289 in OpenJPEG 2.1.2. Impact is Denial of Service. Someone must open a crafted j2k file.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Heap Buffer Over-read in function imagetotga of convert.c(jp2):942 in OpenJPEG 2.1.2. Impact is Denial of Service. Someone must open a crafted j2k file.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
- Vulnerable module: pixman/libpixman-1-0
- Introduced through: pixman/libpixman-1-0@0.42.2-1 and pixman/libpixman-1-dev@0.42.2-1
Detailed paths
-
Introduced through: python@latest › pixman/libpixman-1-0@0.42.2-1
-
Introduced through: python@latest › pixman/libpixman-1-dev@0.42.2-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pixman
package and not the pixman
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
stress-test master commit e4c878 was discovered to contain a FPE vulnerability via the component combine_inner at /pixman-combine-float.c.
Remediation
There is no fixed version for Debian:12
pixman
.
References
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6+deb12u2, tiff/libtiff6@4.5.0-6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › tiff/libtiff-dev@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiff6@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiffxx6@4.5.0-6+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff
package and not the tiff
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability classified as problematic was found in LibTIFF 4.3.0. Affected by this vulnerability is the TIFF File Handler of tiff2ps. Opening a malicious file leads to a denial of service. The attack can be launched remotely but requires user interaction. The exploit has been disclosed to the public and may be used.
Remediation
There is no fixed version for Debian:12
tiff
.
References
- https://security-tracker.debian.org/tracker/CVE-2022-1210
- https://gitlab.com/libtiff/libtiff/-/issues/402
- https://gitlab.com/libtiff/libtiff/uploads/c3da94e53cf1e1e8e6d4d3780dc8c42f/example.tiff
- https://security.gentoo.org/glsa/202210-10
- https://security.netapp.com/advisory/ntap-20220513-0005/
- https://vuldb.com/?id.196363
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6+deb12u2, tiff/libtiff6@4.5.0-6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › tiff/libtiff-dev@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiff6@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiffxx6@4.5.0-6+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff
package and not the tiff
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
ijg-libjpeg before 9d, as used in tiff2pdf (from LibTIFF) and other products, does not check for a NULL pointer at a certain place in jpeg_fdct_16x16 in jfdctint.c.
Remediation
There is no fixed version for Debian:12
tiff
.
References
- https://security-tracker.debian.org/tracker/CVE-2018-10126
- http://bugzilla.maptools.org/show_bug.cgi?id=2786
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-10126
- https://gitlab.com/libtiff/libtiff/-/issues/128
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6+deb12u2, tiff/libtiff6@4.5.0-6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › tiff/libtiff-dev@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiff6@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiffxx6@4.5.0-6+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff
package and not the tiff
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An out-of-memory flaw was found in libtiff. Passing a crafted tiff file to TIFFOpen() API may allow a remote attacker to cause a denial of service via a craft input with size smaller than 379 KB.
Remediation
There is no fixed version for Debian:12
tiff
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-6277
- http://seclists.org/fulldisclosure/2024/Jul/16
- http://seclists.org/fulldisclosure/2024/Jul/17
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://seclists.org/fulldisclosure/2024/Jul/21
- http://seclists.org/fulldisclosure/2024/Jul/22
- http://seclists.org/fulldisclosure/2024/Jul/23
- https://access.redhat.com/security/cve/CVE-2023-6277
- https://bugzilla.redhat.com/show_bug.cgi?id=2251311
- https://gitlab.com/libtiff/libtiff/-/issues/614
- https://gitlab.com/libtiff/libtiff/-/merge_requests/545
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WJIN6DTSL3VODZUGWEUXLEL5DR53EZMV/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Y7ZGN2MZXJ6E57W3L4YBM3ZPAU3T7T5C/
- https://security.netapp.com/advisory/ntap-20240119-0002/
- https://support.apple.com/kb/HT214116
- https://support.apple.com/kb/HT214117
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
- https://support.apple.com/kb/HT214122
- https://support.apple.com/kb/HT214123
- https://support.apple.com/kb/HT214124
low severity
- Vulnerable module: libwmf/libwmf-0.2-7
- Introduced through: libwmf/libwmf-0.2-7@0.2.12-5.1, libwmf/libwmf-dev@0.2.12-5.1 and others
Detailed paths
-
Introduced through: python@latest › libwmf/libwmf-0.2-7@0.2.12-5.1
-
Introduced through: python@latest › libwmf/libwmf-dev@0.2.12-5.1
-
Introduced through: python@latest › libwmf/libwmflite-0.2-7@0.2.12-5.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libwmf
package and not the libwmf
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Multiple integer overflows in libgd in PHP before 5.2.4 allow remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a large (1) srcW or (2) srcH value to the (a) gdImageCopyResized function, or a large (3) sy (height) or (4) sx (width) value to the (b) gdImageCreate or the (c) gdImageCreateTrueColor function.
Remediation
There is no fixed version for Debian:12
libwmf
.
References
- https://security-tracker.debian.org/tracker/CVE-2007-3996
- http://www.debian.org/security/2008/dsa-1613
- http://security.gentoo.org/glsa/glsa-200712-13.xml
- http://www.gentoo.org/security/en/glsa/glsa-200710-02.xml
- http://bugs.gentoo.org/show_bug.cgi?id=201546
- http://securityreason.com/securityalert/3103
- http://secweb.se/en/advisories/php-imagecopyresized-integer-overflow/
- http://secweb.se/en/advisories/php-imagecreatetruecolor-integer-overflow/
- https://issues.rpath.com/browse/RPL-1693
- https://issues.rpath.com/browse/RPL-1702
- http://support.avaya.com/elmodocs2/security/ASA-2007-449.htm
- https://www.redhat.com/archives/fedora-package-announce/2007-September/msg00354.html
- http://www.php.net/ChangeLog-5.php#5.2.4
- http://www.php.net/releases/5_2_4.php
- http://www.trustix.org/errata/2007/0026/
- http://www.vupen.com/english/advisories/2007/3023
- http://lists.opensuse.org/opensuse-security-announce/2008-01/msg00006.html
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11147
- http://rhn.redhat.com/errata/RHSA-2007-0889.html
- http://secunia.com/advisories/26642
- http://secunia.com/advisories/26822
- http://secunia.com/advisories/26838
- http://secunia.com/advisories/26871
- http://secunia.com/advisories/26895
- http://secunia.com/advisories/26930
- http://secunia.com/advisories/26967
- http://secunia.com/advisories/27102
- http://secunia.com/advisories/27351
- http://secunia.com/advisories/27377
- http://secunia.com/advisories/27545
- http://secunia.com/advisories/28009
- http://secunia.com/advisories/28147
- http://secunia.com/advisories/28658
- http://secunia.com/advisories/31168
- http://www.ubuntu.com/usn/usn-557-1
- https://exchange.xforce.ibmcloud.com/vulnerabilities/36382
- https://exchange.xforce.ibmcloud.com/vulnerabilities/36383
- http://www.mandriva.com/security/advisories?name=MDKSA-2007:187
- http://www.redhat.com/support/errata/RHSA-2007-0888.html
- http://www.redhat.com/support/errata/RHSA-2007-0890.html
- http://www.redhat.com/support/errata/RHSA-2007-0891.html
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u5
Detailed paths
-
Introduced through: python@latest › openssh/openssh-client@1:9.2p1-2+deb12u5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh
package and not the openssh
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
sshd in OpenSSH 4 on Debian GNU/Linux, and the 20070303 OpenSSH snapshot, allows remote authenticated users to obtain access to arbitrary SELinux roles by appending a :/ (colon slash) sequence, followed by the role name, to the username.
Remediation
There is no fixed version for Debian:12
openssh
.
References
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
Detailed paths
-
Introduced through: python@latest › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: python@latest › shadow/passwd@1:4.13+dfsg1-1+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow
package and not the shadow
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
initscripts in rPath Linux 1 sets insecure permissions for the /var/log/btmp file, which allows local users to obtain sensitive information regarding authentication attempts. NOTE: because sshd detects the insecure permissions and does not log certain events, this also prevents sshd from logging failed authentication attempts by remote attackers.
Remediation
There is no fixed version for Debian:12
shadow
.
References
- https://security-tracker.debian.org/tracker/CVE-2007-5686
- http://www.securityfocus.com/archive/1/482129/100/100/threaded
- http://www.securityfocus.com/archive/1/482857/100/0/threaded
- https://issues.rpath.com/browse/RPL-1825
- http://secunia.com/advisories/27215
- http://www.securityfocus.com/bid/26048
- http://www.vupen.com/english/advisories/2007/3474
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6+deb12u2, tiff/libtiff6@4.5.0-6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › tiff/libtiff-dev@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiff6@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiffxx6@4.5.0-6+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff
package and not the tiff
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A flaw was found in tiffcrop, a program distributed by the libtiff package. A specially crafted tiff file can lead to an out-of-bounds read in the extractImageSection function in tools/tiffcrop.c, resulting in a denial of service and limited information disclosure. This issue affects libtiff versions 4.x.
Remediation
There is no fixed version for Debian:12
tiff
.
References
low severity
- Vulnerable module: wget
- Introduced through: wget@1.21.3-1+deb12u1
Detailed paths
-
Introduced through: python@latest › wget@1.21.3-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream wget
package and not the wget
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
GNU Wget through 1.21.1 does not omit the Authorization header upon a redirect to a different origin, a related issue to CVE-2018-1000007.
Remediation
There is no fixed version for Debian:12
wget
.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability classified as problematic was found in GNU Binutils 2.43/2.44. Affected by this vulnerability is the function bfd_set_format of the file format.c. The manipulation leads to memory corruption. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. Upgrading to version 2.45 is able to address this issue. The identifier of the patch is 8d97c1a53f3dc9fd8e1ccdb039b8a33d50133150. It is recommended to upgrade the affected component.
Remediation
There is no fixed version for Debian:12
binutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1153
- https://sourceware.org/bugzilla/show_bug.cgi?id=32603
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8d97c1a53f3dc9fd8e1ccdb039b8a33d50133150
- https://vuldb.com/?ctiid.295057
- https://vuldb.com/?id.295057
- https://vuldb.com/?submit.489991
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0005/
low severity
- Vulnerable module: dav1d/libdav1d6
- Introduced through: dav1d/libdav1d6@1.0.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › dav1d/libdav1d6@1.0.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream dav1d
package and not the dav1d
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
VideoLAN dav1d before 1.2.0 has a thread_task.c race condition that can lead to an application crash, related to dav1d_decode_frame_exit.
Remediation
There is no fixed version for Debian:12
dav1d
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-32570
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3WGSO7UMOF4MVLQ5H6KIV7OG6ONS377B/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LXZ6CUNJFDJLCFOZHY2TIGMCAEITLCRP/
- https://code.videolan.org/videolan/dav1d/-/commit/cf617fdae0b9bfabd27282854c8e81450d955efa
- https://code.videolan.org/videolan/dav1d/-/tags/1.2.0
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3WGSO7UMOF4MVLQ5H6KIV7OG6ONS377B/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LXZ6CUNJFDJLCFOZHY2TIGMCAEITLCRP/
- https://security.gentoo.org/glsa/202310-05
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u5
Detailed paths
-
Introduced through: python@latest › openssh/openssh-client@1:9.2p1-2+deb12u5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh
package and not the openssh
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The client side in OpenSSH 5.7 through 8.4 has an Observable Discrepancy leading to an information leak in the algorithm negotiation. This allows man-in-the-middle attackers to target initial connection attempts (where no host key for the server has been cached by the client). NOTE: some reports state that 8.5 and 8.6 are also affected.
Remediation
There is no fixed version for Debian:12
openssh
.
References
- https://security-tracker.debian.org/tracker/CVE-2020-14145
- https://security.netapp.com/advisory/ntap-20200709-0004/
- https://security.gentoo.org/glsa/202105-35
- https://anongit.mindrot.org/openssh.git/commit/?id=b3855ff053f5078ec3d3c653cdaedefaa5fc362d
- https://docs.ssh-mitm.at/CVE-2020-14145.html
- https://github.com/openssh/openssh-portable/compare/V_8_3_P1...V_8_4_P1
- https://github.com/ssh-mitm/ssh-mitm/blob/master/ssh_proxy_server/plugins/session/cve202014145.py
- https://www.fzi.de/en/news/news/detail-en/artikel/fsa-2020-2-ausnutzung-eines-informationslecks-fuer-gezielte-mitm-angriffe-auf-ssh-clients/
- http://www.openwall.com/lists/oss-security/2020/12/02/1
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been declared as problematic. Affected by this vulnerability is the function bfd_putl64 of the file libbfd.c of the component ld. The manipulation leads to memory corruption. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The identifier of the patch is 75086e9de1707281172cc77f178e7949a4414ed0. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12
binutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1178
- https://sourceware.org/bugzilla/attachment.cgi?id=15914
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=75086e9de1707281172cc77f178e7949a4414ed0
- https://vuldb.com/?ctiid.295081
- https://vuldb.com/?id.295081
- https://vuldb.com/?submit.495369
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250411-0008/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32638
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The C++ symbol demangler routine in cplus-dem.c in libiberty, as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (excessive memory allocation and application crash) via a crafted file, as demonstrated by a call from the Binary File Descriptor (BFD) library (aka libbfd).
Remediation
There is no fixed version for Debian:12
binutils
.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The demangle_template function in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.31.1, contains an integer overflow vulnerability (for "Create an array for saving the template argument values") that can trigger a heap-based buffer overflow, as demonstrated by nm.
Remediation
There is no fixed version for Debian:12
binutils
.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30. Stack Exhaustion occurs in the C++ demangling functions provided by libiberty, and there are recursive stack frames: demangle_template_value_parm, demangle_integral_value, and demangle_expression.
Remediation
There is no fixed version for Debian:12
binutils
.
References
low severity
- Vulnerable module: cairo/libcairo-gobject2
- Introduced through: cairo/libcairo-gobject2@1.16.0-7, cairo/libcairo-script-interpreter2@1.16.0-7 and others
Detailed paths
-
Introduced through: python@latest › cairo/libcairo-gobject2@1.16.0-7
-
Introduced through: python@latest › cairo/libcairo-script-interpreter2@1.16.0-7
-
Introduced through: python@latest › cairo/libcairo2@1.16.0-7
-
Introduced through: python@latest › cairo/libcairo2-dev@1.16.0-7
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream cairo
package and not the cairo
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Cairo version 1.15.4 is vulnerable to a NULL pointer dereference related to the FT_Load_Glyph and FT_Render_Glyph resulting in an application crash.
Remediation
There is no fixed version for Debian:12
cairo
.
References
- https://security-tracker.debian.org/tracker/CVE-2017-7475
- https://bugs.freedesktop.org/show_bug.cgi?id=100763
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://seclists.org/oss-sec/2017/q2/151
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-7475
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2017-7475
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1 and expat/libexpat1-dev@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@latest › expat/libexpat1@2.5.0-1+deb12u1
-
Introduced through: python@latest › expat/libexpat1-dev@2.5.0-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat
package and not the expat
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libexpat through 2.5.0 allows recursive XML Entity Expansion if XML_DTD is undefined at compile time.
Remediation
There is no fixed version for Debian:12
expat
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-52426
- https://cwe.mitre.org/data/definitions/776.html
- https://github.com/libexpat/libexpat/commit/0f075ec8ecb5e43f8fdca5182f8cca4703da0404
- https://github.com/libexpat/libexpat/pull/777
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WNUBSGZFEZOBHJFTAD42SAN4ATW2VEMV/
- https://security.netapp.com/advisory/ntap-20240307-0005/
low severity
- Vulnerable module: gcc-12
- Introduced through: gcc-12@12.2.0-14, gcc-12/cpp-12@12.2.0-14 and others
Detailed paths
-
Introduced through: python@latest › gcc-12@12.2.0-14
-
Introduced through: python@latest › gcc-12/cpp-12@12.2.0-14
-
Introduced through: python@latest › gcc-12/g++-12@12.2.0-14
-
Introduced through: python@latest › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: python@latest › gcc-12/libasan8@12.2.0-14
-
Introduced through: python@latest › gcc-12/libatomic1@12.2.0-14
-
Introduced through: python@latest › gcc-12/libcc1-0@12.2.0-14
-
Introduced through: python@latest › gcc-12/libgcc-12-dev@12.2.0-14
-
Introduced through: python@latest › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: python@latest › gcc-12/libgomp1@12.2.0-14
-
Introduced through: python@latest › gcc-12/libitm1@12.2.0-14
-
Introduced through: python@latest › gcc-12/liblsan0@12.2.0-14
-
Introduced through: python@latest › gcc-12/libquadmath0@12.2.0-14
-
Introduced through: python@latest › gcc-12/libstdc++-12-dev@12.2.0-14
-
Introduced through: python@latest › gcc-12/libstdc++6@12.2.0-14
-
Introduced through: python@latest › gcc-12/libtsan2@12.2.0-14
-
Introduced through: python@latest › gcc-12/libubsan1@12.2.0-14
…and 14 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-12
package and not the gcc-12
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by nm-new.
Remediation
There is no fixed version for Debian:12
gcc-12
.
References
- https://security-tracker.debian.org/tracker/CVE-2022-27943
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105039
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/H424YXGW7OKXS2NCAP35OP6Y4P4AW6VG/
- https://sourceware.org/bugzilla/show_bug.cgi?id=28995
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/H424YXGW7OKXS2NCAP35OP6Y4P4AW6VG/
low severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6+deb12u2
…and 10 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick
package and not the imagemagick
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A design flaw in image processing software that modifies JPEG images might not modify the original EXIF thumbnail, which could lead to an information leak of potentially sensitive visual information that had been removed from the main JPEG image.
Remediation
There is no fixed version for Debian:12
imagemagick
.
References
low severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6+deb12u2
…and 10 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick
package and not the imagemagick
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The ReadPCXImage function in coders/pcx.c in ImageMagick 7.0.4.9 allows remote attackers to cause a denial of service (attempted large memory allocation and application crash) via a crafted file. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-8862 and CVE-2016-8866.
Remediation
There is no fixed version for Debian:12
imagemagick
.
References
- https://security-tracker.debian.org/tracker/CVE-2017-7275
- https://github.com/ImageMagick/ImageMagick/issues/271
- https://blogs.gentoo.org/ago/2017/03/27/imagemagick-memory-allocation-failure-in-acquiremagickmemory-memory-c-incomplete-fix-for-cve-2016-8862-and-cve-2016-8866/
- http://www.securityfocus.com/bid/97166
low severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6+deb12u2
…and 10 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick
package and not the imagemagick
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The IsPixelMonochrome function in MagickCore/pixel-accessor.h in ImageMagick 7.0.3.0 allows remote attackers to cause a denial of service (out-of-bounds read and crash) via a crafted file. NOTE: the vendor says "This is a Q64 issue and we do not support Q64."
Remediation
There is no fixed version for Debian:12
imagemagick
.
References
- https://security-tracker.debian.org/tracker/CVE-2016-8678
- https://github.com/ImageMagick/ImageMagick/issues/272
- http://www.openwall.com/lists/oss-security/2016/10/16/2
- http://www.openwall.com/lists/oss-security/2016/12/08/18
- https://bugzilla.redhat.com/show_bug.cgi?id=1385694
- http://www.securityfocus.com/bid/93599
low severity
- Vulnerable module: krb5/krb5-multidev
- Introduced through: krb5/krb5-multidev@1.20.1-2+deb12u2, krb5/libgssapi-krb5-2@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › krb5/krb5-multidev@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libgssrpc4@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkadm5clnt-mit12@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkadm5srv-mit12@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkdb5-10@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5-dev@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5support0@1.20.1-2+deb12u2
…and 7 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5
package and not the krb5
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/kdc/ndr.c.
Remediation
There is no fixed version for Debian:12
krb5
.
References
low severity
- Vulnerable module: libpng1.6/libpng-dev
- Introduced through: libpng1.6/libpng-dev@1.6.39-2 and libpng1.6/libpng16-16@1.6.39-2
Detailed paths
-
Introduced through: python@latest › libpng1.6/libpng-dev@1.6.39-2
-
Introduced through: python@latest › libpng1.6/libpng16-16@1.6.39-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6
package and not the libpng1.6
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A heap overflow flaw was found in libpngs' pngimage.c program. This flaw allows an attacker with local network access to pass a specially crafted PNG file to the pngimage utility, causing an application to crash, leading to a denial of service.
Remediation
There is no fixed version for Debian:12
libpng1.6
.
References
low severity
- Vulnerable module: openexr/libopenexr-3-1-30
- Introduced through: openexr/libopenexr-3-1-30@3.1.5-5 and openexr/libopenexr-dev@3.1.5-5
Detailed paths
-
Introduced through: python@latest › openexr/libopenexr-3-1-30@3.1.5-5
-
Introduced through: python@latest › openexr/libopenexr-dev@3.1.5-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openexr
package and not the openexr
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Header::readfrom in IlmImf/ImfHeader.cpp in OpenEXR 2.2.0 allows remote attackers to cause a denial of service (excessive memory allocation) via a crafted file that is accessed with the ImfOpenInputFile function in IlmImf/ImfCRgbaFile.cpp. NOTE: The maintainer and multiple third parties believe that this vulnerability isn't valid
Remediation
There is no fixed version for Debian:12
openexr
.
References
low severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u1, pam/libpam-modules-bin@1.5.2-6+deb12u1 and others
Detailed paths
-
Introduced through: python@latest › pam/libpam-modules@1.5.2-6+deb12u1
-
Introduced through: python@latest › pam/libpam-modules-bin@1.5.2-6+deb12u1
-
Introduced through: python@latest › pam/libpam-runtime@1.5.2-6+deb12u1
-
Introduced through: python@latest › pam/libpam0g@1.5.2-6+deb12u1
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream pam
package and not the pam
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
linux-pam (aka Linux PAM) before 1.6.0 allows attackers to cause a denial of service (blocked login process) via mkfifo because the openat call (for protect_dir) lacks O_DIRECTORY.
Remediation
There is no fixed version for Debian:12
pam
.
References
low severity
- Vulnerable module: patch
- Introduced through: patch@2.7.6-7
Detailed paths
-
Introduced through: python@latest › patch@2.7.6-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream patch
package and not the patch
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An Invalid Pointer vulnerability exists in GNU patch 2.7 via the another_hunk function, which causes a Denial of Service.
Remediation
There is no fixed version for Debian:12
patch
.
References
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
Detailed paths
-
Introduced through: python@latest › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: python@latest › shadow/passwd@1:4.13+dfsg1-1+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow
package and not the shadow
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A flaw was found in shadow-utils. When asking for a new password, shadow-utils asks the password twice. If the password fails on the second attempt, shadow-utils fails in cleaning the buffer used to store the first entry. This may allow an attacker with enough access to retrieve the password from the memory.
Remediation
There is no fixed version for Debian:12
shadow
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4641
- https://access.redhat.com/errata/RHSA-2023:6632
- https://access.redhat.com/errata/RHSA-2023:7112
- https://access.redhat.com/errata/RHSA-2024:0417
- https://access.redhat.com/errata/RHSA-2024:2577
- https://access.redhat.com/security/cve/CVE-2023-4641
- https://bugzilla.redhat.com/show_bug.cgi?id=2215945
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6+deb12u2, tiff/libtiff6@4.5.0-6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › tiff/libtiff-dev@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiff6@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiffxx6@4.5.0-6+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff
package and not the tiff
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A heap-buffer-overflow vulnerability was found in LibTIFF, in extractImageSection() at tools/tiffcrop.c:7916 and tools/tiffcrop.c:7801. This flaw allows attackers to cause a denial of service via a crafted tiff file.
Remediation
There is no fixed version for Debian:12
tiff
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-3164
- https://access.redhat.com/security/cve/CVE-2023-4156
- https://bugzilla.redhat.com/show_bug.cgi?id=2215930
- https://access.redhat.com/security/cve/CVE-2023-3164
- https://bugzilla.redhat.com/show_bug.cgi?id=2213531
- https://gitlab.com/libtiff/libtiff/-/issues/542
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.38.1-5+deb12u3, util-linux/bsdutils@1:2.38.1-5+deb12u3 and others
Detailed paths
-
Introduced through: python@latest › util-linux@2.38.1-5+deb12u3
-
Introduced through: python@latest › util-linux/bsdutils@1:2.38.1-5+deb12u3
-
Introduced through: python@latest › util-linux/libblkid-dev@2.38.1-5+deb12u3
-
Introduced through: python@latest › util-linux/libblkid1@2.38.1-5+deb12u3
-
Introduced through: python@latest › util-linux/libmount-dev@2.38.1-5+deb12u3
-
Introduced through: python@latest › util-linux/libmount1@2.38.1-5+deb12u3
-
Introduced through: python@latest › util-linux/libsmartcols1@2.38.1-5+deb12u3
-
Introduced through: python@latest › util-linux/libuuid1@2.38.1-5+deb12u3
-
Introduced through: python@latest › util-linux/mount@2.38.1-5+deb12u3
-
Introduced through: python@latest › util-linux/util-linux-extra@2.38.1-5+deb12u3
-
Introduced through: python@latest › util-linux/uuid-dev@2.38.1-5+deb12u3
…and 8 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream util-linux
package and not the util-linux
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4.
Remediation
There is no fixed version for Debian:12
util-linux
.
References
- https://security-tracker.debian.org/tracker/CVE-2022-0563
- https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w@ws.net.home/T/#u
- https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w%40ws.net.home/T/#u
- https://security.gentoo.org/glsa/202401-08
- https://security.netapp.com/advisory/ntap-20220331-0002/
low severity
- Vulnerable module: patch
- Introduced through: patch@2.7.6-7
Detailed paths
-
Introduced through: python@latest › patch@2.7.6-7
NVD Description
Note: Versions mentioned in the description apply only to the upstream patch
package and not the patch
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Directory traversal vulnerability in util.c in GNU patch 2.6.1 and earlier allows user-assisted remote attackers to create or overwrite arbitrary files via a filename that is specified with a .. (dot dot) or full pathname, a related issue to CVE-2010-1679.
Remediation
There is no fixed version for Debian:12
patch
.
References
- https://security-tracker.debian.org/tracker/CVE-2010-4651
- http://support.apple.com/kb/HT4723
- http://lists.apple.com/archives/security-announce/2011//Jun/msg00000.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-March/055241.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-March/055246.html
- http://git.savannah.gnu.org/cgit/patch.git/commit/?id=685a78b6052f4df6eac6d625a545cfb54a6ac0e1
- http://lists.gnu.org/archive/html/bug-patch/2010-12/msg00000.html
- http://www.vupen.com/english/advisories/2011/0600
- http://openwall.com/lists/oss-security/2011/01/05/10
- http://openwall.com/lists/oss-security/2011/01/06/19
- http://openwall.com/lists/oss-security/2011/01/06/20
- http://openwall.com/lists/oss-security/2011/01/06/21
- https://bugzilla.redhat.com/show_bug.cgi?id=667529
- http://secunia.com/advisories/43663
- http://secunia.com/advisories/43677
- http://www.securityfocus.com/bid/46768
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2010-4651
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.43 and classified as problematic. Affected by this vulnerability is the function __sanitizer::internal_strlen of the file binutils/nm.c of the component nm. The manipulation of the argument const leads to buffer overflow. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used.
Remediation
There is no fixed version for Debian:12
binutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1147
- https://sourceware.org/bugzilla/attachment.cgi?id=15881
- https://sourceware.org/bugzilla/show_bug.cgi?id=32556
- https://vuldb.com/?ctiid.295051
- https://vuldb.com/?id.295051
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0003/
- https://vuldb.com/?submit.485254
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In BlueZ 5.42, a buffer overflow was observed in "pklg_read_hci" function in "btsnoop.c" source file. This issue can be triggered by processing a corrupted dump file and will result in btmon crash.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In BlueZ 5.42, a buffer overflow was observed in "set_ext_ctrl" function in "tools/parser/l2cap.c" source file when processing corrupted dump file.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In BlueZ 5.42, a buffer overflow was observed in "commands_dump" function in "tools/parser/csr.c" source file. The issue exists because "commands" array is overflowed by supplied parameter due to lack of boundary checks on size of the buffer from frame "frm->ptr" parameter. This issue can be triggered by processing a corrupted dump file and will result in hcidump crash.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In BlueZ 5.42, an out-of-bounds read was observed in "le_meta_ev_dump" function in "tools/parser/hci.c" source file. This issue exists because 'subevent' (which is used to read correct element from 'ev_le_meta_str' array) is overflowed.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In BlueZ 5.42, a buffer over-read was identified in "l2cap_packet" function in "monitor/packet.c" source file. This issue can be triggered by processing a corrupted dump file and will result in btmon crash.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In BlueZ 5.42, a buffer overflow was observed in "pin_code_reply_dump" function in "tools/parser/hci.c" source file. The issue exists because "pin" array is overflowed by supplied parameter due to lack of boundary checks on size of the buffer from frame "pin_code_reply_cp *cp" parameter.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In BlueZ 5.42, a buffer over-read was observed in "l2cap_dump" function in "tools/parser/l2cap.c" source file. This issue can be triggered by processing a corrupted dump file and will result in hcidump crash.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In BlueZ 5.42, a use-after-free was identified in "conf_opt" function in "tools/parser/l2cap.c" source file. This issue can be triggered by processing a corrupted dump file and will result in hcidump crash.
Remediation
There is no fixed version for Debian:12
bluez
.
References
- https://security-tracker.debian.org/tracker/CVE-2016-9798
- https://www.spinics.net/lists/linux-bluetooth/msg68892.html
- http://lists.opensuse.org/opensuse-security-announce/2019-05/msg00069.html
- http://www.securityfocus.com/bid/94652
- http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00071.html
- http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00072.html
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2016-9798
low severity
- Vulnerable module: elfutils/libelf1
- Introduced through: elfutils/libelf1@0.188-2.1
Detailed paths
-
Introduced through: python@latest › elfutils/libelf1@0.188-2.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream elfutils
package and not the elfutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability, which was classified as critical, was found in GNU elfutils 0.192. This affects the function process_symtab of the file readelf.c of the component eu-readelf. The manipulation of the argument D/a leads to buffer overflow. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The identifier of the patch is 5e5c0394d82c53e97750fe7b18023e6f84157b81. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12
elfutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1365
- https://sourceware.org/bugzilla/attachment.cgi?id=15925
- https://sourceware.org/bugzilla/show_bug.cgi?id=32654
- https://sourceware.org/bugzilla/show_bug.cgi?id=32654#c2
- https://vuldb.com/?ctiid.295977
- https://vuldb.com/?id.295977
- https://vuldb.com/?submit.496483
- https://www.gnu.org/
low severity
- Vulnerable module: elfutils/libelf1
- Introduced through: elfutils/libelf1@0.188-2.1
Detailed paths
-
Introduced through: python@latest › elfutils/libelf1@0.188-2.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream elfutils
package and not the elfutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability was found in GNU elfutils 0.192. It has been declared as critical. Affected by this vulnerability is the function dump_data_section/print_string_section of the file readelf.c of the component eu-readelf. The manipulation of the argument z/x leads to buffer overflow. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The identifier of the patch is 73db9d2021cab9e23fd734b0a76a612d52a6f1db. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12
elfutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1372
- https://sourceware.org/bugzilla/attachment.cgi?id=15927
- https://sourceware.org/bugzilla/show_bug.cgi?id=32656
- https://sourceware.org/bugzilla/show_bug.cgi?id=32656#c3
- https://sourceware.org/bugzilla/show_bug.cgi?id=32657
- https://vuldb.com/?ctiid.295981
- https://vuldb.com/?id.295981
- https://vuldb.com/?submit.496485
- https://www.gnu.org/
low severity
- Vulnerable module: glib2.0/libglib2.0-0
- Introduced through: glib2.0/libglib2.0-0@2.74.6-2+deb12u5, glib2.0/libglib2.0-bin@2.74.6-2+deb12u5 and others
Detailed paths
-
Introduced through: python@latest › glib2.0/libglib2.0-0@2.74.6-2+deb12u5
-
Introduced through: python@latest › glib2.0/libglib2.0-bin@2.74.6-2+deb12u5
-
Introduced through: python@latest › glib2.0/libglib2.0-data@2.74.6-2+deb12u5
-
Introduced through: python@latest › glib2.0/libglib2.0-dev@2.74.6-2+deb12u5
-
Introduced through: python@latest › glib2.0/libglib2.0-dev-bin@2.74.6-2+deb12u5
…and 2 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream glib2.0
package and not the glib2.0
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
GLib 2.31.8 and earlier, when the g_str_hash function is used, computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. NOTE: this issue may be disputed by the vendor; the existence of the g_str_hash function is not a vulnerability in the library, because callers of g_hash_table_new and g_hash_table_new_full can specify an arbitrary hash function that is appropriate for the application.
Remediation
There is no fixed version for Debian:12
glib2.0
.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u10, glibc/libc-dev-bin@2.36-9+deb12u10 and others
Detailed paths
-
Introduced through: python@latest › glibc/libc-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc-dev-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6-dev@2.36-9+deb12u10
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc
package and not the glibc
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
Remediation
There is no fixed version for Debian:12
glibc
.
References
- https://security-tracker.debian.org/tracker/CVE-2019-1010024
- https://support.f5.com/csp/article/K06046097
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22852
- http://www.securityfocus.com/bid/109162
- https://ubuntu.com/security/CVE-2019-1010024
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u10, glibc/libc-dev-bin@2.36-9+deb12u10 and others
Detailed paths
-
Introduced through: python@latest › glibc/libc-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc-dev-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6-dev@2.36-9+deb12u10
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc
package and not the glibc
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may guess the heap addresses of pthread_created thread. The component is: glibc. NOTE: the vendor's position is "ASLR bypass itself is not a vulnerability.
Remediation
There is no fixed version for Debian:12
glibc
.
References
- https://security-tracker.debian.org/tracker/CVE-2019-1010025
- https://support.f5.com/csp/article/K06046097
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22853
- https://ubuntu.com/security/CVE-2019-1010025
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6+deb12u2
…and 10 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick
package and not the imagemagick
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Multiple unspecified vulnerabilities in GraphicsMagick before 1.2.4 allow remote attackers to cause a denial of service (crash, infinite loop, or memory consumption) via (a) unspecified vectors in the (1) AVI, (2) AVS, (3) DCM, (4) EPT, (5) FITS, (6) MTV, (7) PALM, (8) RLA, and (9) TGA decoder readers; and (b) the GetImageCharacteristics function in magick/image.c, as reachable from a crafted (10) PNG, (11) JPEG, (12) BMP, or (13) TIFF file.
Remediation
There is no fixed version for Debian:12
imagemagick
.
References
- https://security-tracker.debian.org/tracker/CVE-2008-3134
- http://sourceforge.net/forum/forum.php?forum_id=841176
- http://sourceforge.net/project/shownotes.php?release_id=610253
- http://www.vupen.com/english/advisories/2008/1984/references
- http://xforce.iss.net/xforce/xfdb/43511
- http://xforce.iss.net/xforce/xfdb/43513
- http://lists.opensuse.org/opensuse-security-announce/2008-10/msg00004.html
- http://secunia.com/advisories/30879
- http://secunia.com/advisories/32151
- http://www.securityfocus.com/bid/30055
- http://www.securitytracker.com/id?1020413
- https://exchange.xforce.ibmcloud.com/vulnerabilities/43511
- https://exchange.xforce.ibmcloud.com/vulnerabilities/43513
low severity
- Vulnerable module: libwmf/libwmf-0.2-7
- Introduced through: libwmf/libwmf-0.2-7@0.2.12-5.1, libwmf/libwmf-dev@0.2.12-5.1 and others
Detailed paths
-
Introduced through: python@latest › libwmf/libwmf-0.2-7@0.2.12-5.1
-
Introduced through: python@latest › libwmf/libwmf-dev@0.2.12-5.1
-
Introduced through: python@latest › libwmf/libwmflite-0.2-7@0.2.12-5.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libwmf
package and not the libwmf
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The (a) imagearc and (b) imagefilledarc functions in GD Graphics Library (libgd) before 2.0.35 allow attackers to cause a denial of service (CPU consumption) via a large (1) start or (2) end angle degree value.
Remediation
There is no fixed version for Debian:12
libwmf
.
References
- https://security-tracker.debian.org/tracker/CVE-2007-3477
- http://www.securityfocus.com/archive/1/478796/100/0/threaded
- ftp://ftp.slackware.com/pub/slackware/slackware-11.0/patches/packages/gd-2.0.35-i486-1_slack11.0.tgz
- http://bugs.libgd.org/?do=details&task_id=74
- http://bugs.libgd.org/?do=details&task_id=92
- https://issues.rpath.com/browse/RPL-1643
- http://www.debian.org/security/2008/dsa-1613
- http://fedoranews.org/updates/FEDORA-2007-205.shtml
- http://www.redhat.com/archives/fedora-package-announce/2007-September/msg00311.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-January/052848.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-January/052854.html
- http://security.gentoo.org/glsa/glsa-200708-05.xml
- http://security.gentoo.org/glsa/glsa-200711-34.xml
- http://security.gentoo.org/glsa/glsa-200805-13.xml
- http://www.libgd.org/ReleaseNote020035
- http://osvdb.org/42062
- https://bugzilla.redhat.com/show_bug.cgi?id=277421
- http://secunia.com/advisories/25860
- http://secunia.com/advisories/26272
- http://secunia.com/advisories/26390
- http://secunia.com/advisories/26415
- http://secunia.com/advisories/26467
- http://secunia.com/advisories/26663
- http://secunia.com/advisories/26766
- http://secunia.com/advisories/26856
- http://secunia.com/advisories/30168
- http://secunia.com/advisories/31168
- http://secunia.com/advisories/42813
- http://www.securityfocus.com/bid/24651
- http://www.novell.com/linux/security/advisories/2007_15_sr.html
- http://www.trustix.org/errata/2007/0024/
- http://www.vupen.com/english/advisories/2011/0022
- http://www.mandriva.com/security/advisories?name=MDKSA-2007:153
- http://www.mandriva.com/security/advisories?name=MDKSA-2007:164
low severity
- Vulnerable module: libxslt/libxslt1-dev
- Introduced through: libxslt/libxslt1-dev@1.1.35-1+deb12u1 and libxslt/libxslt1.1@1.1.35-1+deb12u1
Detailed paths
-
Introduced through: python@latest › libxslt/libxslt1-dev@1.1.35-1+deb12u1
-
Introduced through: python@latest › libxslt/libxslt1.1@1.1.35-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxslt
package and not the libxslt
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In libxslt 1.1.29 and earlier, the EXSLT math.random function was not initialized with a random seed during startup, which could cause usage of this function to produce predictable outputs.
Remediation
There is no fixed version for Debian:12
libxslt
.
References
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u5
Detailed paths
-
Introduced through: python@latest › openssh/openssh-client@1:9.2p1-2+deb12u5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh
package and not the openssh
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
OpenSSH through 8.7 allows remote attackers, who have a suspicion that a certain combination of username and public key is known to an SSH server, to test whether this suspicion is correct. This occurs because a challenge is sent only when that combination could be valid for a login session. NOTE: the vendor does not recognize user enumeration as a vulnerability for this product
Remediation
There is no fixed version for Debian:12
openssh
.
References
- https://security-tracker.debian.org/tracker/CVE-2016-20012
- https://security.netapp.com/advisory/ntap-20211014-0005/
- https://github.com/openssh/openssh-portable/blob/d0fffc88c8fe90c1815c6f4097bc8cbcabc0f3dd/auth2-pubkey.c#L261-L265
- https://github.com/openssh/openssh-portable/pull/270
- https://rushter.com/blog/public-ssh-keys/
- https://utcc.utoronto.ca/~cks/space/blog/tech/SSHKeysAreInfoLeak
- https://github.com/openssh/openssh-portable/pull/270#issuecomment-920577097
- https://github.com/openssh/openssh-portable/pull/270#issuecomment-943909185
- https://www.openwall.com/lists/oss-security/2018/08/24/1
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u5
Detailed paths
-
Introduced through: python@latest › openssh/openssh-client@1:9.2p1-2+deb12u5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh
package and not the openssh
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
OpenSSH 4.6 and earlier, when ChallengeResponseAuthentication is enabled, allows remote attackers to determine the existence of user accounts by attempting to authenticate via S/KEY, which displays a different response if the user account exists, a similar issue to CVE-2001-1483.
Remediation
There is no fixed version for Debian:12
openssh
.
References
- https://security-tracker.debian.org/tracker/CVE-2007-2243
- https://security.netapp.com/advisory/ntap-20191107-0003/
- http://lists.grok.org.uk/pipermail/full-disclosure/2007-April/053906.html
- http://lists.grok.org.uk/pipermail/full-disclosure/2007-April/053951.html
- http://securityreason.com/securityalert/2631
- http://www.securityfocus.com/bid/23601
- https://exchange.xforce.ibmcloud.com/vulnerabilities/33794
- http://www.osvdb.org/34600
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u5
Detailed paths
-
Introduced through: python@latest › openssh/openssh-client@1:9.2p1-2+deb12u5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh
package and not the openssh
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Remotely observable behaviour in auth-gss2.c in OpenSSH through 7.8 could be used by remote attackers to detect existence of users on a target system when GSS2 is in use. NOTE: the discoverer states 'We understand that the OpenSSH developers do not want to treat such a username enumeration (or "oracle") as a vulnerability.'
Remediation
There is no fixed version for Debian:12
openssh
.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.36-1~deb12u1 and systemd/libudev1@252.36-1~deb12u1
Detailed paths
-
Introduced through: python@latest › systemd/libsystemd0@252.36-1~deb12u1
-
Introduced through: python@latest › systemd/libudev1@252.36-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd
package and not the systemd
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in systemd 253. An attacker can modify a sealed log file such that, in some views, not all existing and sealed log messages are displayed. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."
Remediation
There is no fixed version for Debian:12
systemd
.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.36-1~deb12u1 and systemd/libudev1@252.36-1~deb12u1
Detailed paths
-
Introduced through: python@latest › systemd/libsystemd0@252.36-1~deb12u1
-
Introduced through: python@latest › systemd/libudev1@252.36-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd
package and not the systemd
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."
Remediation
There is no fixed version for Debian:12
systemd
.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.36-1~deb12u1 and systemd/libudev1@252.36-1~deb12u1
Detailed paths
-
Introduced through: python@latest › systemd/libsystemd0@252.36-1~deb12u1
-
Introduced through: python@latest › systemd/libudev1@252.36-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd
package and not the systemd
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."
Remediation
There is no fixed version for Debian:12
systemd
.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability classified as critical was found in GNU Binutils 2.43. This vulnerability affects the function _bfd_elf_gc_mark_rsec of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is 931494c9a89558acb36a03a340c01726545eef24. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12
binutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1181
- https://sourceware.org/bugzilla/attachment.cgi?id=15918
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=931494c9a89558acb36a03a340c01726545eef24
- https://vuldb.com/?ctiid.295084
- https://vuldb.com/?id.295084
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250425-0007/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32643
- https://vuldb.com/?submit.495402
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43 and classified as critical. This issue affects the function _bfd_elf_gc_mark_rsec of the file elflink.c of the component ld. The manipulation leads to heap-based buffer overflow. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The patch is named f9978defb6fab0bd8583942d97c112b0932ac814. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12
binutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1176
- https://sourceware.org/bugzilla/attachment.cgi?id=15913
- https://sourceware.org/bugzilla/show_bug.cgi?id=32636
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f9978defb6fab0bd8583942d97c112b0932ac814
- https://vuldb.com/?ctiid.295079
- https://vuldb.com/?id.295079
- https://vuldb.com/?submit.495329
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250411-0007/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability, which was classified as critical, was found in GNU Binutils 2.43. Affected is the function bfd_elf_reloc_symbol_deleted_p of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The patch is identified as b425859021d17adf62f06fb904797cf8642986ad. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12
binutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1182
- https://sourceware.org/bugzilla/attachment.cgi?id=15919
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b425859021d17adf62f06fb904797cf8642986ad
- https://vuldb.com/?ctiid.295086
- https://vuldb.com/?id.295086
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32644
- https://vuldb.com/?submit.495407
low severity
- Vulnerable module: elfutils/libelf1
- Introduced through: elfutils/libelf1@0.188-2.1
Detailed paths
-
Introduced through: python@latest › elfutils/libelf1@0.188-2.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream elfutils
package and not the elfutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability has been found in GNU elfutils 0.192 and classified as critical. This vulnerability affects the function __libdw_thread_tail in the library libdw_alloc.c of the component eu-readelf. The manipulation of the argument w leads to memory corruption. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is 2636426a091bd6c6f7f02e49ab20d4cdc6bfc753. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12
elfutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1352
- https://sourceware.org/bugzilla/attachment.cgi?id=15923
- https://sourceware.org/bugzilla/show_bug.cgi?id=32650
- https://sourceware.org/bugzilla/show_bug.cgi?id=32650#c2
- https://vuldb.com/?ctiid.295960
- https://vuldb.com/?id.295960
- https://vuldb.com/?submit.495965
- https://www.gnu.org/
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.5-0+deb12u2 and git/git-man@1:2.39.5-0+deb12u2
Detailed paths
-
Introduced through: python@latest › git@1:2.39.5-0+deb12u2
-
Introduced through: python@latest › git/git-man@1:2.39.5-0+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream git
package and not the git
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
GIT version 2.15.1 and earlier contains a Input Validation Error vulnerability in Client that can result in problems including messing up terminal configuration to RCE. This attack appear to be exploitable via The user must interact with a malicious git server, (or have their traffic modified in a MITM attack).
Remediation
There is no fixed version for Debian:12
git
.
References
low severity
- Vulnerable module: gcc-12
- Introduced through: gcc-12@12.2.0-14, gcc-12/cpp-12@12.2.0-14 and others
Detailed paths
-
Introduced through: python@latest › gcc-12@12.2.0-14
-
Introduced through: python@latest › gcc-12/cpp-12@12.2.0-14
-
Introduced through: python@latest › gcc-12/g++-12@12.2.0-14
-
Introduced through: python@latest › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: python@latest › gcc-12/libasan8@12.2.0-14
-
Introduced through: python@latest › gcc-12/libatomic1@12.2.0-14
-
Introduced through: python@latest › gcc-12/libcc1-0@12.2.0-14
-
Introduced through: python@latest › gcc-12/libgcc-12-dev@12.2.0-14
-
Introduced through: python@latest › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: python@latest › gcc-12/libgomp1@12.2.0-14
-
Introduced through: python@latest › gcc-12/libitm1@12.2.0-14
-
Introduced through: python@latest › gcc-12/liblsan0@12.2.0-14
-
Introduced through: python@latest › gcc-12/libquadmath0@12.2.0-14
-
Introduced through: python@latest › gcc-12/libstdc++-12-dev@12.2.0-14
-
Introduced through: python@latest › gcc-12/libstdc++6@12.2.0-14
-
Introduced through: python@latest › gcc-12/libtsan2@12.2.0-14
-
Introduced through: python@latest › gcc-12/libubsan1@12.2.0-14
…and 14 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-12
package and not the gcc-12
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
DISPUTEDA failure in the -fstack-protector feature in GCC-based toolchains that target AArch64 allows an attacker to exploit an existing buffer overflow in dynamically-sized local variables in your application without this being detected. This stack-protector failure only applies to C99-style dynamically-sized local variables or those created using alloca(). The stack-protector operates as intended for statically-sized local variables.
The default behavior when the stack-protector detects an overflow is to terminate your application, resulting in controlled loss of availability. An attacker who can exploit a buffer overflow without triggering the stack-protector might be able to change program flow control to cause an uncontrolled loss of availability or to go further and affect confidentiality or integrity. NOTE: The GCC project argues that this is a missed hardening bug and not a vulnerability by itself.
Remediation
There is no fixed version for Debian:12
gcc-12
.
References
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: python@latest › coreutils@9.1-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream coreutils
package and not the coreutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.
Remediation
There is no fixed version for Debian:12
coreutils
.
References
low severity
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: python@latest › openldap/libldap-2.5-0@2.5.13+dfsg-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap
package and not the openldap
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill cat /pathname
" command, as demonstrated by openldap-initscript.
Remediation
There is no fixed version for Debian:12
openldap
.
References
low severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u1, pam/libpam-modules-bin@1.5.2-6+deb12u1 and others
Detailed paths
-
Introduced through: python@latest › pam/libpam-modules@1.5.2-6+deb12u1
-
Introduced through: python@latest › pam/libpam-modules-bin@1.5.2-6+deb12u1
-
Introduced through: python@latest › pam/libpam-runtime@1.5.2-6+deb12u1
-
Introduced through: python@latest › pam/libpam0g@1.5.2-6+deb12u1
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream pam
package and not the pam
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.
Remediation
There is no fixed version for Debian:12
pam
.
References
- https://security-tracker.debian.org/tracker/CVE-2024-10041
- https://access.redhat.com/security/cve/CVE-2024-10041
- https://bugzilla.redhat.com/show_bug.cgi?id=2319212
- https://access.redhat.com/errata/RHSA-2024:9941
- https://access.redhat.com/errata/RHSA-2024:10379
- https://access.redhat.com/errata/RHSA-2024:11250
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.36-1~deb12u1 and systemd/libudev1@252.36-1~deb12u1
Detailed paths
-
Introduced through: python@latest › systemd/libsystemd0@252.36-1~deb12u1
-
Introduced through: python@latest › systemd/libudev1@252.36-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd
package and not the systemd
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.
Remediation
There is no fixed version for Debian:12
systemd
.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u10, glibc/libc-dev-bin@2.36-9+deb12u10 and others
Detailed paths
-
Introduced through: python@latest › glibc/libc-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc-dev-bin@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6@2.36-9+deb12u10
-
Introduced through: python@latest › glibc/libc6-dev@2.36-9+deb12u10
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc
package and not the glibc
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The glob implementation in the GNU C Library (aka glibc or libc6) allows remote authenticated users to cause a denial of service (CPU and memory consumption) via crafted glob expressions that do not match any pathnames, as demonstrated by glob expressions in STAT commands to an FTP daemon, a different vulnerability than CVE-2010-2632.
Remediation
There is no fixed version for Debian:12
glibc
.
References
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u4
Detailed paths
-
Introduced through: python@latest › gnutls28/libgnutls30@3.7.9-2+deb12u4
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28
package and not the gnutls28
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.
Remediation
There is no fixed version for Debian:12
gnutls28
.
References
- https://security-tracker.debian.org/tracker/CVE-2011-3389
- http://lists.apple.com/archives/Security-announce/2011//Oct/msg00001.html
- http://lists.apple.com/archives/Security-announce/2011//Oct/msg00002.html
- http://support.apple.com/kb/HT4999
- http://support.apple.com/kb/HT5001
- http://support.apple.com/kb/HT5130
- http://support.apple.com/kb/HT5281
- http://support.apple.com/kb/HT5501
- http://support.apple.com/kb/HT6150
- http://lists.apple.com/archives/security-announce/2012/Feb/msg00000.html
- http://lists.apple.com/archives/security-announce/2012/Jul/msg00001.html
- http://lists.apple.com/archives/security-announce/2012/May/msg00001.html
- http://lists.apple.com/archives/security-announce/2012/Sep/msg00004.html
- http://lists.apple.com/archives/security-announce/2013/Oct/msg00004.html
- http://www.us-cert.gov/cas/techalerts/TA12-010A.html
- http://www.kb.cert.org/vuls/id/864643
- http://googlechromereleases.blogspot.com/2011/10/chrome-stable-release.html
- http://blog.mozilla.com/security/2011/09/27/attack-against-tls-protected-communications/
- http://blogs.technet.com/b/msrc/archive/2011/09/26/microsoft-releases-security-advisory-2588513.aspx
- http://blogs.technet.com/b/srd/archive/2011/09/26/is-ssl-broken-more-about-security-advisory-2588513.aspx
- http://curl.haxx.se/docs/adv_20120124B.html
- http://downloads.asterisk.org/pub/security/AST-2016-001.html
- http://my.opera.com/securitygroup/blog/2011/09/28/the-beast-ssl-tls-issue
- https://blogs.oracle.com/sunsecurity/entry/multiple_vulnerabilities_in_fetchmail
- https://bugzilla.novell.com/show_bug.cgi?id=719047
- https://cert-portal.siemens.com/productcert/pdf/ssa-556833.pdf
- http://technet.microsoft.com/security/advisory/2588513
- http://www.apcmedia.com/salestools/SJHN-7RKGNM/SJHN-7RKGNM_R4_EN.pdf
- http://www.ibm.com/developerworks/java/jdk/alerts/
- http://www.imperialviolet.org/2011/09/23/chromeandbeast.html
- http://www.opera.com/docs/changelogs/mac/1151/
- http://www.opera.com/docs/changelogs/mac/1160/
- http://www.opera.com/docs/changelogs/unix/1151/
- http://www.opera.com/docs/changelogs/unix/1160/
- http://www.opera.com/docs/changelogs/windows/1151/
- http://www.opera.com/docs/changelogs/windows/1160/
- http://www.opera.com/support/kb/view/1004/
- http://www.debian.org/security/2012/dsa-2398
- http://security.gentoo.org/glsa/glsa-201203-02.xml
- http://security.gentoo.org/glsa/glsa-201406-32.xml
- https://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c03839862
- http://marc.info/?l=bugtraq&m=132750579901589&w=2
- http://marc.info/?l=bugtraq&m=132872385320240&w=2
- http://marc.info/?l=bugtraq&m=133365109612558&w=2
- http://marc.info/?l=bugtraq&m=133728004526190&w=2
- http://marc.info/?l=bugtraq&m=134254866602253&w=2
- http://marc.info/?l=bugtraq&m=134254957702612&w=2
- http://ekoparty.org/2011/juliano-rizzo.php
- http://eprint.iacr.org/2004/111
- http://eprint.iacr.org/2006/136
- http://isc.sans.edu/diary/SSL+TLS+part+3+/11635
- https://ics-cert.us-cert.gov/advisories/ICSMA-18-058-02
- http://vnhacker.blogspot.com/2011/09/beast.html
- http://www.educatedguesswork.org/2011/09/security_impact_of_the_rizzodu.html
- http://www.insecure.cl/Beast-SSL.rar
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2012/ms12-006
- http://technet.microsoft.com/security/bulletin/MS12-006
- http://lists.opensuse.org/opensuse-security-announce/2012-01/msg00049.html
- http://lists.opensuse.org/opensuse-security-announce/2012-01/msg00051.html
- http://lists.opensuse.org/opensuse-security-announce/2012-05/msg00009.html
- http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html
- http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html
- http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html
- http://osvdb.org/74829
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14752
- https://bugzilla.redhat.com/show_bug.cgi?id=737506
- http://rhn.redhat.com/errata/RHSA-2012-0508.html
- http://rhn.redhat.com/errata/RHSA-2013-1455.html
- http://secunia.com/advisories/45791
- http://secunia.com/advisories/47998
- http://secunia.com/advisories/48256
- http://secunia.com/advisories/48692
- http://secunia.com/advisories/48915
- http://secunia.com/advisories/48948
- http://secunia.com/advisories/49198
- http://secunia.com/advisories/55322
- http://secunia.com/advisories/55350
- http://secunia.com/advisories/55351
- http://www.securityfocus.com/bid/49388
- http://www.securityfocus.com/bid/49778
- http://www.securitytracker.com/id?1025997
- http://www.securitytracker.com/id?1026103
- http://www.securitytracker.com/id?1026704
- http://www.securitytracker.com/id/1029190
- http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00040.html
- https://hermes.opensuse.org/messages/13154861
- https://hermes.opensuse.org/messages/13155432
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2011-3389
- http://www.ubuntu.com/usn/USN-1263-1
- http://www.mandriva.com/security/advisories?name=MDVSA-2012:058
- http://www.redhat.com/support/errata/RHSA-2011-1384.html
- http://www.redhat.com/support/errata/RHSA-2012-0006.html
low severity
- Vulnerable module: libwmf/libwmf-0.2-7
- Introduced through: libwmf/libwmf-0.2-7@0.2.12-5.1, libwmf/libwmf-dev@0.2.12-5.1 and others
Detailed paths
-
Introduced through: python@latest › libwmf/libwmf-0.2-7@0.2.12-5.1
-
Introduced through: python@latest › libwmf/libwmf-dev@0.2.12-5.1
-
Introduced through: python@latest › libwmf/libwmflite-0.2-7@0.2.12-5.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libwmf
package and not the libwmf
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Array index error in gd_gif_in.c in the GD Graphics Library (libgd) before 2.0.35 allows user-assisted remote attackers to cause a denial of service (crash and heap corruption) via large color index values in crafted image data, which results in a segmentation fault.
Remediation
There is no fixed version for Debian:12
libwmf
.
References
- https://security-tracker.debian.org/tracker/CVE-2007-3476
- http://www.securityfocus.com/archive/1/478796/100/0/threaded
- ftp://ftp.slackware.com/pub/slackware/slackware-11.0/patches/packages/gd-2.0.35-i486-1_slack11.0.tgz
- http://bugs.libgd.org/?do=details&task_id=87
- https://issues.rpath.com/browse/RPL-1643
- http://www.debian.org/security/2008/dsa-1613
- http://fedoranews.org/updates/FEDORA-2007-205.shtml
- http://www.redhat.com/archives/fedora-package-announce/2007-September/msg00311.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-January/052848.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-January/052854.html
- http://security.gentoo.org/glsa/glsa-200708-05.xml
- http://security.gentoo.org/glsa/glsa-200711-34.xml
- http://security.gentoo.org/glsa/glsa-200805-13.xml
- http://www.libgd.org/ReleaseNote020035
- http://osvdb.org/37741
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10348
- https://bugzilla.redhat.com/show_bug.cgi?id=277421
- http://secunia.com/advisories/25860
- http://secunia.com/advisories/26272
- http://secunia.com/advisories/26390
- http://secunia.com/advisories/26415
- http://secunia.com/advisories/26467
- http://secunia.com/advisories/26663
- http://secunia.com/advisories/26766
- http://secunia.com/advisories/26856
- http://secunia.com/advisories/29157
- http://secunia.com/advisories/30168
- http://secunia.com/advisories/31168
- http://secunia.com/advisories/42813
- http://www.securityfocus.com/bid/24651
- http://www.novell.com/linux/security/advisories/2007_15_sr.html
- http://www.trustix.org/errata/2007/0024/
- http://www.vupen.com/english/advisories/2011/0022
- http://www.mandriva.com/security/advisories?name=MDKSA-2007:153
- http://www.mandriva.com/security/advisories?name=MDKSA-2007:164
- http://www.redhat.com/support/errata/RHSA-2008-0146.html
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u5
Detailed paths
-
Introduced through: python@latest › openssh/openssh-client@1:9.2p1-2+deb12u5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh
package and not the openssh
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
OpenSSH, when using OPIE (One-Time Passwords in Everything) for PAM, allows remote attackers to determine the existence of certain user accounts, which displays a different response if the user account exists and is configured to use one-time passwords (OTP), a similar issue to CVE-2007-2243.
Remediation
There is no fixed version for Debian:12
openssh
.
References
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2+deb12u1 and sqlite3/libsqlite3-dev@3.40.1-2+deb12u1
Detailed paths
-
Introduced through: python@latest › sqlite3/libsqlite3-0@3.40.1-2+deb12u1
-
Introduced through: python@latest › sqlite3/libsqlite3-dev@3.40.1-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream sqlite3
package and not the sqlite3
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.
Remediation
There is no fixed version for Debian:12
sqlite3
.
References
- https://security-tracker.debian.org/tracker/CVE-2021-45346
- https://github.com/guyinatuxedo/sqlite3_record_leaking
- https://security.netapp.com/advisory/ntap-20220303-0001/
- https://sqlite.org/forum/forumpost/056d557c2f8c452ed5
- https://sqlite.org/forum/forumpost/53de8864ba114bf6
- https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves
low severity
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: openldap/libldap-2.5-0@2.5.13+dfsg-5
Detailed paths
-
Introduced through: python@latest › openldap/libldap-2.5-0@2.5.13+dfsg-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap
package and not the openldap
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux.
Remediation
There is no fixed version for Debian:12
openldap
.
References
- https://security-tracker.debian.org/tracker/CVE-2020-15719
- https://access.redhat.com/errata/RHBA-2019:3674
- https://bugs.openldap.org/show_bug.cgi?id=9266
- https://bugzilla.redhat.com/show_bug.cgi?id=1740070
- http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00033.html
- http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00059.html
- https://kc.mcafee.com/corporate/index?page=content&id=SB10365
- https://www.oracle.com/security-alerts/cpuapr2022.html
low severity
- Vulnerable module: apt
- Introduced through: apt@2.6.1 and apt/libapt-pkg6.0@2.6.1
Detailed paths
-
Introduced through: python@latest › apt@2.6.1
-
Introduced through: python@latest › apt/libapt-pkg6.0@2.6.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream apt
package and not the apt
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.
Remediation
There is no fixed version for Debian:12
apt
.
References
- https://security-tracker.debian.org/tracker/CVE-2011-3374
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642480
- https://people.canonical.com/~ubuntu-security/cve/2011/CVE-2011-3374.html
- https://seclists.org/fulldisclosure/2011/Sep/221
- https://snyk.io/vuln/SNYK-LINUX-APT-116518
- https://ubuntu.com/security/CVE-2011-3374
- https://access.redhat.com/security/cve/cve-2011-3374
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability classified as problematic has been found in GNU Binutils 2.43. Affected is the function xstrdup of the file xstrdup.c of the component ld. The manipulation leads to memory leak. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:12
binutils
.
References
low severity
new
- Vulnerable module: glib2.0/libglib2.0-0
- Introduced through: glib2.0/libglib2.0-0@2.74.6-2+deb12u5, glib2.0/libglib2.0-bin@2.74.6-2+deb12u5 and others
Detailed paths
-
Introduced through: python@latest › glib2.0/libglib2.0-0@2.74.6-2+deb12u5
-
Introduced through: python@latest › glib2.0/libglib2.0-bin@2.74.6-2+deb12u5
-
Introduced through: python@latest › glib2.0/libglib2.0-data@2.74.6-2+deb12u5
-
Introduced through: python@latest › glib2.0/libglib2.0-dev@2.74.6-2+deb12u5
-
Introduced through: python@latest › glib2.0/libglib2.0-dev-bin@2.74.6-2+deb12u5
…and 2 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream glib2.0
package and not the glib2.0
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A flaw was found in GLib. An integer overflow and buffer under-read occur when parsing a long invalid ISO 8601 timestamp with the g_date_time_new_from_iso8601() function.
Remediation
There is no fixed version for Debian:12
glib2.0
.
References
low severity
new
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.43/2.44 and classified as problematic. Affected by this vulnerability is the function display_info of the file binutils/bucomm.c of the component objdump. The manipulation leads to memory leak. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The patch is named ba6ad3a18cb26b79e0e3b84c39f707535bbc344d. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12
binutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-3198
- https://sourceware.org/bugzilla/show_bug.cgi?id=32716#c0
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ba6ad3a18cb26b79e0e3b84c39f707535bbc344d
- https://vuldb.com/?ctiid.303151
- https://vuldb.com/?id.303151
- https://vuldb.com/?submit.545773
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32716
low severity
- Vulnerable module: elfutils/libelf1
- Introduced through: elfutils/libelf1@0.188-2.1
Detailed paths
-
Introduced through: python@latest › elfutils/libelf1@0.188-2.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream elfutils
package and not the elfutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability, which was classified as problematic, has been found in GNU elfutils 0.192. This issue affects the function gelf_getsymshndx of the file strip.c of the component eu-strip. The manipulation leads to denial of service. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. The identifier of the patch is fbf1df9ca286de3323ae541973b08449f8d03aba. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12
elfutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1377
- https://sourceware.org/bugzilla/attachment.cgi?id=15941
- https://sourceware.org/bugzilla/show_bug.cgi?id=32673
- https://sourceware.org/bugzilla/show_bug.cgi?id=32673#c2
- https://vuldb.com/?ctiid.295985
- https://vuldb.com/?id.295985
- https://vuldb.com/?submit.497539
- https://www.gnu.org/
low severity
- Vulnerable module: elfutils/libelf1
- Introduced through: elfutils/libelf1@0.188-2.1
Detailed paths
-
Introduced through: python@latest › elfutils/libelf1@0.188-2.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream elfutils
package and not the elfutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability has been found in GNU elfutils 0.192 and classified as problematic. This vulnerability affects the function handle_dynamic_symtab of the file readelf.c of the component eu-read. The manipulation leads to null pointer dereference. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The patch is identified as b38e562a4c907e08171c76b8b2def8464d5a104a. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12
elfutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1371
- https://sourceware.org/bugzilla/attachment.cgi?id=15926
- https://sourceware.org/bugzilla/show_bug.cgi?id=32655#c2
- https://vuldb.com/?ctiid.295978
- https://vuldb.com/?id.295978
- https://vuldb.com/?submit.496484
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32655
low severity
- Vulnerable module: gnupg2/dirmngr
- Introduced through: gnupg2/dirmngr@2.2.40-1.1, gnupg2/gnupg@2.2.40-1.1 and others
Detailed paths
-
Introduced through: python@latest › gnupg2/dirmngr@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gnupg@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gnupg-l10n@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gnupg-utils@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpg@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpg-agent@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpg-wks-client@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpg-wks-server@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpgconf@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpgsm@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpgv@2.2.40-1.1
…and 8 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2
package and not the gnupg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.
Remediation
There is no fixed version for Debian:12
gnupg2
.
References
- https://security-tracker.debian.org/tracker/CVE-2022-3219
- https://access.redhat.com/security/cve/CVE-2022-3219
- https://bugzilla.redhat.com/show_bug.cgi?id=2127010
- https://dev.gnupg.org/D556
- https://dev.gnupg.org/T5993
- https://marc.info/?l=oss-security&m=165696590211434&w=4
- https://security.netapp.com/advisory/ntap-20230324-0001/
low severity
- Vulnerable module: procps
- Introduced through: procps@2:4.0.2-3 and procps/libproc2-0@2:4.0.2-3
Detailed paths
-
Introduced through: python@latest › procps@2:4.0.2-3
-
Introduced through: python@latest › procps/libproc2-0@2:4.0.2-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream procps
package and not the procps
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Under some circumstances, this weakness allows a user who has access to run the “ps” utility on a machine, the ability to write almost unlimited amounts of unfiltered data into the process heap.
Remediation
There is no fixed version for Debian:12
procps
.
References
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
Detailed paths
-
Introduced through: python@latest › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: python@latest › shadow/passwd@1:4.13+dfsg1-1+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow
package and not the shadow
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In Shadow 4.13, it is possible to inject control characters into fields provided to the SUID program chfn (change finger). Although it is not possible to exploit this directly (e.g., adding a new user fails because \n is in the block list), it is possible to misrepresent the /etc/passwd file when viewed. Use of \r manipulations and Unicode characters to work around blocking of the : character make it possible to give the impression that a new user has been added. In other words, an adversary may be able to convince a system administrator to take the system offline (an indirect, social-engineered denial of service) by demonstrating that "cat /etc/passwd" shows a rogue user account.
Remediation
There is no fixed version for Debian:12
shadow
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-29383
- https://github.com/shadow-maint/shadow/commit/e5905c4b84d4fb90aefcd96ee618411ebfac663d
- https://github.com/shadow-maint/shadow/pull/687
- https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/cve-2023-29383-abusing-linux-chfn-to-misrepresent-etc-passwd/
- https://www.trustwave.com/en-us/resources/security-resources/security-advisories/?fid=31797
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6+deb12u2, tiff/libtiff6@4.5.0-6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › tiff/libtiff-dev@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiff6@4.5.0-6+deb12u2
-
Introduced through: python@latest › tiff/libtiffxx6@4.5.0-6+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tiff
package and not the tiff
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was found in the tiffcp utility distributed by the libtiff package where a crafted TIFF file on processing may cause a heap-based buffer overflow leads to an application crash.
Remediation
There is no fixed version for Debian:12
tiff
.
References
low severity
- Vulnerable module: unzip
- Introduced through: unzip@6.0-28
Detailed paths
-
Introduced through: python@latest › unzip@6.0-28
NVD Description
Note: Versions mentioned in the description apply only to the upstream unzip
package and not the unzip
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A flaw was found in unzip. The vulnerability occurs due to improper handling of Unicode strings, which can lead to a null pointer dereference. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.
Remediation
There is no fixed version for Debian:12
unzip
.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been classified as problematic. This affects the function xstrdup of the file libiberty/xmalloc.c of the component ld. The manipulation leads to memory leak. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:12
binutils
.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been declared as problematic. This vulnerability affects the function bfd_malloc of the file libbfd.c of the component ld. The manipulation leads to memory leak. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:12
binutils
.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43 and classified as problematic. Affected by this issue is the function link_order_scan of the file ld/ldelfgen.c of the component ld. The manipulation leads to memory leak. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:12
binutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1148
- https://sourceware.org/bugzilla/attachment.cgi?id=15887
- https://sourceware.org/bugzilla/show_bug.cgi?id=32576
- https://vuldb.com/?ctiid.295052
- https://vuldb.com/?id.295052
- https://vuldb.com/?submit.485747
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0004/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43. It has been rated as problematic. This issue affects the function xmemdup of the file xmemdup.c of the component ld. The manipulation leads to memory leak. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Debian:12
binutils
.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability classified as problematic has been found in GNU Binutils 2.43. This affects the function _bfd_elf_write_section_eh_frame of the file bfd/elf-eh-frame.c of the component ld. The manipulation leads to memory corruption. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12
binutils
.
References
low severity
- Vulnerable module: elfutils/libelf1
- Introduced through: elfutils/libelf1@0.188-2.1
Detailed paths
-
Introduced through: python@latest › elfutils/libelf1@0.188-2.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream elfutils
package and not the elfutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability classified as problematic was found in GNU elfutils 0.192. This vulnerability affects the function elf_strptr in the library /libelf/elf_strptr.c of the component eu-strip. The manipulation leads to denial of service. It is possible to launch the attack on the local host. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is b16f441cca0a4841050e3215a9f120a6d8aea918. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Debian:12
elfutils
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1376
- https://sourceware.org/bugzilla/attachment.cgi?id=15940
- https://sourceware.org/bugzilla/show_bug.cgi?id=32672
- https://sourceware.org/bugzilla/show_bug.cgi?id=32672#c3
- https://vuldb.com/?ctiid.295984
- https://vuldb.com/?id.295984
- https://vuldb.com/?submit.497538
- https://www.gnu.org/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
GNU objdump 2.43 is vulnerable to Buffer Overflow in the BFD (Binary File Descriptor) library's handling of tekhex format files.
Remediation
There is no fixed version for Debian:12
binutils
.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: python@latest › binutils@2.40-2
-
Introduced through: python@latest › binutils/binutils-common@2.40-2
-
Introduced through: python@latest › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: python@latest › binutils/libbinutils@2.40-2
-
Introduced through: python@latest › binutils/libctf-nobfd0@2.40-2
-
Introduced through: python@latest › binutils/libctf0@2.40-2
-
Introduced through: python@latest › binutils/libgprofng0@2.40-2
…and 4 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils
package and not the binutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
https://www.gnu.org/software/binutils/ nm >=2.43 is affected by: Incorrect Access Control. The type of exploitation is: local. The component is: nm --without-symbol-version
function.
Remediation
There is no fixed version for Debian:12
binutils
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
BlueZ Audio Profile AVRCP Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code via Bluetooth on affected installations of BlueZ. User interaction is required to exploit this vulnerability in that the target must connect to a malicious device.
The specific flaw exists within the handling of the AVRCP protocol. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-19909.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
BlueZ Audio Profile AVRCP avrcp_parse_attribute_list Out-Of-Bounds Read Information Disclosure Vulnerability. This vulnerability allows network-adjacent attackers to disclose sensitive information via Bluetooth on affected installations of BlueZ. User interaction is required to exploit this vulnerability in that the target must connect to a malicious device.
The specific flaw exists within the handling of the AVRCP protocol. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of root. Was ZDI-CAN-20852.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
BlueZ Audio Profile AVRCP parse_media_element Out-Of-Bounds Read Information Disclosure Vulnerability. This vulnerability allows network-adjacent attackers to disclose sensitive information via Bluetooth on affected installations of BlueZ. User interaction is required to exploit this vulnerability in that the target must connect to a malicious device.
The specific flaw exists within the handling of the AVRCP protocol. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of root. Was ZDI-CAN-20853.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
BlueZ Audio Profile AVRCP parse_media_folder Out-Of-Bounds Read Information Disclosure Vulnerability. This vulnerability allows network-adjacent attackers to disclose sensitive information via Bluetooth on affected installations of BlueZ. User interaction is required to exploit this vulnerability in that the target must connect to a malicious device.
The specific flaw exists within the handling of the AVRCP protocol. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of root. Was ZDI-CAN-20854.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
BlueZ OBEX Library Out-Of-Bounds Read Information Disclosure Vulnerability. This vulnerability allows network-adjacent attackers to disclose sensitive information on affected installations of BlueZ. User interaction is required to exploit this vulnerability in that the target must connect to a malicious Bluetooth device.
The specific flaw exists within the handling of OBEX protocol parameters. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of root. Was ZDI-CAN-20937.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: bluez/libbluetooth-dev
- Introduced through: bluez/libbluetooth-dev@5.66-1+deb12u2 and bluez/libbluetooth3@5.66-1+deb12u2
Detailed paths
-
Introduced through: python@latest › bluez/libbluetooth-dev@5.66-1+deb12u2
-
Introduced through: python@latest › bluez/libbluetooth3@5.66-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez
package and not the bluez
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
BlueZ Phone Book Access Profile Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of BlueZ. User interaction is required to exploit this vulnerability in that the target must connect to a malicious Bluetooth device.
The specific flaw exists within the handling of the Phone Book Access profile. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-20939.
Remediation
There is no fixed version for Debian:12
bluez
.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u12, curl/libcurl3-gnutls@7.88.1-10+deb12u12 and others
Detailed paths
-
Introduced through: python@latest › curl@7.88.1-10+deb12u12
-
Introduced through: python@latest › curl/libcurl3-gnutls@7.88.1-10+deb12u12
-
Introduced through: python@latest › curl/libcurl4@7.88.1-10+deb12u12
-
Introduced through: python@latest › curl/libcurl4-openssl-dev@7.88.1-10+deb12u12
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl
package and not the curl
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libcurl skips the certificate verification for a QUIC connection under certain conditions, when built to use wolfSSL. If told to use an unknown/bad cipher or curve, the error path accidentally skips the verification and returns OK, thus ignoring any certificate problems.
Remediation
There is no fixed version for Debian:12
curl
.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2379
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://www.openwall.com/lists/oss-security/2024/03/27/2
- https://curl.se/docs/CVE-2024-2379.html
- https://curl.se/docs/CVE-2024-2379.json
- https://hackerone.com/reports/2410774
- https://security.netapp.com/advisory/ntap-20240531-0001/
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10+deb12u12, curl/libcurl3-gnutls@7.88.1-10+deb12u12 and others
Detailed paths
-
Introduced through: python@latest › curl@7.88.1-10+deb12u12
-
Introduced through: python@latest › curl/libcurl3-gnutls@7.88.1-10+deb12u12
-
Introduced through: python@latest › curl/libcurl4@7.88.1-10+deb12u12
-
Introduced through: python@latest › curl/libcurl4-openssl-dev@7.88.1-10+deb12u12
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl
package and not the curl
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
When libcurl is asked to perform automatic gzip decompression of
content-encoded HTTP responses with the CURLOPT_ACCEPT_ENCODING
option,
using zlib 1.2.0.3 or older, an attacker-controlled integer overflow would
make libcurl perform a buffer overflow.
Remediation
There is no fixed version for Debian:12
curl
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-0725
- https://curl.se/docs/CVE-2025-0725.html
- https://curl.se/docs/CVE-2025-0725.json
- https://hackerone.com/reports/2956023
- http://www.openwall.com/lists/oss-security/2025/02/05/3
- http://www.openwall.com/lists/oss-security/2025/02/06/2
- http://www.openwall.com/lists/oss-security/2025/02/06/4
- https://security.netapp.com/advisory/ntap-20250306-0009/
low severity
- Vulnerable module: elfutils/libelf1
- Introduced through: elfutils/libelf1@0.188-2.1
Detailed paths
-
Introduced through: python@latest › elfutils/libelf1@0.188-2.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream elfutils
package and not the elfutils
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
elfutils v0.189 was discovered to contain a NULL pointer dereference via the handle_verdef() function at readelf.c.
Remediation
There is no fixed version for Debian:12
elfutils
.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1 and expat/libexpat1-dev@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@latest › expat/libexpat1@2.5.0-1+deb12u1
-
Introduced through: python@latest › expat/libexpat1-dev@2.5.0-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat
package and not the expat
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in libexpat before 2.6.4. There is a crash within the XML_ResumeParser function because XML_StopParser can stop/suspend an unstarted parser.
Remediation
There is no fixed version for Debian:12
expat
.
References
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.5-0+deb12u2 and git/git-man@1:2.39.5-0+deb12u2
Detailed paths
-
Introduced through: python@latest › git@1:2.39.5-0+deb12u2
-
Introduced through: python@latest › git/git-man@1:2.39.5-0+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream git
package and not the git
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.
Remediation
There is no fixed version for Debian:12
git
.
References
low severity
new
- Vulnerable module: glib2.0/libglib2.0-0
- Introduced through: glib2.0/libglib2.0-0@2.74.6-2+deb12u5, glib2.0/libglib2.0-bin@2.74.6-2+deb12u5 and others
Detailed paths
-
Introduced through: python@latest › glib2.0/libglib2.0-0@2.74.6-2+deb12u5
-
Introduced through: python@latest › glib2.0/libglib2.0-bin@2.74.6-2+deb12u5
-
Introduced through: python@latest › glib2.0/libglib2.0-data@2.74.6-2+deb12u5
-
Introduced through: python@latest › glib2.0/libglib2.0-dev@2.74.6-2+deb12u5
-
Introduced through: python@latest › glib2.0/libglib2.0-dev-bin@2.74.6-2+deb12u5
…and 2 more
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Debian:12
glib2.0
.
References
low severity
- Vulnerable module: gnupg2/dirmngr
- Introduced through: gnupg2/dirmngr@2.2.40-1.1, gnupg2/gnupg@2.2.40-1.1 and others
Detailed paths
-
Introduced through: python@latest › gnupg2/dirmngr@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gnupg@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gnupg-l10n@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gnupg-utils@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpg@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpg-agent@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpg-wks-client@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpg-wks-server@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpgconf@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpgsm@2.2.40-1.1
-
Introduced through: python@latest › gnupg2/gpgv@2.2.40-1.1
…and 8 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2
package and not the gnupg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In GnuPG before 2.5.5, if a user chooses to import a certificate with certain crafted subkey data that lacks a valid backsig or that has incorrect usage flags, the user loses the ability to verify signatures made from certain other signing keys, aka a "verification DoS."
Remediation
There is no fixed version for Debian:12
gnupg2
.
References
low severity
new
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › imagemagick@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6+deb12u2
-
Introduced through: python@latest › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6+deb12u2
…and 10 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream imagemagick
package and not the imagemagick
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In MIFF image processing in ImageMagick before 7.1.1-44, image depth is mishandled after SetQuantumFormat is used.
Remediation
There is no fixed version for Debian:12
imagemagick
.
References
low severity
- Vulnerable module: krb5/krb5-multidev
- Introduced through: krb5/krb5-multidev@1.20.1-2+deb12u2, krb5/libgssapi-krb5-2@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › krb5/krb5-multidev@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libgssrpc4@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkadm5clnt-mit12@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkadm5srv-mit12@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkdb5-10@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5-dev@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5support0@1.20.1-2+deb12u2
…and 7 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5
package and not the krb5
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.
Remediation
There is no fixed version for Debian:12
krb5
.
References
low severity
- Vulnerable module: krb5/krb5-multidev
- Introduced through: krb5/krb5-multidev@1.20.1-2+deb12u2, krb5/libgssapi-krb5-2@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › krb5/krb5-multidev@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libgssrpc4@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkadm5clnt-mit12@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkadm5srv-mit12@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkdb5-10@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5-dev@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5support0@1.20.1-2+deb12u2
…and 7 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5
package and not the krb5
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.
Remediation
There is no fixed version for Debian:12
krb5
.
References
low severity
- Vulnerable module: krb5/krb5-multidev
- Introduced through: krb5/krb5-multidev@1.20.1-2+deb12u2, krb5/libgssapi-krb5-2@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@latest › krb5/krb5-multidev@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libgssrpc4@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkadm5clnt-mit12@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkadm5srv-mit12@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkdb5-10@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5-dev@1.20.1-2+deb12u2
-
Introduced through: python@latest › krb5/libkrb5support0@1.20.1-2+deb12u2
…and 7 more
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Debian:12
krb5
.
References
low severity
new
- Vulnerable module: lcms2/liblcms2-2
- Introduced through: lcms2/liblcms2-2@2.14-2 and lcms2/liblcms2-dev@2.14-2
Detailed paths
-
Introduced through: python@latest › lcms2/liblcms2-2@2.14-2
-
Introduced through: python@latest › lcms2/liblcms2-dev@2.14-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream lcms2
package and not the lcms2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A heap buffer overflow vulnerability has been identified in thesmooth2() in cmsgamma.c in lcms2-2.16 which allows a remote attacker to cause a denial of service. NOTE: the Supplier disputes this because "this is not exploitable as this function is never called on normal color management, is there only as a helper for low-level programming and investigation."
Remediation
There is no fixed version for Debian:12
lcms2
.
References
low severity
- Vulnerable module: libcap2
- Introduced through: libcap2@1:2.66-4
Detailed paths
-
Introduced through: python@latest › libcap2@1:2.66-4
NVD Description
Note: Versions mentioned in the description apply only to the upstream libcap2
package and not the libcap2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The PAM module pam_cap.so of libcap configuration supports group names starting with “@”, during actual parsing, configurations not starting with “@” are incorrectly recognized as group names. This may result in nonintended users being granted an inherited capability set, potentially leading to security risks. Attackers can exploit this vulnerability to achieve local privilege escalation on systems where /etc/security/capability.conf is used to configure user inherited privileges by constructing specific usernames.
Remediation
There is no fixed version for Debian:12
libcap2
.
References
low severity
- Vulnerable module: libde265/libde265-0
- Introduced through: libde265/libde265-0@1.0.11-1+deb12u2
Detailed paths
-
Introduced through: python@latest › libde265/libde265-0@1.0.11-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libde265
package and not the libde265
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Buffer Overflow vulnerability in libde265 v1.0.12 allows a local attacker to cause a denial of service via the allocation size exceeding the maximum supported size of 0x10000000000.
Remediation
There is no fixed version for Debian:12
libde265
.
References
- https://security-tracker.debian.org/tracker/CVE-2023-51792
- https://github.com/strukturag/libde265
- https://github.com/strukturag/libde265/issues/427
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6G7EYH2JAK5OJPVNC6AXYQ5K7YGYNCDN/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IPETICRXUOGRIM4U3BCRTIKE3IZWCSBT/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LE3ASLH6QF2E5OVJI5VA3JSEPJFFFMNY/
low severity
- Vulnerable module: libde265/libde265-0
- Introduced through: libde265/libde265-0@1.0.11-1+deb12u2
Detailed paths
-
Introduced through: python@latest › libde265/libde265-0@1.0.11-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libde265
package and not the libde265
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Heap Buffer Overflow vulnerability in Libde265 v1.0.15 allows attackers to crash the application via crafted payload to display444as420 function at sdl.cc
Remediation
There is no fixed version for Debian:12
libde265
.
References
low severity
- Vulnerable module: libde265/libde265-0
- Introduced through: libde265/libde265-0@1.0.11-1+deb12u2
Detailed paths
-
Introduced through: python@latest › libde265/libde265-0@1.0.11-1+deb12u2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libde265
package and not the libde265
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Heap Buffer Overflow vulnerability in Libde265 v1.0.15 allows attackers to crash the application via crafted payload to __interceptor_memcpy function.
Remediation
There is no fixed version for Debian:12
libde265
.
References
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.10.1-3
Detailed paths
-
Introduced through: python@latest › libgcrypt20@1.10.1-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream libgcrypt20
package and not the libgcrypt20
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.
Remediation
There is no fixed version for Debian:12
libgcrypt20
.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2236
- https://access.redhat.com/errata/RHSA-2024:9404
- https://bugzilla.redhat.com/show_bug.cgi?id=2268268
- https://access.redhat.com/errata/RHSA-2025:3534
- https://access.redhat.com/errata/RHSA-2025:3530
- https://access.redhat.com/security/cve/CVE-2024-2236
- https://bugzilla.redhat.com/show_bug.cgi?id=2245218
low severity
- Vulnerable module: libheif/libheif1
- Introduced through: libheif/libheif1@1.15.1-1+deb12u1
Detailed paths
-
Introduced through: python@latest › libheif/libheif1@1.15.1-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libheif
package and not the libheif
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libheif <= 1.17.6 contains a memory leak in the function JpegEncoder::Encode. This flaw allows an attacker to cause a denial of service attack.
Remediation
There is no fixed version for Debian:12
libheif
.
References
low severity
new
- Vulnerable module: libheif/libheif1
- Introduced through: libheif/libheif1@1.15.1-1+deb12u1
Detailed paths
-
Introduced through: python@latest › libheif/libheif1@1.15.1-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libheif
package and not the libheif
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libheif before 1.19.6 has a NULL pointer dereference in ImageItem_iden in image-items/iden.cc.
Remediation
There is no fixed version for Debian:12
libheif
.
References
low severity
new
- Vulnerable module: libheif/libheif1
- Introduced through: libheif/libheif1@1.15.1-1+deb12u1
Detailed paths
-
Introduced through: python@latest › libheif/libheif1@1.15.1-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libheif
package and not the libheif
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libheif before 1.19.6 has a NULL pointer dereference in ImageItem_Grid::get_decoder in image-items/grid.cc because a grid image can reference a nonexistent image item.
Remediation
There is no fixed version for Debian:12
libheif
.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1 and libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: python@latest › libxml2@2.9.14+dfsg-1.3~deb12u1
-
Introduced through: python@latest › libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2
package and not the libxml2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
xmlXIncludeAddNode in xinclude.c in libxml2 before 2.11.0 has a use-after-free.
Remediation
There is no fixed version for Debian:12
libxml2
.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1 and libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: python@latest › libxml2@2.9.14+dfsg-1.3~deb12u1
-
Introduced through: python@latest › libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2
package and not the libxml2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue was discovered in xmllint (from libxml2) before 2.11.8 and 2.12.x before 2.12.7. Formatting error messages with xmllint --htmlout can result in a buffer over-read in xmlHTMLPrintFileContext in xmllint.c.
Remediation
There is no fixed version for Debian:12
libxml2
.
References
- https://security-tracker.debian.org/tracker/CVE-2024-34459
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/720
- https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.11.8
- https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.7
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/5HVUXKYTBWT3G5DEEQX62STJQBY367NL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/INKSSLW5VMZIXHRPZBAW4TJUX5SQKARG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VRDJCNQP32LV56KESUQ5SNZKAJWSZZRI/
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1 and libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: python@latest › libxml2@2.9.14+dfsg-1.3~deb12u1
-
Introduced through: python@latest › libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2
package and not the libxml2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and xmlSchemaBubbleIDCNodeTables in xmlschemas.c. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used.
Remediation
There is no fixed version for Debian:12
libxml2
.
References
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.3~deb12u1 and libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: python@latest › libxml2@2.9.14+dfsg-1.3~deb12u1
-
Introduced through: python@latest › libxml2/libxml2-dev@2.9.14+dfsg-1.3~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libxml2
package and not the libxml2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a stack-based buffer overflow in xmlSnprintfElements in valid.c. To exploit this, DTD validation must occur for an untrusted document or untrusted DTD. NOTE: this is similar to CVE-2017-9047.
Remediation
There is no fixed version for Debian:12
libxml2
.
References
low severity
- Vulnerable module: mariadb/libmariadb-dev
- Introduced through: mariadb/libmariadb-dev@1:10.11.11-0+deb12u1, mariadb/libmariadb-dev-compat@1:10.11.11-0+deb12u1 and others
Detailed paths
-
Introduced through: python@latest › mariadb/libmariadb-dev@1:10.11.11-0+deb12u1
-
Introduced through: python@latest › mariadb/libmariadb-dev-compat@1:10.11.11-0+deb12u1
-
Introduced through: python@latest › mariadb/libmariadb3@1:10.11.11-0+deb12u1
-
Introduced through: python@latest › mariadb/mariadb-common@1:10.11.11-0+deb12u1
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream mariadb
package and not the mariadb
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
MariaDB Server 10.4 through 10.5., 10.6 through 10.6., 10.7 through 10.11., and 11.0 through 11.0. can sometimes crash with an empty backtrace log. This may be related to make_aggr_tables_info and optimize_stage2.
Remediation
There is no fixed version for Debian:12
mariadb
.
References
low severity
- Vulnerable module: mariadb/libmariadb-dev
- Introduced through: mariadb/libmariadb-dev@1:10.11.11-0+deb12u1, mariadb/libmariadb-dev-compat@1:10.11.11-0+deb12u1 and others
Detailed paths
-
Introduced through: python@latest › mariadb/libmariadb-dev@1:10.11.11-0+deb12u1
-
Introduced through: python@latest › mariadb/libmariadb-dev-compat@1:10.11.11-0+deb12u1
-
Introduced through: python@latest › mariadb/libmariadb3@1:10.11.11-0+deb12u1
-
Introduced through: python@latest › mariadb/mariadb-common@1:10.11.11-0+deb12u1
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream mariadb
package and not the mariadb
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
MariaDB Server 10.4 through 10.5., 10.6 through 10.6., 10.7 through 10.11., 11.0 through 11.0., and 11.1 through 11.4.* crashes in Item_direct_view_ref::derived_field_transformer_for_where.
Remediation
There is no fixed version for Debian:12
mariadb
.
References
low severity
- Vulnerable module: mariadb/libmariadb-dev
- Introduced through: mariadb/libmariadb-dev@1:10.11.11-0+deb12u1, mariadb/libmariadb-dev-compat@1:10.11.11-0+deb12u1 and others
Detailed paths
-
Introduced through: python@latest › mariadb/libmariadb-dev@1:10.11.11-0+deb12u1
-
Introduced through: python@latest › mariadb/libmariadb-dev-compat@1:10.11.11-0+deb12u1
-
Introduced through: python@latest › mariadb/libmariadb3@1:10.11.11-0+deb12u1
-
Introduced through: python@latest › mariadb/mariadb-common@1:10.11.11-0+deb12u1
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream mariadb
package and not the mariadb
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
MariaDB Server 10.10 through 10.11.* and 11.0 through 11.4.* crashes in JOIN::fix_all_splittings_in_plan.
Remediation
There is no fixed version for Debian:12
mariadb
.
References
low severity
- Vulnerable module: openexr/libopenexr-3-1-30
- Introduced through: openexr/libopenexr-3-1-30@3.1.5-5 and openexr/libopenexr-dev@3.1.5-5
Detailed paths
-
Introduced through: python@latest › openexr/libopenexr-3-1-30@3.1.5-5
-
Introduced through: python@latest › openexr/libopenexr-dev@3.1.5-5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openexr
package and not the openexr
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
An issue in Academy Software Foundation openexr v.3.2.3 and before allows a local attacker to cause a denial of service (DoS) via the convert function of exrmultipart.cpp.
Remediation
There is no fixed version for Debian:12
openexr
.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A flaw was found in OpenJPEG. Maliciously constructed pictures can cause the program to enter a large loop and continuously print warning messages on the terminal.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A flaw was found in OpenJPEG. A resource exhaustion can occur in the opj_t1_decode_cblks function in tcd.c through a crafted image file, causing a denial of service.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2+deb12u1 and openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
Detailed paths
-
Introduced through: python@latest › openjpeg2/libopenjp2-7@2.5.0-2+deb12u1
-
Introduced through: python@latest › openjpeg2/libopenjp2-7-dev@2.5.0-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openjpeg2
package and not the openjpeg2
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
A vulnerability was found in OpenJPEG similar to CVE-2019-6988. This flaw allows an attacker to bypass existing protections and cause an application crash through a maliciously crafted file.
Remediation
There is no fixed version for Debian:12
openjpeg2
.
References
low severity
new
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2+deb12u5
Detailed paths
-
Introduced through: python@latest › openssh/openssh-client@1:9.2p1-2+deb12u5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh
package and not the openssh
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In sshd in OpenSSH before 10.0, the DisableForwarding directive does not adhere to the documentation stating that it disables X11 and agent forwarding.
Remediation
There is no fixed version for Debian:12
openssh
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-32728
- https://ftp.openbsd.org/pub/OpenBSD/patches/7.6/common/013_ssh.patch.sig
- https://github.com/openssh/openssh-portable/commit/fc86875e6acb36401dfc1dfb6b628a9d1460f367
- https://lists.mindrot.org/pipermail/openssh-unix-dev/2025-April/041879.html
- https://www.openssh.com/txt/release-10.0
- https://www.openssh.com/txt/release-7.4
- https://security.netapp.com/advisory/ntap-20250425-0002/
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.15-1~deb12u1, openssl/libssl-dev@3.0.15-1~deb12u1 and others
Detailed paths
-
Introduced through: python@latest › openssl@3.0.15-1~deb12u1
-
Introduced through: python@latest › openssl/libssl-dev@3.0.15-1~deb12u1
-
Introduced through: python@latest › openssl/libssl3@3.0.15-1~deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl
package and not the openssl
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation.
Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency.
There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low.
The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are affected by this issue.
Remediation
There is no fixed version for Debian:12
openssl
.
References
- https://security-tracker.debian.org/tracker/CVE-2024-13176
- https://github.com/openssl/openssl/commit/07272b05b04836a762b4baa874958af51d513844
- https://github.com/openssl/openssl/commit/2af62e74fb59bc469506bc37eb2990ea408d9467
- https://github.com/openssl/openssl/commit/392dcb336405a0c94486aa6655057f59fd3a0902
- https://github.com/openssl/openssl/commit/4b1cb94a734a7d4ec363ac0a215a25c181e11f65
- https://github.com/openssl/openssl/commit/77c608f4c8857e63e98e66444e2e761c9627916f
- https://github.openssl.org/openssl/extended-releases/commit/0d5fd1ab987f7571e2c955d8d8b638fc0fb54ded
- https://github.openssl.org/openssl/extended-releases/commit/a2639000db19878d5d89586ae7b725080592ae86
- https://openssl-library.org/news/secadv/20250120.txt
- http://www.openwall.com/lists/oss-security/2025/01/20/2
- https://security.netapp.com/advisory/ntap-20250124-0005/
- https://security.netapp.com/advisory/ntap-20250418-0010/
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6+deb12u5, python3.11/libpython3.11-minimal@3.11.2-6+deb12u5 and others
Detailed paths
-
Introduced through: python@latest › python3.11@3.11.2-6+deb12u5
-
Introduced through: python@latest › python3.11/libpython3.11-minimal@3.11.2-6+deb12u5
-
Introduced through: python@latest › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u5
-
Introduced through: python@latest › python3.11/python3.11-minimal@3.11.2-6+deb12u5
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream python3.11
package and not the python3.11
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
The Python standard library functions urllib.parse.urlsplit
and urlparse
accepted domain names that included square brackets which isn't valid according to RFC 3986. Square brackets are only meant to be used as delimiters for specifying IPv6 and IPvFuture hosts in URLs. This could result in differential parsing across the Python URL parser and other specification-compliant URL parsers.
Remediation
There is no fixed version for Debian:12
python3.11
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-0938
- https://github.com/python/cpython/issues/105704
- https://github.com/python/cpython/pull/129418
- https://github.com/python/cpython/commit/d89a5f6a6e65511a5f6e0618c4c30a7aa5aba56a
- https://mail.python.org/archives/list/security-announce@python.org/thread/K4EUG6EKV6JYFIC24BASYOZS4M5XOQIB/
- https://github.com/python/cpython/commit/90e526ae67b172ed7c6c56e7edad36263b0f9403
- https://github.com/python/cpython/commit/a7084f6075c9595ba60119ce8c62f1496f50c568
- https://github.com/python/cpython/commit/526617ed68cde460236c973e5d0a8bad4de896ba
- https://github.com/python/cpython/commit/b8b4b713c5f8ec0958c7ef8d29d6711889bc94ab
- https://github.com/python/cpython/commit/ff4e5c25666f63544071a6b075ae8b25c98b7a32
- https://security.netapp.com/advisory/ntap-20250314-0002/
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6+deb12u5, python3.11/libpython3.11-minimal@3.11.2-6+deb12u5 and others
Detailed paths
-
Introduced through: python@latest › python3.11@3.11.2-6+deb12u5
-
Introduced through: python@latest › python3.11/libpython3.11-minimal@3.11.2-6+deb12u5
-
Introduced through: python@latest › python3.11/libpython3.11-stdlib@3.11.2-6+deb12u5
-
Introduced through: python@latest › python3.11/python3.11-minimal@3.11.2-6+deb12u5
…and 1 more
NVD Description
Note: Versions mentioned in the description apply only to the upstream python3.11
package and not the python3.11
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
During an address list folding when a separating comma ends up on a folded line and that line is to be unicode-encoded then the separator itself is also unicode-encoded. Expected behavior is that the separating comma remains a plan comma. This can result in the address header being misinterpreted by some mail servers.
Remediation
There is no fixed version for Debian:12
python3.11
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-1795
- https://github.com/python/cpython/issues/100884
- https://github.com/python/cpython/pull/100885
- https://github.com/python/cpython/pull/119099
- https://github.com/python/cpython/commit/09fab93c3d857496c0bd162797fab816c311ee48
- https://github.com/python/cpython/commit/70754d21c288535e86070ca7a6e90dcb670b8593
- https://github.com/python/cpython/commit/9148b77e0af91cdacaa7fe3dfac09635c3fe9a74
- https://mail.python.org/archives/list/security-announce@python.org/thread/MB62IZMEC3UM6SGHP5LET5JX2Y7H4ZUR/
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
Detailed paths
-
Introduced through: python@latest › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: python@latest › shadow/passwd@1:4.13+dfsg1-1+b1
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow
package and not the shadow
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.
Remediation
There is no fixed version for Debian:12
shadow
.
References
low severity
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2+deb12u1 and sqlite3/libsqlite3-dev@3.40.1-2+deb12u1
Detailed paths
-
Introduced through: python@latest › sqlite3/libsqlite3-0@3.40.1-2+deb12u1
-
Introduced through: python@latest › sqlite3/libsqlite3-dev@3.40.1-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream sqlite3
package and not the sqlite3
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
In SQLite 3.49.0 before 3.49.1, certain argument values to sqlite3_db_config (in the C-language API) can cause a denial of service (application crash). An sz*nBig multiplication is not cast to a 64-bit integer, and consequently some memory allocations may be incorrect.
Remediation
There is no fixed version for Debian:12
sqlite3
.
References
- https://security-tracker.debian.org/tracker/CVE-2025-29088
- https://gist.github.com/ylwango613/d3883fb9f6ba8a78086356779ce88248
- https://github.com/sqlite/sqlite/commit/56d2fd008b108109f489339f5fd55212bb50afd4
- https://sqlite.org/forum/forumpost/48f365daec
- https://sqlite.org/releaselog/3_49_1.html
- https://www.sqlite.org/cves.html
low severity
- Vulnerable module: wget
- Introduced through: wget@1.21.3-1+deb12u1
Detailed paths
-
Introduced through: python@latest › wget@1.21.3-1+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream wget
package and not the wget
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Applications that use Wget to access a remote resource using shorthand URLs and pass arbitrary user credentials in the URL are vulnerable. In these cases attackers can enter crafted credentials which will cause Wget to access an arbitrary host.
Remediation
There is no fixed version for Debian:12
wget
.
References
- https://security-tracker.debian.org/tracker/CVE-2024-10524
- https://git.savannah.gnu.org/cgit/wget.git/commit/?id=c419542d956a2607bbce5df64b9d378a8588d778
- https://jfrog.com/blog/cve-2024-10524-wget-zero-day-vulnerability/
- https://seclists.org/oss-sec/2024/q4/107
- http://www.openwall.com/lists/oss-security/2024/11/18/6
- https://security.netapp.com/advisory/ntap-20250321-0007/