Vulnerabilities |
290 via 993 paths |
|---|---|
Dependencies |
415 |
Source |
Docker |
Target OS |
debian:12 |
critical severity
- Vulnerable module: aom/libaom3
- Introduced through: aom/libaom3@3.6.0-1
- Fixed in: 3.6.0-1+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › aom/libaom3@3.6.0-1
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.
Integer overflow in libaom internal function img_alloc_helper can lead to heap buffer overflow. This function can be reached via 3 callers:
- Calling aom_img_alloc() with a large value of the d_w, d_h, or align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid.
- Calling aom_img_wrap() with a large value of the d_w, d_h, or align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid.
- Calling aom_img_alloc_with_border() with a large value of the d_w, d_h, align, size_align, or border parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid.
Remediation
Upgrade Debian:12 aom to version 3.6.0-1+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-5171
- https://issues.chromium.org/issues/332382766
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6HYUEHZ35ZPY2EONVZCGO6LPT3AMLZCP/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U5NRNCEYS246CYGOR32MF7OGKWOWER22/
critical severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10, curl/libcurl3-gnutls@7.88.1-10 and others
- Fixed in: 7.88.1-10+deb12u4
Detailed paths
-
Introduced through: node@18.16.1-bookworm › curl@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl3-gnutls@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4-openssl-dev@7.88.1-10
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.
This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake.
When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes.
If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there.
The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with.
Remediation
Upgrade Debian:12 curl to version 7.88.1-10+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-38545
- https://curl.se/docs/CVE-2023-38545.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OGMXNRNSJ4ETDK6FRNU3J7SABXPWCHSQ/
- https://security.netapp.com/advisory/ntap-20231027-0009/
- https://www.secpod.com/blog/high-severity-heap-buffer-overflow-vulnerability/
- http://seclists.org/fulldisclosure/2024/Jan/34
- http://seclists.org/fulldisclosure/2024/Jan/37
- http://seclists.org/fulldisclosure/2024/Jan/38
- https://security.netapp.com/advisory/ntap-20240201-0005/
- https://support.apple.com/kb/HT214036
- https://support.apple.com/kb/HT214057
- https://support.apple.com/kb/HT214058
- https://support.apple.com/kb/HT214063
- https://forum.vmssoftware.com/viewtopic.php?f=8&t=8868
critical severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2
- Fixed in: 1:9.2p1-2+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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.
ssh-add in OpenSSH before 9.3 adds smartcard keys to ssh-agent without the intended per-hop destination constraints. The earliest affected version is 8.9.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-28531
- https://www.openwall.com/lists/oss-security/2023/03/15/8
- https://security.netapp.com/advisory/ntap-20230413-0008/
- https://security.gentoo.org/glsa/202307-01
- https://www.debian.org/security/2023/dsa-5586
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/AN2UDTXEUSKFIOIYMV6JNI5VSBMYZOFT/
critical severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2
- Fixed in: 1:9.2p1-2+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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 PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: this issue exists because of an incomplete fix for CVE-2016-10009.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-38408
- http://packetstormsecurity.com/files/173661/OpenSSH-Forwarded-SSH-Agent-Remote-Code-Execution.html
- http://www.openwall.com/lists/oss-security/2023/07/20/1
- http://www.openwall.com/lists/oss-security/2023/07/20/2
- https://blog.qualys.com/vulnerabilities-threat-research/2023/07/19/cve-2023-38408-remote-code-execution-in-opensshs-forwarded-ssh-agent
- https://github.com/openbsd/src/commit/7bc29a9d5cd697290aa056e94ecee6253d3425f8
- https://github.com/openbsd/src/commit/f03a4faa55c4ce0818324701dadbf91988d7351d
- https://github.com/openbsd/src/commit/f8f5a6b003981bb824329dc987d101977beda7ca
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CEBTJJINE2I3FHAUKKNQWMFGYMLSMWKQ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RAXVQS6ZYTULFAK3TEJHRLKZALJS3AOU/
- https://news.ycombinator.com/item?id=36790196
- https://security.gentoo.org/glsa/202307-01
- https://www.openssh.com/security.html
- https://www.openssh.com/txt/release-9.3p2
- https://www.qualys.com/2023/07/19/cve-2023-38408/rce-openssh-forwarded-ssh-agent.txt
- https://security.netapp.com/advisory/ntap-20230803-0010/
- https://lists.debian.org/debian-lts-announce/2023/08/msg00021.html
- http://www.openwall.com/lists/oss-security/2023/09/22/9
- http://www.openwall.com/lists/oss-security/2023/09/22/11
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CEBTJJINE2I3FHAUKKNQWMFGYMLSMWKQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RAXVQS6ZYTULFAK3TEJHRLKZALJS3AOU/
- https://support.apple.com/kb/HT213940
- https://www.vicarius.io/vsociety/posts/exploring-opensshs-agent-forwarding-rce-cve-2023-38408
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: node@18.16.1-bookworm › zlib/zlib1g@1:1.2.13.dfsg-1
-
Introduced through: node@18.16.1-bookworm › 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
- 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://www.winimage.com/zLibDll/minizip.html
- http://www.openwall.com/lists/oss-security/2023/10/20/9
- https://lists.debian.org/debian-lts-announce/2023/11/msg00026.html
- https://security.netapp.com/advisory/ntap-20231130-0009/
- https://pypi.org/project/pyminizip/#history
- https://security.gentoo.org/glsa/202401-18
- http://www.openwall.com/lists/oss-security/2024/01/24/10
critical severity
- Vulnerable module: krb5/krb5-multidev
- Introduced through: krb5/krb5-multidev@1.20.1-2, krb5/libgssapi-krb5-2@1.20.1-2 and others
- Fixed in: 1.20.1-2+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › krb5/krb5-multidev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssapi-krb5-2@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssrpc4@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libk5crypto3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5clnt-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5srv-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkdb5-10@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-dev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5support0@1.20.1-2
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.
In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u2 or higher.
References
critical severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › git@1:2.39.2-1.1
-
Introduced through: node@18.16.1-bookworm › git/git-man@1:2.39.2-1.1
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 revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a .git/ directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. As always, it is best to avoid cloning repositories from untrusted sources.
Remediation
There is no fixed version for Debian:12 git.
References
- https://security-tracker.debian.org/tracker/CVE-2024-32002
- https://git-scm.com/docs/git-clone#Documentation/git-clone.txt---recurse-submodulesltpathspecgt
- https://git-scm.com/docs/git-config#Documentation/git-config.txt-coresymlinks
- https://github.com/git/git/commit/97065761333fd62db1912d81b489db938d8c991d
- https://github.com/git/git/security/advisories/GHSA-8h77-4q3w-gfgv
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
high severity
- Vulnerable module: libde265/libde265-0
- Introduced through: libde265/libde265-0@1.0.11-1
- Fixed in: 1.0.11-1+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libde265/libde265-0@1.0.11-1
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.
Libde265 v1.0.11 was discovered to contain a heap buffer overflow via the function derive_collocated_motion_vectors at motion.cc.
Remediation
Upgrade Debian:12 libde265 to version 1.0.11-1+deb12u1 or higher.
References
high severity
- Vulnerable module: libde265/libde265-0
- Introduced through: libde265/libde265-0@1.0.11-1
- Fixed in: 1.0.11-1+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libde265/libde265-0@1.0.11-1
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.
Libde265 v1.0.14 was discovered to contain a global buffer overflow vulnerability in the read_coding_unit function at slice.cc.
Remediation
Upgrade Debian:12 libde265 to version 1.0.11-1+deb12u2 or higher.
References
high severity
- Vulnerable module: libde265/libde265-0
- Introduced through: libde265/libde265-0@1.0.11-1
- Fixed in: 1.0.11-1+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libde265/libde265-0@1.0.11-1
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.
Libde265 v1.0.14 was discovered to contain a heap-buffer-overflow vulnerability in the derive_combined_bipredictive_merging_candidates function at motion.cc.
Remediation
Upgrade Debian:12 libde265 to version 1.0.11-1+deb12u2 or higher.
References
high severity
- Vulnerable module: libde265/libde265-0
- Introduced through: libde265/libde265-0@1.0.11-1
- Fixed in: 1.0.11-1+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libde265/libde265-0@1.0.11-1
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.
Libde265 v1.0.14 was discovered to contain a heap-buffer-overflow vulnerability in the derive_spatial_luma_vector_prediction function at motion.cc.
Remediation
Upgrade Debian:12 libde265 to version 1.0.11-1+deb12u2 or higher.
References
high severity
- Vulnerable module: libwebp/libwebp-dev
- Introduced through: libwebp/libwebp-dev@1.2.4-0.2, libwebp/libwebp7@1.2.4-0.2 and others
- Fixed in: 1.2.4-0.2+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libwebp/libwebp-dev@1.2.4-0.2
-
Introduced through: node@18.16.1-bookworm › libwebp/libwebp7@1.2.4-0.2
-
Introduced through: node@18.16.1-bookworm › libwebp/libwebpdemux2@1.2.4-0.2
-
Introduced through: node@18.16.1-bookworm › libwebp/libwebpmux3@1.2.4-0.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libwebp package and not the libwebp package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical)
Remediation
Upgrade Debian:12 libwebp to version 1.2.4-0.2+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4863
- https://adamcaudill.com/2023/09/14/whose-cve-is-it-anyway/
- https://bugzilla.suse.com/show_bug.cgi?id=1215231
- https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
- https://crbug.com/1479274
- https://en.bandisoft.com/honeyview/history/
- https://github.com/webmproject/libwebp/commit/902bc9190331343b2017211debcec8d2ab87e17a
- https://github.com/webmproject/libwebp/releases/tag/v1.3.2
- https://lists.debian.org/debian-lts-announce/2023/09/msg00015.html
- https://lists.debian.org/debian-lts-announce/2023/09/msg00016.html
- https://lists.debian.org/debian-lts-announce/2023/09/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6T655QF7CQ3DYAMPFV7IECQYGDEUIVVT/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FYYKLG6CRGEDTNRBSU26EEWAO6D6U645/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OZDGWWMJREPAGKWCJKSCM4WYLANSKIFX/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PYZV7TMKF4QHZ54SFJX54BDN52VHGGCX/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WHOLML7N2G5KCAZXFWC5IDFFHSQS5SDB/
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-4863
- https://news.ycombinator.com/item?id=37478403
- https://security.gentoo.org/glsa/202309-05
- https://stackdiary.com/critical-vulnerability-in-webp-codec-cve-2023-4863/
- https://www.bleepingcomputer.com/news/google/google-fixes-another-chrome-zero-day-bug-exploited-in-attacks/
- https://www.debian.org/security/2023/dsa-5496
- https://www.debian.org/security/2023/dsa-5497
- https://www.debian.org/security/2023/dsa-5498
- https://www.mozilla.org/en-US/security/advisories/mfsa2023-40/
- http://www.openwall.com/lists/oss-security/2023/09/21/4
- http://www.openwall.com/lists/oss-security/2023/09/22/1
- http://www.openwall.com/lists/oss-security/2023/09/22/3
- http://www.openwall.com/lists/oss-security/2023/09/22/4
- http://www.openwall.com/lists/oss-security/2023/09/22/5
- http://www.openwall.com/lists/oss-security/2023/09/22/6
- http://www.openwall.com/lists/oss-security/2023/09/22/7
- http://www.openwall.com/lists/oss-security/2023/09/22/8
- http://www.openwall.com/lists/oss-security/2023/09/26/1
- http://www.openwall.com/lists/oss-security/2023/09/26/7
- http://www.openwall.com/lists/oss-security/2023/09/28/1
- http://www.openwall.com/lists/oss-security/2023/09/28/2
- http://www.openwall.com/lists/oss-security/2023/09/28/4
- https://blog.isosceles.com/the-webp-0day/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KUQ7CTX3W372X3UY56VVNAHCH6H2F4X3/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WTRUIS3564P7ZLM2S2IH4Y4KZ327LI4I/
- https://security.gentoo.org/glsa/202401-10
- https://security.netapp.com/advisory/ntap-20230929-0011/
- https://sethmlarson.dev/security-developer-in-residence-weekly-report-16
- https://www.bentley.com/advisories/be-2023-0001/
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
high severity
- Vulnerable module: postgresql-15/libpq-dev
- Introduced through: postgresql-15/libpq-dev@15.3-0+deb12u1 and postgresql-15/libpq5@15.3-0+deb12u1
- Fixed in: 15.5-0+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq-dev@15.3-0+deb12u1
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq5@15.3-0+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream postgresql-15 package and not the postgresql-15 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in PostgreSQL that allows authenticated database users to execute arbitrary code through missing overflow checks during SQL array value modification. This issue exists due to an integer overflow during array modification where a remote user can trigger the overflow by providing specially crafted data. This enables the execution of arbitrary code on the target system, allowing users to write arbitrary bytes to memory and extensively read the server's memory.
Remediation
Upgrade Debian:12 postgresql-15 to version 15.5-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-5869
- https://access.redhat.com/errata/RHSA-2023:7545
- https://access.redhat.com/errata/RHSA-2023:7579
- https://access.redhat.com/errata/RHSA-2023:7580
- https://access.redhat.com/errata/RHSA-2023:7581
- https://access.redhat.com/errata/RHSA-2023:7616
- https://access.redhat.com/errata/RHSA-2023:7656
- https://access.redhat.com/errata/RHSA-2023:7666
- https://access.redhat.com/errata/RHSA-2023:7667
- https://access.redhat.com/errata/RHSA-2023:7694
- https://access.redhat.com/errata/RHSA-2023:7695
- https://access.redhat.com/errata/RHSA-2023:7714
- https://access.redhat.com/errata/RHSA-2023:7770
- https://access.redhat.com/errata/RHSA-2023:7771
- https://access.redhat.com/errata/RHSA-2023:7772
- https://access.redhat.com/errata/RHSA-2023:7778
- https://access.redhat.com/errata/RHSA-2023:7783
- https://access.redhat.com/security/cve/CVE-2023-5869
- https://bugzilla.redhat.com/show_bug.cgi?id=2247169
- https://www.postgresql.org/about/news/postgresql-161-155-1410-1313-1217-and-1122-released-2749/
- https://www.postgresql.org/support/security/CVE-2023-5869/
- https://access.redhat.com/errata/RHSA-2023:7784
- https://access.redhat.com/errata/RHSA-2023:7785
- https://access.redhat.com/errata/RHSA-2023:7786
- https://access.redhat.com/errata/RHSA-2023:7788
- https://access.redhat.com/errata/RHSA-2023:7789
- https://access.redhat.com/errata/RHSA-2023:7790
- https://access.redhat.com/errata/RHSA-2023:7878
- https://access.redhat.com/errata/RHSA-2023:7883
- https://access.redhat.com/errata/RHSA-2023:7884
- https://access.redhat.com/errata/RHSA-2023:7885
- https://access.redhat.com/errata/RHSA-2024:0304
- https://security.netapp.com/advisory/ntap-20240119-0003/
- https://access.redhat.com/errata/RHSA-2024:0332
- https://access.redhat.com/errata/RHSA-2024:0337
high severity
- Vulnerable module: postgresql-15/libpq-dev
- Introduced through: postgresql-15/libpq-dev@15.3-0+deb12u1 and postgresql-15/libpq5@15.3-0+deb12u1
- Fixed in: 15.5-0+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq-dev@15.3-0+deb12u1
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq5@15.3-0+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream postgresql-15 package and not the postgresql-15 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
IN THE EXTENSION SCRIPT, a SQL Injection vulnerability was found in PostgreSQL if it uses @extowner@, @extschema@, or @extschema:...@ inside a quoting construct (dollar quoting, '', or ""). If an administrator has installed files of a vulnerable, trusted, non-bundled extension, an attacker with database-level CREATE privilege can execute arbitrary code as the bootstrap superuser.
Remediation
Upgrade Debian:12 postgresql-15 to version 15.5-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-39417
- https://access.redhat.com/security/cve/CVE-2023-39417
- https://bugzilla.redhat.com/show_bug.cgi?id=2228111
- https://www.postgresql.org/support/security/CVE-2023-39417
- https://lists.debian.org/debian-lts-announce/2023/10/msg00003.html
- https://security.netapp.com/advisory/ntap-20230915-0002/
- https://access.redhat.com/errata/RHSA-2023:7545
- https://access.redhat.com/errata/RHSA-2023:7579
- https://access.redhat.com/errata/RHSA-2023:7580
- https://access.redhat.com/errata/RHSA-2023:7581
- https://access.redhat.com/errata/RHSA-2023:7616
- https://access.redhat.com/errata/RHSA-2023:7656
- https://access.redhat.com/errata/RHSA-2023:7666
- https://access.redhat.com/errata/RHSA-2023:7667
- https://access.redhat.com/errata/RHSA-2023:7694
- https://access.redhat.com/errata/RHSA-2023:7695
- https://access.redhat.com/errata/RHSA-2023:7714
- https://access.redhat.com/errata/RHSA-2023:7770
- https://access.redhat.com/errata/RHSA-2023:7772
- https://access.redhat.com/errata/RHSA-2023:7784
- https://access.redhat.com/errata/RHSA-2023:7785
- https://access.redhat.com/errata/RHSA-2023:7883
- https://access.redhat.com/errata/RHSA-2023:7884
- https://access.redhat.com/errata/RHSA-2023:7885
- https://access.redhat.com/errata/RHSA-2024:0304
- https://access.redhat.com/errata/RHSA-2024:0332
- https://access.redhat.com/errata/RHSA-2024:0337
- https://www.debian.org/security/2023/dsa-5553
- https://www.debian.org/security/2023/dsa-5554
high severity
- Vulnerable module: libde265/libde265-0
- Introduced through: libde265/libde265-0@1.0.11-1
- Fixed in: 1.0.11-1+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libde265/libde265-0@1.0.11-1
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.
Libde265 v1.0.12 was discovered to contain multiple buffer overflows via the num_tile_columns and num_tile_row parameters in the function pic_parameter_set::dump.
Remediation
Upgrade Debian:12 libde265 to version 1.0.11-1+deb12u1 or higher.
References
high severity
- Vulnerable module: node
- Introduced through: node@18.16.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Code Injection due to the incorrect handling of environment variables on Linux when the process is running with elevated privileges that the current user lacks (does not apply to CAP_NET_BIND_SERVICE).
Remediation
Upgrade node to version 18.19.1, 20.11.1, 21.6.2 or higher.
References
high severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2
- Fixed in: 1:9.2p1-2+deb12u3
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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.
A security regression (CVE-2006-5051) was discovered in OpenSSH's server (sshd). There is a race condition which can lead sshd to handle some signals in an unsafe manner. An unauthenticated, remote attacker may be able to trigger it by failing to authenticate within a set time period.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-6387
- https://access.redhat.com/errata/RHSA-2024:4312
- https://access.redhat.com/security/cve/CVE-2024-6387
- https://archlinux.org/news/the-sshd-service-needs-to-be-restarted-after-upgrading-to-openssh-98p1/
- https://arstechnica.com/security/2024/07/regresshion-vulnerability-in-openssh-gives-attackers-root-on-linux/
- https://blog.qualys.com/vulnerabilities-threat-research/2024/07/01/regresshion-remote-unauthenticated-code-execution-vulnerability-in-openssh-server
- https://explore.alas.aws.amazon.com/CVE-2024-6387.html
- https://ftp.netbsd.org/pub/NetBSD/security/advisories/NetBSD-SA2024-002.txt.asc
- https://github.com/zgzhang/cve-2024-6387-poc
- https://lists.mindrot.org/pipermail/openssh-unix-announce/2024-July/000158.html
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2024-0010
- https://security.netapp.com/advisory/ntap-20240701-0001/
- https://sig-security.rocky.page/issues/CVE-2024-6387/
- https://stackdiary.com/openssh-race-condition-in-sshd-allows-remote-code-execution/
- https://ubuntu.com/security/CVE-2024-6387
- https://ubuntu.com/security/notices/USN-6859-1
- https://www.freebsd.org/security/advisories/FreeBSD-SA-24:04.openssh.asc
- https://www.qualys.com/2024/07/01/cve-2024-6387/regresshion.txt
- https://www.suse.com/security/cve/CVE-2024-6387.html
- https://www.theregister.com/2024/07/01/regresshion_openssh/
- http://www.openwall.com/lists/oss-security/2024/07/01/12
- http://www.openwall.com/lists/oss-security/2024/07/01/13
- http://www.openwall.com/lists/oss-security/2024/07/02/1
- http://www.openwall.com/lists/oss-security/2024/07/03/1
- http://www.openwall.com/lists/oss-security/2024/07/03/11
- http://www.openwall.com/lists/oss-security/2024/07/03/2
- http://www.openwall.com/lists/oss-security/2024/07/03/3
- http://www.openwall.com/lists/oss-security/2024/07/03/4
- http://www.openwall.com/lists/oss-security/2024/07/03/5
- http://www.openwall.com/lists/oss-security/2024/07/04/1
- http://www.openwall.com/lists/oss-security/2024/07/04/2
- http://www.openwall.com/lists/oss-security/2024/07/08/2
- http://www.openwall.com/lists/oss-security/2024/07/08/3
- http://www.openwall.com/lists/oss-security/2024/07/09/2
- http://www.openwall.com/lists/oss-security/2024/07/09/5
- http://www.openwall.com/lists/oss-security/2024/07/10/1
- http://www.openwall.com/lists/oss-security/2024/07/10/2
- http://www.openwall.com/lists/oss-security/2024/07/10/3
- http://www.openwall.com/lists/oss-security/2024/07/10/4
- http://www.openwall.com/lists/oss-security/2024/07/10/6
- http://www.openwall.com/lists/oss-security/2024/07/11/1
- http://www.openwall.com/lists/oss-security/2024/07/11/3
- http://www.openwall.com/lists/oss-security/2024/07/23/4
- http://www.openwall.com/lists/oss-security/2024/07/23/6
- https://access.redhat.com/errata/RHSA-2024:4340
- https://access.redhat.com/errata/RHSA-2024:4389
- https://access.redhat.com/errata/RHSA-2024:4469
- https://access.redhat.com/errata/RHSA-2024:4474
- https://access.redhat.com/errata/RHSA-2024:4479
- https://access.redhat.com/errata/RHSA-2024:4484
- https://bugzilla.redhat.com/show_bug.cgi?id=2294604
- https://forum.vmssoftware.com/viewtopic.php?f=8&t=9132
- https://github.com/AlmaLinux/updates/issues/629
- https://github.com/Azure/AKS/issues/4379
- https://github.com/PowerShell/Win32-OpenSSH/discussions/2248
- https://github.com/PowerShell/Win32-OpenSSH/issues/2249
- https://github.com/microsoft/azurelinux/issues/9555
- https://github.com/openela-main/openssh/commit/e1f438970e5a337a17070a637c1b9e19697cad09
- https://github.com/oracle/oracle-linux/issues/149
- https://github.com/rapier1/hpn-ssh/issues/87
- https://lists.almalinux.org/archives/list/announce@lists.almalinux.org/thread/23BF5BMGFVEVUI2WNVAGMLKT557EU7VY/
- https://lists.mindrot.org/pipermail/openssh-unix-dev/2024-July/041431.html
- https://news.ycombinator.com/item?id=40843778
- https://www.akamai.com/blog/security-research/2024-openssh-vulnerability-regression-what-to-know-and-do
- https://www.arista.com/en/support/advisories-notices/security-advisory/19904-security-advisory-0100
- https://www.openssh.com/txt/release-9.8
- https://www.splunk.com/en_us/blog/security/cve-2024-6387-regresshion-vulnerability.html
- http://www.openwall.com/lists/oss-security/2024/07/28/2
- http://www.openwall.com/lists/oss-security/2024/07/28/3
- https://santandersecurityresearch.github.io/blog/sshing_the_masses.html
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
high severity
- Vulnerable module: postgresql-15/libpq-dev
- Introduced through: postgresql-15/libpq-dev@15.3-0+deb12u1 and postgresql-15/libpq5@15.3-0+deb12u1
- Fixed in: 15.6-0+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq-dev@15.3-0+deb12u1
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq5@15.3-0+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream postgresql-15 package and not the postgresql-15 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Late privilege drop in REFRESH MATERIALIZED VIEW CONCURRENTLY in PostgreSQL allows an object creator to execute arbitrary SQL functions as the command issuer. The command intends to run SQL functions as the owner of the materialized view, enabling safe refresh of untrusted materialized views. The victim is a superuser or member of one of the attacker's roles. The attack requires luring the victim into running REFRESH MATERIALIZED VIEW CONCURRENTLY on the attacker's materialized view. Versions before PostgreSQL 16.2, 15.6, 14.11, 13.14, and 12.18 are affected.
Remediation
Upgrade Debian:12 postgresql-15 to version 15.6-0+deb12u1 or higher.
References
high severity
- Vulnerable module: gdk-pixbuf/gir1.2-gdkpixbuf-2.0
- Introduced through: gdk-pixbuf/gir1.2-gdkpixbuf-2.0@2.42.10+dfsg-1+b1, gdk-pixbuf/libgdk-pixbuf-2.0-0@2.42.10+dfsg-1+b1 and others
- Fixed in: 2.42.10+dfsg-1+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › gdk-pixbuf/gir1.2-gdkpixbuf-2.0@2.42.10+dfsg-1+b1
-
Introduced through: node@18.16.1-bookworm › gdk-pixbuf/libgdk-pixbuf-2.0-0@2.42.10+dfsg-1+b1
-
Introduced through: node@18.16.1-bookworm › gdk-pixbuf/libgdk-pixbuf-2.0-dev@2.42.10+dfsg-1+b1
-
Introduced through: node@18.16.1-bookworm › gdk-pixbuf/libgdk-pixbuf2.0-bin@2.42.10+dfsg-1+b1
-
Introduced through: node@18.16.1-bookworm › gdk-pixbuf/libgdk-pixbuf2.0-common@2.42.10+dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gdk-pixbuf package and not the gdk-pixbuf package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In GNOME GdkPixbuf (aka gdk-pixbuf) through 2.42.10, the ANI (Windows animated cursor) decoder encounters heap memory corruption (in ani_load_chunk in io-ani.c) when parsing chunks in a crafted .ani file. A crafted file could allow an attacker to overwrite heap metadata, leading to a denial of service or code execution attack. This occurs in gdk_pixbuf_set_option() in gdk-pixbuf.c.
Remediation
Upgrade Debian:12 gdk-pixbuf to version 2.42.10+dfsg-1+deb12u1 or higher.
References
high severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9, glibc/libc-dev-bin@2.36-9 and others
- Fixed in: 2.36-9+deb12u3
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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.
A buffer overflow was discovered in the GNU C Library's dynamic loader ld.so while processing the GLIBC_TUNABLES environment variable. This issue could allow a local attacker to use maliciously crafted GLIBC_TUNABLES environment variables when launching binaries with SUID permission to execute code with elevated privileges.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4911
- http://www.openwall.com/lists/oss-security/2023/10/03/2
- http://www.openwall.com/lists/oss-security/2023/10/03/3
- http://www.openwall.com/lists/oss-security/2023/10/05/1
- https://access.redhat.com/errata/RHSA-2023:5453
- https://access.redhat.com/errata/RHSA-2023:5454
- https://access.redhat.com/errata/RHSA-2023:5455
- https://access.redhat.com/security/cve/CVE-2023-4911
- https://bugzilla.redhat.com/show_bug.cgi?id=2238352
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4DBUQRRPB47TC3NJOUIBVWUGFHBJAFDL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DFG4P76UHHZEWQ26FWBXG76N2QLKKPZA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NDAQWHTSVOCOZ5K6KPIWKRT3JX4RTZUR/
- https://security.gentoo.org/glsa/202310-03
- https://www.debian.org/security/2023/dsa-5514
- https://www.qualys.com/2023/10/03/cve-2023-4911/looney-tunables-local-privilege-escalation-glibc-ld-so.txt
- https://www.qualys.com/cve-2023-4911/
- http://packetstormsecurity.com/files/174986/glibc-ld.so-Local-Privilege-Escalation.html
- http://packetstormsecurity.com/files/176288/Glibc-Tunables-Privilege-Escalation.html
- http://seclists.org/fulldisclosure/2023/Oct/11
- http://www.openwall.com/lists/oss-security/2023/10/13/11
- http://www.openwall.com/lists/oss-security/2023/10/14/3
- http://www.openwall.com/lists/oss-security/2023/10/14/5
- http://www.openwall.com/lists/oss-security/2023/10/14/6
- https://access.redhat.com/errata/RHSA-2023:5476
- https://access.redhat.com/errata/RHSA-2024:0033
- https://security.netapp.com/advisory/ntap-20231013-0006/
- https://github.com/projectdiscovery/nuclei-templates/blob/master/code/cves/2023/CVE-2023-4911.yaml
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
high severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9, glibc/libc-dev-bin@2.36-9 and others
- Fixed in: 2.36-9+deb12u4
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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.
A heap-based buffer overflow was found in the __vsyslog_internal function of the glibc library. This function is called by the syslog and vsyslog functions. This issue occurs when the openlog function was not called, or called with the ident argument set to NULL, and the program name (the basename of argv[0]) is bigger than 1024 bytes, resulting in an application crash or local privilege escalation. This issue affects glibc 2.36 and newer.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-6246
- https://access.redhat.com/security/cve/CVE-2023-6246
- https://bugzilla.redhat.com/show_bug.cgi?id=2249053
- https://www.openwall.com/lists/oss-security/2024/01/30/6
- http://packetstormsecurity.com/files/176931/glibc-qsort-Out-Of-Bounds-Read-Write.html
- http://packetstormsecurity.com/files/176932/glibc-syslog-Heap-Based-Buffer-Overflow.html
- http://seclists.org/fulldisclosure/2024/Feb/3
- http://seclists.org/fulldisclosure/2024/Feb/5
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/D2FIH77VHY3KCRROCXOT6L27WMZXSJ2G/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MWQ6BZJ6CV5UAW4VZSKJ6TO4KIW2KWAQ/
- https://security.gentoo.org/glsa/202402-01
- https://www.qualys.com/2024/01/30/cve-2023-6246/syslog.txt
- https://security.netapp.com/advisory/ntap-20240216-0007/
- https://github.com/projectdiscovery/nuclei-templates/blob/master/code/cves/2023/CVE-2023-6246.yaml
high severity
- Vulnerable module: libx11/libx11-6
- Introduced through: libx11/libx11-6@2:1.8.4-2+deb12u1, libx11/libx11-data@2:1.8.4-2+deb12u1 and others
- Fixed in: 2:1.8.4-2+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libx11/libx11-6@2:1.8.4-2+deb12u1
-
Introduced through: node@18.16.1-bookworm › libx11/libx11-data@2:1.8.4-2+deb12u1
-
Introduced through: node@18.16.1-bookworm › libx11/libx11-dev@2:1.8.4-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in libX11 due to an integer overflow within the XCreateImage() function. This flaw allows a local user to trigger an integer overflow and execute arbitrary code with elevated privileges.
Remediation
Upgrade Debian:12 libx11 to version 2:1.8.4-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-43787
- https://access.redhat.com/security/cve/CVE-2023-43787
- https://bugzilla.redhat.com/show_bug.cgi?id=2242254
- https://security.netapp.com/advisory/ntap-20231103-0006/
- http://www.openwall.com/lists/oss-security/2024/01/24/9
- https://jfrog.com/blog/xorg-libx11-vulns-cve-2023-43786-cve-2023-43787-part-two/
- https://access.redhat.com/errata/RHSA-2024:2145
- https://access.redhat.com/errata/RHSA-2024:2973
high severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7, perl/libperl5.36@5.36.0-7 and others
- Fixed in: 5.36.0-7+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › perl@5.36.0-7
-
Introduced through: node@18.16.1-bookworm › perl/libperl5.36@5.36.0-7
-
Introduced through: node@18.16.1-bookworm › perl/perl-base@5.36.0-7
-
Introduced through: node@18.16.1-bookworm › perl/perl-modules-5.36@5.36.0-7
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.
A vulnerability was found in perl 5.30.0 through 5.38.0. This issue occurs when a crafted regular expression is compiled by perl, which can allow an attacker controlled byte buffer overflow in a heap allocated buffer.
Remediation
Upgrade Debian:12 perl to version 5.36.0-7+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-47038
- https://access.redhat.com/security/cve/CVE-2023-47038
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056746
- https://bugzilla.redhat.com/show_bug.cgi?id=2249523
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNEEWAACXQCEEAKSG7XX2D5YDRWLCIZJ/
- https://perldoc.perl.org/perl5382delta#CVE-2023-47038-Write-past-buffer-end-via-illegal-user-defined-Unicode-property
- https://access.redhat.com/errata/RHSA-2024:2228
- https://access.redhat.com/errata/RHSA-2024:3128
high severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10, curl/libcurl3-gnutls@7.88.1-10 and others
- Fixed in: 7.88.1-10+deb12u3
Detailed paths
-
Introduced through: node@18.16.1-bookworm › curl@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl3-gnutls@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4-openssl-dev@7.88.1-10
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 curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.
However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endless series of headers and eventually cause curl to run out of heap memory.
Remediation
Upgrade Debian:12 curl to version 7.88.1-10+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-38039
- https://hackerone.com/reports/2072338
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TEAWTYHC3RT6ZRS5OZRHLAIENVN6CCIS/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5DCZMYODALBLVOXVJEN2LF2MLANEYL4F/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/M6KGKB2JNZVT276JYSKI6FV2VFJUGDOJ/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20231013-0005/
- https://support.apple.com/kb/HT214036
- https://support.apple.com/kb/HT214057
- https://support.apple.com/kb/HT214058
- https://support.apple.com/kb/HT214063
- https://www.insyde.com/security-pledge/SA-2023064
- http://seclists.org/fulldisclosure/2023/Oct/17
- http://seclists.org/fulldisclosure/2024/Jan/34
- http://seclists.org/fulldisclosure/2024/Jan/37
- http://seclists.org/fulldisclosure/2024/Jan/38
high severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9, glibc/libc-dev-bin@2.36-9 and others
- Fixed in: 2.36-9+deb12u4
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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.
An off-by-one heap-based buffer overflow was found in the __vsyslog_internal function of the glibc library. This function is called by the syslog and vsyslog functions. This issue occurs when these functions are called with a message bigger than INT_MAX bytes, leading to an incorrect calculation of the buffer size to store the message, resulting in an application crash. This issue affects glibc 2.37 and newer.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-6779
- http://packetstormsecurity.com/files/176932/glibc-syslog-Heap-Based-Buffer-Overflow.html
- http://seclists.org/fulldisclosure/2024/Feb/3
- https://access.redhat.com/security/cve/CVE-2023-6779
- https://bugzilla.redhat.com/show_bug.cgi?id=2254395
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/D2FIH77VHY3KCRROCXOT6L27WMZXSJ2G/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MWQ6BZJ6CV5UAW4VZSKJ6TO4KIW2KWAQ/
- https://security.gentoo.org/glsa/202402-01
- https://www.openwall.com/lists/oss-security/2024/01/30/6
- https://security.netapp.com/advisory/ntap-20240223-0006/
- https://www.qualys.com/2024/01/30/cve-2023-6246/syslog.txt
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2
- Fixed in: 3.7.9-2+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › gnutls28/libgnutls30@3.7.9-2
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.
A vulnerability was found in GnuTLS, where a cockpit (which uses gnuTLS) rejects a certificate chain with distributed trust. This issue occurs when validating a certificate chain with cockpit-certificate-ensure. This flaw allows an unauthenticated, remote client or attacker to initiate a denial of service attack.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-0567
- http://www.openwall.com/lists/oss-security/2024/01/19/3
- https://access.redhat.com/security/cve/CVE-2024-0567
- https://bugzilla.redhat.com/show_bug.cgi?id=2258544
- https://gitlab.com/gnutls/gnutls/-/issues/1521
- https://lists.gnupg.org/pipermail/gnutls-help/2024-January/004841.html
- https://access.redhat.com/errata/RHSA-2024:0533
- https://access.redhat.com/errata/RHSA-2024:1082
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7ZEIOLORQ7N6WRPFXZSYDL2MC4LP7VFV/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNXKVR5YNUEBNHAHM5GSYKBZX4W2HMN2/
- https://security.netapp.com/advisory/ntap-20240202-0011/
- https://access.redhat.com/errata/RHSA-2024:1383
- https://access.redhat.com/errata/RHSA-2024:2094
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2
- Fixed in: 3.7.9-2+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › gnutls28/libgnutls30@3.7.9-2
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.
A vulnerability was found in GnuTLS. The response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from the response times of ciphertexts with correct PKCS#1 v1.5 padding. This issue may allow a remote attacker to perform a timing side-channel attack in the RSA-PSK key exchange, potentially leading to the leakage of sensitive data. CVE-2024-0553 is designated as an incomplete resolution for CVE-2023-5981.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-0553
- http://www.openwall.com/lists/oss-security/2024/01/19/3
- https://access.redhat.com/security/cve/CVE-2024-0553
- https://bugzilla.redhat.com/show_bug.cgi?id=2258412
- https://gitlab.com/gnutls/gnutls/-/issues/1522
- https://lists.gnupg.org/pipermail/gnutls-help/2024-January/004841.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNXKVR5YNUEBNHAHM5GSYKBZX4W2HMN2/
- https://access.redhat.com/errata/RHSA-2024:0533
- https://access.redhat.com/errata/RHSA-2024:0627
- https://security.netapp.com/advisory/ntap-20240202-0011/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7ZEIOLORQ7N6WRPFXZSYDL2MC4LP7VFV/
- https://access.redhat.com/errata/RHSA-2024:0796
- https://lists.debian.org/debian-lts-announce/2024/02/msg00010.html
- https://access.redhat.com/errata/RHSA-2024:1082
- https://access.redhat.com/errata/RHSA-2024:1108
- https://access.redhat.com/errata/RHSA-2024:1383
- https://access.redhat.com/errata/RHSA-2024:2094
high severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
- Fixed in: 8:6.9.11.60+dfsg-1.6+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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 heap-based buffer overflow vulnerability was found in ImageMagick in versions prior to 7.0.11-14 in ReadTIFFImage() in coders/tiff.c. This issue is due to an incorrect setting of the pixel array size, which can lead to a crash and segmentation fault.
Remediation
Upgrade Debian:12 imagemagick to version 8:6.9.11.60+dfsg-1.6+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2021-3610
- http://www.openwall.com/lists/oss-security/2023/06/05/1
- http://www.openwall.com/lists/oss-security/2023/05/29/4
- https://bugzilla.redhat.com/show_bug.cgi?id=1973689
- https://github.com/ImageMagick/ImageMagick/commit/930ff0d1a9bc42925a7856e9ea53f5fc9f318bf3
high severity
- Vulnerable module: krb5/krb5-multidev
- Introduced through: krb5/krb5-multidev@1.20.1-2, krb5/libgssapi-krb5-2@1.20.1-2 and others
- Fixed in: 1.20.1-2+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › krb5/krb5-multidev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssapi-krb5-2@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssrpc4@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libk5crypto3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5clnt-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5srv-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkdb5-10@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-dev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5support0@1.20.1-2
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.
In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can modify the plaintext Extra Count field of a confidential GSS krb5 wrap token, causing the unwrapped token to appear truncated to the application.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u2 or higher.
References
high severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.2 and libxml2/libxml2-dev@2.9.14+dfsg-1.2
- Fixed in: 2.9.14+dfsg-1.3~deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libxml2@2.9.14+dfsg-1.2
-
Introduced through: node@18.16.1-bookworm › libxml2/libxml2-dev@2.9.14+dfsg-1.2
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.
NULL Pointer Dereference allows attackers to cause a denial of service (or application crash). This only applies when lxml is used together with libxml2 2.9.10 through 2.9.14. libxml2 2.9.9 and earlier are not affected. It allows triggering crashes through forged input data, given a vulnerable code sequence in the application. The vulnerability is caused by the iterwalk function (also used by the canonicalize function). Such code shouldn't be in wide-spread use, given that parsing + iterwalk would usually be replaced with the more efficient iterparse function. However, an XML converter that serialises to C14N would also be vulnerable, for example, and there are legitimate use cases for this code sequence. If untrusted input is received (also remotely) and processed via iterwalk function, a crash can be triggered.
Remediation
Upgrade Debian:12 libxml2 to version 2.9.14+dfsg-1.3~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-2309
- https://github.com/lxml/lxml/commit/86368e9cf70a0ad23cccd5ee32de847149af0c6f
- https://huntr.dev/bounties/8264e74f-edda-4c40-9956-49de635105ba
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HGYC6L7ENH5VEGN3YWFBYMGKX6WNS7HZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/URHHSIBTPTALXMECRLAC2EVDNAFSR5NO/
- https://security.gentoo.org/glsa/202208-06
- https://security.netapp.com/advisory/ntap-20220915-0006/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HGYC6L7ENH5VEGN3YWFBYMGKX6WNS7HZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/URHHSIBTPTALXMECRLAC2EVDNAFSR5NO/
high severity
- Vulnerable module: nghttp2/libnghttp2-14
- Introduced through: nghttp2/libnghttp2-14@1.52.0-1
- Fixed in: 1.52.0-1+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › nghttp2/libnghttp2-14@1.52.0-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
Remediation
Upgrade Debian:12 nghttp2 to version 1.52.0-1+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-44487
- https://chaos.social/@icing/111210915918780532
- https://github.com/hyperium/hyper/issues/3337
- http://www.openwall.com/lists/oss-security/2023/10/13/4
- https://access.redhat.com/security/cve/cve-2023-44487
- https://blog.cloudflare.com/technical-breakdown-http2-rapid-reset-ddos-attack/
- https://blog.cloudflare.com/zero-day-rapid-reset-http2-record-breaking-ddos-attack/
- https://blog.litespeedtech.com/2023/10/11/rapid-reset-http-2-vulnerablilty/
- https://blog.vespa.ai/cve-2023-44487/
- https://bugzilla.redhat.com/show_bug.cgi?id=2242803
- https://cloud.google.com/blog/products/identity-security/google-cloud-mitigated-largest-ddos-attack-peaking-above-398-million-rps/
- https://cloud.google.com/blog/products/identity-security/how-it-works-the-novel-http2-rapid-reset-ddos-attack
- https://community.traefik.io/t/is-traefik-vulnerable-to-cve-2023-44487/20125
- https://forums.swift.org/t/swift-nio-http2-security-update-cve-2023-44487-http-2-dos/67764
- https://github.com/Azure/AKS/issues/3947
- https://github.com/Kong/kong/discussions/11741
- https://github.com/akka/akka-http/issues/4323
- https://github.com/apache/apisix/issues/10320
- https://github.com/apache/httpd-site/pull/10
- https://github.com/h2o/h2o/security/advisories/GHSA-2m7v-gc89-fjqf
- https://github.com/junkurihara/rust-rpxy/issues/97
- https://github.com/linkerd/website/pull/1695/commits/4b9c6836471bc8270ab48aae6fd2181bc73fd632
- https://github.com/ninenines/cowboy/issues/1615
- https://github.com/nodejs/node/pull/50121
- https://github.com/openresty/openresty/issues/930
- https://github.com/tempesta-tech/tempesta/issues/1986
- https://github.com/varnishcache/varnish-cache/issues/3996
- https://istio.io/latest/news/security/istio-security-2023-004/
- https://my.f5.com/manage/s/article/K000137106
- https://openssf.org/blog/2023/10/10/http-2-rapid-reset-vulnerability-highlights-need-for-rapid-response/
- https://seanmonstar.com/post/730794151136935936/hyper-http2-rapid-reset-unaffected
- https://security.paloaltonetworks.com/CVE-2023-44487
- https://ubuntu.com/security/CVE-2023-44487
- https://www.bleepingcomputer.com/news/security/new-http-2-rapid-reset-zero-day-attack-breaks-ddos-records/
- https://www.cisa.gov/news-events/alerts/2023/10/10/http2-rapid-reset-vulnerability-cve-2023-44487
- https://www.debian.org/security/2023/dsa-5521
- https://www.debian.org/security/2023/dsa-5522
- https://www.haproxy.com/blog/haproxy-is-not-affected-by-the-http-2-rapid-reset-attack-cve-2023-44487
- https://www.netlify.com/blog/netlify-successfully-mitigates-cve-2023-44487/
- https://www.openwall.com/lists/oss-security/2023/10/10/6
- https://www.phoronix.com/news/HTTP2-Rapid-Reset-Attack
- http://www.openwall.com/lists/oss-security/2023/10/13/9
- https://edg.io/lp/blog/resets-leaks-ddos-and-the-tale-of-a-hidden-cve
- https://gist.github.com/adulau/7c2bfb8e9cdbe4b35a5e131c66a0c088
- https://github.com/advisories/GHSA-vx74-f528-fxqg
- https://github.com/advisories/GHSA-xpw8-rcwv-8f8p
- https://github.com/alibaba/tengine/issues/1872
- https://github.com/apache/trafficserver/pull/10564
- https://github.com/bcdannyboy/CVE-2023-44487
- https://github.com/caddyserver/caddy/issues/5877
- https://github.com/dotnet/announcements/issues/277
- https://github.com/dotnet/core/blob/e4613450ea0da7fd2fc6b61dfb2c1c1dec1ce9ec/release-notes/6.0/6.0.23/6.0.23.md?plain=1#L73
- https://github.com/eclipse/jetty.project/issues/10679
- https://github.com/envoyproxy/envoy/pull/30055
- https://github.com/facebook/proxygen/pull/466
- https://github.com/golang/go/issues/63417
- https://github.com/grpc/grpc-go/pull/6703
- https://github.com/haproxy/haproxy/issues/2312
- https://github.com/icing/mod_h2/blob/0a864782af0a942aa2ad4ed960a6b32cd35bcf0a/mod_http2/README.md?plain=1#L239-L244
- https://github.com/kubernetes/kubernetes/pull/121120
- https://github.com/micrictor/http2-rst-stream
- https://github.com/microsoft/CBL-Mariner/pull/6381
- https://github.com/netty/netty/commit/58f75f665aa81a8cbcf6ffa74820042a285c5e61
- https://github.com/nghttp2/nghttp2/pull/1961
- https://github.com/opensearch-project/data-prepper/issues/3474
- https://github.com/oqtane/oqtane.framework/discussions/3367
- https://lists.apache.org/thread/5py8h42mxfsn8l1wy6o41xwhsjlsd87q
- https://msrc.microsoft.com/blog/2023/10/microsoft-response-to-distributed-denial-of-service-ddos-attacks-against-http/2/
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-44487
- https://netty.io/news/2023/10/10/4-1-100-Final.html
- https://news.ycombinator.com/item?id=37830987
- https://news.ycombinator.com/item?id=37830998
- https://news.ycombinator.com/item?id=37831062
- https://security.netapp.com/advisory/ntap-20231016-0001/
- https://tomcat.apache.org/security-10.html#Fixed_in_Apache_Tomcat_10.1.14
- https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/
- https://arstechnica.com/security/2023/10/how-ddosers-used-the-http-2-protocol-to-deliver-attacks-of-unprecedented-size/
- https://bugzilla.suse.com/show_bug.cgi?id=1216123
- https://github.com/advisories/GHSA-qppj-fm5r-hxr3
- https://github.com/arkrwn/PoC/tree/main/CVE-2023-44487
- https://github.com/etcd-io/etcd/issues/16740
- https://github.com/line/armeria/pull/5232
- https://github.com/projectcontour/contour/pull/5826
- https://linkerd.io/2023/10/12/linkerd-cve-2023-44487/
- https://lists.debian.org/debian-lts-announce/2023/10/msg00023.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00024.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JMEXY22BFG5Q64HQCM5CK2Q7KDKVV4TY/
- https://martinthomson.github.io/h2-stream-limits/draft-thomson-httpbis-h2-stream-limits.html
- https://news.ycombinator.com/item?id=37837043
- http://www.openwall.com/lists/oss-security/2023/10/18/4
- http://www.openwall.com/lists/oss-security/2023/10/18/8
- http://www.openwall.com/lists/oss-security/2023/10/19/6
- http://www.openwall.com/lists/oss-security/2023/10/20/8
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JIZSEFC3YKCGABA2BZW6ZJRMDZJMB7PJ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZKQSIKIAT5TJ3WSLU3RDBQ35YX4GY4V3/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BFQD3KUEMFBHPAPBGLWQC34L4OWL5HAZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/E72T67UPDRXHIDLO3OROR25YAMN4GGW5/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WLPRQ5TWUQQXYWBJM7ECYDAIL2YVKIUH/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZLU6U2R2IC2K64NDPNMV55AUAO65MAF4/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LKYHSZQFDNR7RSA7LHVLLIAQMVYCUGBG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/X6QXN4ORIVF6XBW4WWFE7VNPVC74S45Y/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FNA62Q767CFAFHBCDKYNPBMZWB7TWYVU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LNMZJCDHGLJJLXO4OXWJMTVQRNWOC7UL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KSEGD2IWKNUO3DWY4KQGUQM5BISRWHQE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CLB4TW7KALB3EEQWNWCN7OUIWWVWWCG2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3N4NJ7FR4X4FPZUGNTQAPSTVB2HB2Y4A/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HT7T2R4MQKLIF4ODV4BDLPARWFPCJ5CZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VHUHTSXLXGXS7JYKBXTA3VINUPHTNGVU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VSRDIV77HNKUSM7SJC5BKE5JSHLHU2NK/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XFOIBB4YFICHDM7IBOP7PWXW3FX4HLL2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZB43REMKRQR62NJEI7I5NQ4FSXNLBKRT/
- https://blog.qualys.com/vulnerabilities-threat-research/2023/10/10/cve-2023-44487-http-2-rapid-reset-attack
- https://bugzilla.proxmox.com/show_bug.cgi?id=4988
- https://cgit.freebsd.org/ports/commit/?id=c64c329c2c1752f46b73e3e6ce9f4329be6629f9
- https://discuss.hashicorp.com/t/hcsec-2023-32-vault-consul-and-boundary-affected-by-http-2-rapid-reset-denial-of-service-vulnerability-cve-2023-44487/59715
- https://github.com/apache/httpd/blob/afcdbeebbff4b0c50ea26cdd16e178c0d1f24152/modules/http2/h2_mplx.c#L1101-L1113
- https://github.com/apache/tomcat/tree/main/java/org/apache/coyote/http2
- https://github.com/caddyserver/caddy/releases/tag/v2.7.5
- https://github.com/h2o/h2o/pull/3291
- https://github.com/kazu-yamamoto/http2/commit/f61d41a502bd0f60eb24e1ce14edc7b6df6722a1
- https://github.com/kazu-yamamoto/http2/issues/93
- https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0
- https://groups.google.com/g/golang-announce/c/iNNxDTCjZvo
- https://lists.debian.org/debian-lts-announce/2023/10/msg00020.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00045.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00047.html
- https://lists.debian.org/debian-lts-announce/2023/11/msg00001.html
- https://lists.debian.org/debian-lts-announce/2023/11/msg00012.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/2MBEPPC36UBVOZZNAXFHKLFGSLCMN5LI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3N4NJ7FR4X4FPZUGNTQAPSTVB2HB2Y4A/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BFQD3KUEMFBHPAPBGLWQC34L4OWL5HAZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CLB4TW7KALB3EEQWNWCN7OUIWWVWWCG2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/E72T67UPDRXHIDLO3OROR25YAMN4GGW5/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FNA62Q767CFAFHBCDKYNPBMZWB7TWYVU/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HT7T2R4MQKLIF4ODV4BDLPARWFPCJ5CZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JIZSEFC3YKCGABA2BZW6ZJRMDZJMB7PJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JMEXY22BFG5Q64HQCM5CK2Q7KDKVV4TY/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KSEGD2IWKNUO3DWY4KQGUQM5BISRWHQE/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LKYHSZQFDNR7RSA7LHVLLIAQMVYCUGBG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LNMZJCDHGLJJLXO4OXWJMTVQRNWOC7UL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VHUHTSXLXGXS7JYKBXTA3VINUPHTNGVU/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VSRDIV77HNKUSM7SJC5BKE5JSHLHU2NK/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WE2I52RHNNU42PX6NZ2RBUHSFFJ2LVZX/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WLPRQ5TWUQQXYWBJM7ECYDAIL2YVKIUH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X6QXN4ORIVF6XBW4WWFE7VNPVC74S45Y/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XFOIBB4YFICHDM7IBOP7PWXW3FX4HLL2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZB43REMKRQR62NJEI7I5NQ4FSXNLBKRT/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZKQSIKIAT5TJ3WSLU3RDBQ35YX4GY4V3/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZLU6U2R2IC2K64NDPNMV55AUAO65MAF4/
- https://lists.w3.org/Archives/Public/ietf-http-wg/2023OctDec/0025.html
- https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html
- https://security.gentoo.org/glsa/202311-09
- https://www.darkreading.com/cloud/internet-wide-zero-day-bug-fuels-largest-ever-ddos-event
- https://www.debian.org/security/2023/dsa-5540
- https://www.debian.org/security/2023/dsa-5549
- https://www.debian.org/security/2023/dsa-5558
- https://www.theregister.com/2023/10/10/http2_rapid_reset_zeroday/
- https://www.debian.org/security/2023/dsa-5570
- https://aws.amazon.com/security/security-bulletins/AWS-2023-011/
- https://security.netapp.com/advisory/ntap-20240426-0007/
- https://security.netapp.com/advisory/ntap-20240621-0006/
- https://security.netapp.com/advisory/ntap-20240621-0007/
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
high severity
- Vulnerable module: node
- Introduced through: node@18.16.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to a lack of safeguards on chunk extension bytes. The server may read an unbounded number of bytes from a single connection, which allows an attacker to cause denial of service via CPU and network bandwidth exhaustion.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade node to version 18.19.1, 20.11.1, 21.6.2 or higher.
References
high severity
- Vulnerable module: node
- Introduced through: node@18.16.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to a race condition in Http2Session when nghttp2 data is left in memory after a connection is reset while processing HTTP/2 CONTINUATION frames. An attacker can cause denial of service by sending such frames then triggering the Http2Session destructor.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade node to version 18.20.1, 20.12.1, 21.7.2 or higher.
References
high severity
- Vulnerable module: node
- Introduced through: node@18.16.1
- Fixed in: 18.17.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Arbitrary Code Injection. The use of the deprecated API process.binding() can bypass the policy mechanism by requiring internal modules and eventually take advantage of process.binding('spawn_sync') to run arbitrary code, outside of the limits defined in a policy.json file.
Note:
At the time this advisory was issued, the policy is an experimental feature of Node.js, which is not enabled by default.
Remediation
Upgrade node to version 16.20.2, 18.17.1, 20.5.1 or higher.
References
high severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.9-1, openssl/libssl-dev@3.0.9-1 and others
- Fixed in: 3.0.11-1~deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssl@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl-dev@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl3@3.0.9-1
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 bug has been identified in the processing of key and initialisation vector (IV) lengths. This can lead to potential truncation or overruns during the initialisation of some symmetric ciphers.
Impact summary: A truncation in the IV can result in non-uniqueness, which could result in loss of confidentiality for some cipher modes.
When calling EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() or EVP_CipherInit_ex2() the provided OSSL_PARAM array is processed after the key and IV have been established. Any alterations to the key length, via the "keylen" parameter or the IV length, via the "ivlen" parameter, within the OSSL_PARAM array will not take effect as intended, potentially causing truncation or overreading of these values. The following ciphers and cipher modes are impacted: RC2, RC4, RC5, CCM, GCM and OCB.
For the CCM, GCM and OCB cipher modes, truncation of the IV can result in loss of confidentiality. For example, when following NIST's SP 800-38D section 8.2.1 guidance for constructing a deterministic IV for AES in GCM mode, truncation of the counter portion could lead to IV reuse.
Both truncations and overruns of the key and overruns of the IV will produce incorrect results and could, in some cases, trigger a memory exception. However, these issues are not currently assessed as security critical.
Changing the key and/or IV lengths is not considered to be a common operation and the vulnerable API was recently introduced. Furthermore it is likely that application developers will have spotted this problem during testing since decryption would fail unless both peers in the communication were similarly vulnerable. For these reasons we expect the probability of an application being vulnerable to this to be quite low. However if an application is vulnerable then this issue is considered very serious. For these reasons we have assessed this issue as Moderate severity overall.
The OpenSSL SSL/TLS implementation is not affected by this issue.
The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this because the issue lies outside of the FIPS provider boundary.
OpenSSL 3.1 and 3.0 are vulnerable to this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.11-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-5363
- http://www.openwall.com/lists/oss-security/2023/10/24/1
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=0df40630850fb2740e6be6890bb905d3fc623b2d
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=5f69f5c65e483928c4b28ed16af6e5742929f1ee
- https://security.netapp.com/advisory/ntap-20231027-0010/
- https://www.debian.org/security/2023/dsa-5532
- https://www.openssl.org/news/secadv/20231024.txt
- https://security.netapp.com/advisory/ntap-20240201-0003/
- https://security.netapp.com/advisory/ntap-20240201-0004/
high severity
new
- Vulnerable module: postgresql-15/libpq-dev
- Introduced through: postgresql-15/libpq-dev@15.3-0+deb12u1 and postgresql-15/libpq5@15.3-0+deb12u1
- Fixed in: 15.8-0+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq-dev@15.3-0+deb12u1
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq5@15.3-0+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream postgresql-15 package and not the postgresql-15 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Time-of-check Time-of-use (TOCTOU) race condition in pg_dump in PostgreSQL allows an object creator to execute arbitrary SQL functions as the user running pg_dump, which is often a superuser. The attack involves replacing another relation type with a view or foreign table. The attack requires waiting for pg_dump to start, but winning the race condition is trivial if the attacker retains an open transaction. Versions before PostgreSQL 16.4, 15.8, 14.13, 13.16, and 12.20 are affected.
Remediation
Upgrade Debian:12 postgresql-15 to version 15.8-0+deb12u1 or higher.
References
high severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › python3.11@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/python3.11-minimal@3.11.2-6
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.
An issue in the urllib.parse component of Python before 3.11.4 allows attackers to bypass blocklisting methods by supplying a URL that starts with blank characters.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-24329
- https://github.com/python/cpython/pull/99421
- https://pointernull.com/security/python-url-parse-problem.html
- https://github.com/python/cpython/issues/102153
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6PEVICI7YNGGMSL3UCMWGE66QFLATH72/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DSL6NSOAXWBJJ67XPLSSC74MNKZF3BBO/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EM2XLZSTXG44TMFXF4E6VTGKR2MQCW3G/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/F2NY75GFDZ5T6YPN44D3VMFT5SUVTOTG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GR5US3BYILYJ4SKBV6YBNPRUBAL5P2CN/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/H23OSKC6UG6IWOQAUPW74YUHWRWVXJP7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JZTLGV2HYFF4AMYJL25VDIGAIHCU7UPA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LWC4WGXER5P6Q75RFGL7QUTPP3N5JR7T/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MZEHSXSCMA4WWQKXT6QV7AAR6SWNZ2VP/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/O5SP4RT3RRS434ZS2HQKQJ3VZW7YPKYR/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OHHJHJRLEF3TDT2K3676CAUVRDD4CCMR/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PEUN6T22UJFXR7J5F6UUHCXXPKJ2DVHI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PURM5CFDABEWAIWZFD2MQ7ZJGCPYSQ44/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Q3J5N24ECS4B6MJDRO6UAYU6GPLYBDCL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QRQHN7RWJQJHYP6E5EKESOYP5VDSHZG4/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RA2MBEEES6L46OD64OBSVUUMGKNGMOWW/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T4IDB5OAR5Y4UK3HLMZBW4WEL2B7YFMJ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TZH26JGNZ5XYPZ5SAU3NKSBSPRE5OHTG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U2MZOJYGFCB5PPT6AKMAU72N7QOYWLBP/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UONZWLB4QVLQIY5CPDLEUEKH6WX4VQMC/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WTOAUJNDWZDRWVSXJ354AYZYKRMT56HU/
- https://security.netapp.com/advisory/ntap-20230324-0004/
- https://www.kb.cert.org/vuls/id/127587
- https://lists.debian.org/debian-lts-announce/2023/09/msg00022.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6PEVICI7YNGGMSL3UCMWGE66QFLATH72/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DSL6NSOAXWBJJ67XPLSSC74MNKZF3BBO/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EM2XLZSTXG44TMFXF4E6VTGKR2MQCW3G/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/F2NY75GFDZ5T6YPN44D3VMFT5SUVTOTG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GR5US3BYILYJ4SKBV6YBNPRUBAL5P2CN/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/H23OSKC6UG6IWOQAUPW74YUHWRWVXJP7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JZTLGV2HYFF4AMYJL25VDIGAIHCU7UPA/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LWC4WGXER5P6Q75RFGL7QUTPP3N5JR7T/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MZEHSXSCMA4WWQKXT6QV7AAR6SWNZ2VP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/O5SP4RT3RRS434ZS2HQKQJ3VZW7YPKYR/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OHHJHJRLEF3TDT2K3676CAUVRDD4CCMR/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PEUN6T22UJFXR7J5F6UUHCXXPKJ2DVHI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PURM5CFDABEWAIWZFD2MQ7ZJGCPYSQ44/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Q3J5N24ECS4B6MJDRO6UAYU6GPLYBDCL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QRQHN7RWJQJHYP6E5EKESOYP5VDSHZG4/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RA2MBEEES6L46OD64OBSVUUMGKNGMOWW/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/T4IDB5OAR5Y4UK3HLMZBW4WEL2B7YFMJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TZH26JGNZ5XYPZ5SAU3NKSBSPRE5OHTG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/U2MZOJYGFCB5PPT6AKMAU72N7QOYWLBP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UONZWLB4QVLQIY5CPDLEUEKH6WX4VQMC/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WTOAUJNDWZDRWVSXJ354AYZYKRMT56HU/
high severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › python3.11@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/python3.11-minimal@3.11.2-6
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.
An issue was discovered in Python 3.11 through 3.11.4. If a path containing '\0' bytes is passed to os.path.normpath(), the path will be truncated unexpectedly at the first '\0' byte. There are plausible cases in which an application would have rejected a filename for security reasons in Python 3.10.x or earlier, but that filename is no longer rejected in Python 3.11.x.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-41105
- https://github.com/python/cpython/issues/106242
- https://github.com/python/cpython/pull/107981
- https://github.com/python/cpython/pull/107982
- https://github.com/python/cpython/pull/107983
- https://mail.python.org/archives/list/security-announce@python.org/thread/D6CDW3ZZC5D444YGL3VQUY6D4ECMCQLD/
- https://security.netapp.com/advisory/ntap-20231006-0015/
- https://mail.python.org/archives/list/security-announce%40python.org/thread/D6CDW3ZZC5D444YGL3VQUY6D4ECMCQLD/
high severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.6-1 and systemd/libudev1@252.6-1
- Fixed in: 252.23-1~deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › systemd/libsystemd0@252.6-1
-
Introduced through: node@18.16.1-bookworm › systemd/libudev1@252.6-1
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.
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.
Remediation
Upgrade Debian:12 systemd to version 252.23-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-50387
- https://datatracker.ietf.org/doc/html/rfc4035
- http://www.openwall.com/lists/oss-security/2024/02/16/2
- http://www.openwall.com/lists/oss-security/2024/02/16/3
- https://access.redhat.com/security/cve/CVE-2023-50387
- https://bugzilla.suse.com/show_bug.cgi?id=1219823
- https://docs.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-01.html
- https://gitlab.nic.cz/knot/knot-resolver/-/releases/v5.7.1
- https://kb.isc.org/docs/cve-2023-50387
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BUIP7T7Z4T3UHLXFWG6XIVDP4GYPD3AI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNNHZSZPG2E7NBMBNYPGHCFI4V4XRWNQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SVYA42BLXUCIDLD35YIJPJSHDIADNYMP/
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-50387
- https://news.ycombinator.com/item?id=39367411
- https://news.ycombinator.com/item?id=39372384
- https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/
- https://www.athene-center.de/aktuelles/key-trap
- https://www.athene-center.de/fileadmin/content/PDF/Technical_Report_KeyTrap.pdf
- https://www.isc.org/blogs/2024-bind-security-release/
- https://www.securityweek.com/keytrap-dns-attack-could-disable-large-parts-of-internet-researchers/
- https://www.theregister.com/2024/02/13/dnssec_vulnerability_internet/
- https://lists.debian.org/debian-lts-announce/2024/02/msg00006.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TEXGOYGW7DBS3N2QSSQONZ4ENIRQEAPG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UQESRWMJCF4JEYJEAKLRM6CT55GLJAB7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HVRDSJVZKMCXKKPP6PNR62T7RWZ3YSDZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RGS7JN6FZXUSTC2XKQHH27574XOULYYJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6FV5O347JTX7P5OZA6NGO4MKTXRXMKOZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IGSLGKUAQTW5JPPZCMF5YPEYALLRUZZ6/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZDZFMEKQTZ4L7RY46FCENWFB5MDT263R/
- https://security.netapp.com/advisory/ntap-20240307-0007/
- https://lists.debian.org/debian-lts-announce/2024/05/msg00011.html
high severity
- Vulnerable module: node
- Introduced through: node@18.16.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Improper Control of Generation of Code ('Code Injection') due to the improper handling of batch files in child_process.spawn or child_process.spawnSync. An attacker can inject arbitrary commands and achieve code execution even if the shell option is not enabled.
Note: This vulnerability only affects Windows machines.
Remediation
Upgrade node to version 18.20.2, 20.12.2, 21.7.3 or higher.
References
medium severity
- Vulnerable module: node
- Introduced through: node@18.16.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Access Restriction Bypass by embedding non-network imports in data URLs. Exploiting this vulnerability allows an attacker to execute arbitrary code, compromising system security.
Remediation
Upgrade node to version 18.20.4, 20.15.1, 22.4.1 or higher.
References
medium severity
- Vulnerable module: node
- Introduced through: node@18.16.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Improper Control of Generation of Code ('Code Injection'). This is due to a bypass of CVE-2024-27980.
A malicious command line argument can inject arbitrary commands and achieve code execution even if the shell option is not enabled.
Note: This vulnerability affects only users of child_process.spawn and child_process.spawnSync on Windows in all active release lines.
Remediation
Upgrade node to version 18.20.4, 20.15.1, 22.4.1 or higher.
References
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10, curl/libcurl3-gnutls@7.88.1-10 and others
- Fixed in: 7.88.1-10+deb12u5
Detailed paths
-
Introduced through: node@18.16.1-bookworm › curl@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl3-gnutls@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4-openssl-dev@7.88.1-10
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.
This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains.
It could do this by exploiting a mixed case flaw in curl's function that
verifies a given cookie domain against the Public Suffix List (PSL). For
example a cookie could be set with domain=co.UK when the URL used a lower
case hostname curl.co.uk, even though co.uk is listed as a PSL domain.
Remediation
Upgrade Debian:12 curl to version 7.88.1-10+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-46218
- https://curl.se/docs/CVE-2023-46218.html
- https://hackerone.com/reports/2212193
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3ZX3VW67N4ACRAPMV2QS2LVYGD7H2MVE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UOGXU25FMMT2X6UUITQ7EZZYMJ42YWWD/
- https://lists.debian.org/debian-lts-announce/2023/12/msg00015.html
- https://www.debian.org/security/2023/dsa-5587
- https://security.netapp.com/advisory/ntap-20240125-0007/
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9, glibc/libc-dev-bin@2.36-9 and others
- Fixed in: 2.36-9+deb12u3
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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.
A flaw was found in glibc. When the getaddrinfo function is called with the AF_UNSPEC address family and the system is configured with no-aaaa mode via /etc/resolv.conf, a DNS response via TCP larger than 2048 bytes can potentially disclose stack contents through the function returned address data, and may cause a crash.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4527
- https://access.redhat.com/security/cve/CVE-2023-4527
- https://bugzilla.redhat.com/show_bug.cgi?id=2234712
- http://www.openwall.com/lists/oss-security/2023/09/25/1
- https://access.redhat.com/errata/RHSA-2023:5453
- https://access.redhat.com/errata/RHSA-2023:5455
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4DBUQRRPB47TC3NJOUIBVWUGFHBJAFDL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DFG4P76UHHZEWQ26FWBXG76N2QLKKPZA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NDAQWHTSVOCOZ5K6KPIWKRT3JX4RTZUR/
- https://security.gentoo.org/glsa/202310-03
- https://security.netapp.com/advisory/ntap-20231116-0012/
medium severity
- Vulnerable module: krb5/krb5-multidev
- Introduced through: krb5/krb5-multidev@1.20.1-2, krb5/libgssapi-krb5-2@1.20.1-2 and others
- Fixed in: 1.20.1-2+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › krb5/krb5-multidev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssapi-krb5-2@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssrpc4@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libk5crypto3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5clnt-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5srv-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkdb5-10@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-dev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5support0@1.20.1-2
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.
lib/kadm5/kadm_rpc_xdr.c in MIT Kerberos 5 (aka krb5) before 1.20.2 and 1.21.x before 1.21.1 frees an uninitialized pointer. A remote authenticated user can trigger a kadmind crash. This occurs because _xdr_kadm5_principal_ent_rec does not validate the relationship between n_key_data and the key_data array count.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-36054
- https://github.com/krb5/krb5/commit/ef08b09c9459551aabbe7924fb176f1583053cdd
- https://github.com/krb5/krb5/compare/krb5-1.20.1-final...krb5-1.20.2-final
- https://github.com/krb5/krb5/compare/krb5-1.21-final...krb5-1.21.1-final
- https://web.mit.edu/kerberos/www/advisories/
- https://lists.debian.org/debian-lts-announce/2023/10/msg00031.html
- https://security.netapp.com/advisory/ntap-20230908-0004/
medium severity
- Vulnerable module: libde265/libde265-0
- Introduced through: libde265/libde265-0@1.0.11-1
- Fixed in: 1.0.11-1+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libde265/libde265-0@1.0.11-1
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 strukturag libde265 v1.10.12 allows a local attacker to cause a denial of service via the slice_segment_header function in the slice.cc component.
Remediation
Upgrade Debian:12 libde265 to version 1.0.11-1+deb12u1 or higher.
References
medium severity
- Vulnerable module: libde265/libde265-0
- Introduced through: libde265/libde265-0@1.0.11-1
- Fixed in: 1.0.11-1+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libde265/libde265-0@1.0.11-1
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.
Libde265 v1.0.11 was discovered to contain a segmentation violation via the function decoder_context::process_slice_segment_header at decctx.cc.
Remediation
Upgrade Debian:12 libde265 to version 1.0.11-1+deb12u1 or higher.
References
medium severity
- Vulnerable module: node
- Introduced through: node@18.16.1
- Fixed in: 18.17.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Access Restriction Bypass via the Module._load which can bypass the policy mechanism and require modules outside of the policy.json definition for a given module.
Remediation
Upgrade node to version 16.20.2, 18.17.1, 20.5.1 or higher.
References
medium severity
- Vulnerable module: node
- Introduced through: node@18.16.1
- Fixed in: 18.17.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Improper Access Control through the usage of module.constructor.createRequire(), which allows an attacker to bypass the policy mechanism and require modules outside of the policy.json definition for a given module.
Note: This vulnerability affects all users using the experimental policy mechanism.
Remediation
Upgrade node to version 16.20.2, 18.17.1, 20.5.1 or higher.
References
medium severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2
- Fixed in: 1:9.2p1-2+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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 ssh in OpenSSH before 9.6, OS command injection might occur if a user name or host name has shell metacharacters, and this name is referenced by an expansion token in certain situations. For example, an untrusted Git repository can have a submodule with shell metacharacters in a user name or host name.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-51385
- https://github.com/openssh/openssh-portable/commit/7ef3787c84b6b524501211b11a26c742f829af1a
- https://www.openssh.com/txt/release-9.6
- https://www.openwall.com/lists/oss-security/2023/12/18/2
- http://www.openwall.com/lists/oss-security/2023/12/26/4
- https://lists.debian.org/debian-lts-announce/2023/12/msg00017.html
- https://security.gentoo.org/glsa/202312-17
- https://vin01.github.io/piptagole/ssh/security/openssh/libssh/remote-code-execution/2023/12/20/openssh-proxycommand-libssh-rce.html
- https://www.debian.org/security/2023/dsa-5586
- https://security.netapp.com/advisory/ntap-20240105-0005/
- https://support.apple.com/kb/HT214084
- http://seclists.org/fulldisclosure/2024/Mar/21
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.9-1, openssl/libssl-dev@3.0.9-1 and others
- Fixed in: 3.0.13-1~deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssl@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl-dev@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl3@3.0.9-1
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: The POLY1305 MAC (message authentication code) implementation contains a bug that might corrupt the internal state of applications running on PowerPC CPU based platforms if the CPU provides vector instructions.
Impact summary: If an attacker can influence whether the POLY1305 MAC algorithm is used, the application state might be corrupted with various application dependent consequences.
The POLY1305 MAC (message authentication code) implementation in OpenSSL for PowerPC CPUs restores the contents of vector registers in a different order than they are saved. Thus the contents of some of these vector registers are corrupted when returning to the caller. The vulnerable code is used only on newer PowerPC processors supporting the PowerISA 2.07 instructions.
The consequences of this kind of internal application state corruption can be various - from no consequences, if the calling application does not depend on the contents of non-volatile XMM registers at all, to the worst consequences, where the attacker could get complete control of the application process. However unless the compiler uses the vector registers for storing pointers, the most likely consequence, if any, would be an incorrect result of some application dependent calculations or a crash leading to a denial of service.
The POLY1305 MAC algorithm is most frequently used as part of the CHACHA20-POLY1305 AEAD (authenticated encryption with associated data) algorithm. The most common usage of this AEAD cipher is with TLS protocol versions 1.2 and 1.3. If this cipher is enabled on the server a malicious client can influence whether this AEAD cipher is used. This implies that TLS server applications using OpenSSL can be potentially impacted. However we are currently not aware of any concrete application that would be affected by this issue therefore we consider this a Low severity security issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.13-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-6129
- http://www.openwall.com/lists/oss-security/2024/01/09/1
- https://github.com/openssl/openssl/commit/050d26383d4e264966fb83428e72d5d48f402d35
- https://github.com/openssl/openssl/commit/5b139f95c9a47a55a0c54100f3837b1eee942b04
- https://github.com/openssl/openssl/commit/f3fc5808fe9ff74042d639839610d03b8fdcc015
- https://www.openssl.org/news/secadv/20240109.txt
- https://security.netapp.com/advisory/ntap-20240216-0009/
- https://security.netapp.com/advisory/ntap-20240426-0008/
- https://security.netapp.com/advisory/ntap-20240426-0013/
- http://www.openwall.com/lists/oss-security/2024/03/11/1
- https://security.netapp.com/advisory/ntap-20240503-0011/
medium severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6, tiff/libtiff6@4.5.0-6 and others
- Fixed in: 4.5.0-6+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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 is vulnerable to an integer overflow. This flaw allows remote attackers to cause a denial of service (application crash) or possibly execute an arbitrary code via a crafted tiff image, which triggers a heap-based buffer overflow.
Remediation
Upgrade Debian:12 tiff to version 4.5.0-6+deb12u1 or higher.
References
medium severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6, tiff/libtiff6@4.5.0-6 and others
- Fixed in: 4.5.0-6+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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 was found in libtiff due to multiple potential integer overflows in raw2tiff.c. This flaw allows remote attackers to cause a denial of service or possibly execute an arbitrary code via a crafted tiff image, which triggers a heap-based buffer overflow.
Remediation
Upgrade Debian:12 tiff to version 4.5.0-6+deb12u1 or higher.
References
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9, glibc/libc-dev-bin@2.36-9 and others
- Fixed in: 2.36-9+deb12u3
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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.
A flaw was found in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the nss_gethostbyname2_r and nss_getcanonname_r hooks without implementing the nss*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4806
- https://access.redhat.com/security/cve/CVE-2023-4806
- https://bugzilla.redhat.com/show_bug.cgi?id=2237782
- http://www.openwall.com/lists/oss-security/2023/10/03/4
- http://www.openwall.com/lists/oss-security/2023/10/03/5
- http://www.openwall.com/lists/oss-security/2023/10/03/6
- http://www.openwall.com/lists/oss-security/2023/10/03/8
- https://access.redhat.com/errata/RHSA-2023:5453
- https://access.redhat.com/errata/RHSA-2023:5455
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4DBUQRRPB47TC3NJOUIBVWUGFHBJAFDL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DFG4P76UHHZEWQ26FWBXG76N2QLKKPZA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NDAQWHTSVOCOZ5K6KPIWKRT3JX4RTZUR/
- https://security.gentoo.org/glsa/202310-03
- https://access.redhat.com/errata/RHSA-2023:7409
- https://security.netapp.com/advisory/ntap-20240125-0008/
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2
- Fixed in: 3.7.9-2+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › gnutls28/libgnutls30@3.7.9-2
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.
A vulnerability was found that the response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from response times of ciphertexts with correct PKCS#1 v1.5 padding.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-5981
- https://access.redhat.com/security/cve/CVE-2023-5981
- https://bugzilla.redhat.com/show_bug.cgi?id=2248445
- https://gnutls.org/security-new.html#GNUTLS-SA-2023-10-23
- https://access.redhat.com/errata/RHSA-2024:0155
- http://www.openwall.com/lists/oss-security/2024/01/19/3
- https://access.redhat.com/errata/RHSA-2024:0319
- https://access.redhat.com/errata/RHSA-2024:0399
- https://access.redhat.com/errata/RHSA-2024:0451
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNXKVR5YNUEBNHAHM5GSYKBZX4W2HMN2/
- https://access.redhat.com/errata/RHSA-2024:0533
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7ZEIOLORQ7N6WRPFXZSYDL2MC4LP7VFV/
- https://access.redhat.com/errata/RHSA-2024:1383
- https://access.redhat.com/errata/RHSA-2024:2094
medium severity
- Vulnerable module: node
- Introduced through: node@18.16.1
- Fixed in: 18.18.2
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature in checksum comparisons against a trusted manifest, which can be forged by an attacker.
Note:
This vulnerability affects all users using the experimental permission model.
At the time this CVE was issued, the permission model is an experimental feature of Node.js.
Remediation
Upgrade node to version 18.18.2, 20.8.1 or higher.
References
medium severity
- Vulnerable module: node
- Introduced through: node@18.16.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Observable Timing Discrepancy due to the implementation of PKCS#1 v1.5 padding. An attacker can infer the private key used in the cryptographic operation by observing the time taken to execute cryptographic operations (Marvin).
Remediation
Upgrade node to version 18.19.1, 20.11.1, 21.6.2 or higher.
References
medium severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2
- Fixed in: 1:9.2p1-2+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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 SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-48795
- http://packetstormsecurity.com/files/176280/Terrapin-SSH-Connection-Weakening.html
- http://www.openwall.com/lists/oss-security/2023/12/18/3
- http://www.openwall.com/lists/oss-security/2023/12/19/5
- http://www.openwall.com/lists/oss-security/2023/12/20/3
- https://access.redhat.com/security/cve/cve-2023-48795
- https://arstechnica.com/security/2023/12/hackers-can-break-ssh-channel-integrity-using-novel-data-corruption-attack/
- https://bugs.gentoo.org/920280
- https://bugzilla.redhat.com/show_bug.cgi?id=2254210
- https://bugzilla.suse.com/show_bug.cgi?id=1217950
- https://crates.io/crates/thrussh/versions
- https://filezilla-project.org/versions.php
- https://forum.netgate.com/topic/184941/terrapin-ssh-attack
- https://git.libssh.org/projects/libssh.git/commit/?h=stable-0.10&id=10e09e273f69e149389b3e0e5d44b8c221c2e7f6
- https://github.com/NixOS/nixpkgs/pull/275249
- https://github.com/PowerShell/Win32-OpenSSH/issues/2189
- https://github.com/PowerShell/Win32-OpenSSH/releases/tag/v9.5.0.0p1-Beta
- https://github.com/TeraTermProject/teraterm/commit/7279fbd6ef4d0c8bdd6a90af4ada2899d786eec0
- https://github.com/TeraTermProject/teraterm/releases/tag/v5.1
- https://github.com/advisories/GHSA-45x7-px36-x8w8
- https://github.com/apache/mina-sshd/issues/445
- https://github.com/connectbot/sshlib/commit/5c8b534f6e97db7ac0e0e579331213aa25c173ab
- https://github.com/connectbot/sshlib/compare/2.2.21...2.2.22
- https://github.com/cyd01/KiTTY/issues/520
- https://github.com/drakkan/sftpgo/releases/tag/v2.5.6
- https://github.com/erlang/otp/blob/d1b43dc0f1361d2ad67601169e90a7fc50bb0369/lib/ssh/doc/src/notes.xml#L39-L42
- https://github.com/erlang/otp/releases/tag/OTP-26.2.1
- https://github.com/golang/crypto/commit/9d2ee975ef9fe627bf0a6f01c1f69e8ef1d4f05d
- https://github.com/hierynomus/sshj/issues/916
- https://github.com/janmojzis/tinyssh/issues/81
- https://github.com/jtesta/ssh-audit/commit/8e972c5e94b460379fe0c7d20209c16df81538a5
- https://github.com/libssh2/libssh2/pull/1291
- https://github.com/mkj/dropbear/blob/17657c36cce6df7716d5ff151ec09a665382d5dd/CHANGES#L25
- https://github.com/mscdex/ssh2/commit/97b223f8891b96d6fc054df5ab1d5a1a545da2a3
- https://github.com/mwiede/jsch/compare/jsch-0.2.14...jsch-0.2.15
- https://github.com/mwiede/jsch/issues/457
- https://github.com/mwiede/jsch/pull/461
- https://github.com/net-ssh/net-ssh/blob/2e65064a52d73396bfc3806c9196fc8108f33cd8/CHANGES.txt#L14-L16
- https://github.com/openssh/openssh-portable/commits/master
- https://github.com/paramiko/paramiko/issues/2337
- https://github.com/proftpd/proftpd/blob/0a7ea9b0ba9fcdf368374a226370d08f10397d99/RELEASE_NOTES
- https://github.com/proftpd/proftpd/blob/d21e7a2e47e9b38f709bec58e3fa711f759ad0e1/RELEASE_NOTES
- https://github.com/proftpd/proftpd/blob/master/RELEASE_NOTES
- https://github.com/proftpd/proftpd/issues/456
- https://github.com/rapier1/hpn-ssh/releases
- https://github.com/ronf/asyncssh/blob/develop/docs/changes.rst
- https://github.com/ronf/asyncssh/tags
- https://github.com/ssh-mitm/ssh-mitm/issues/165
- https://github.com/warp-tech/russh/releases/tag/v0.40.2
- https://gitlab.com/libssh/libssh-mirror/-/tags
- https://groups.google.com/g/golang-announce/c/-n5WqVC18LQ
- https://groups.google.com/g/golang-announce/c/qA3XtxvMUyg
- https://help.panic.com/releasenotes/transmit5/
- https://jadaptive.com/important-java-ssh-security-update-new-ssh-vulnerability-discovered-cve-2023-48795/
- https://lists.debian.org/debian-lts-announce/2023/12/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MKQRBF3DWMWPH36LBCOBUTSIZRTPEZXB/
- https://matt.ucc.asn.au/dropbear/CHANGES
- https://nest.pijul.com/pijul/thrussh/changes/D6H7OWTTMHHX6BTB3B6MNBOBX2L66CBL4LGSEUSAI2MCRCJDQFRQC
- https://news.ycombinator.com/item?id=38684904
- https://news.ycombinator.com/item?id=38685286
- https://news.ycombinator.com/item?id=38732005
- https://nova.app/releases/#v11.8
- https://oryx-embedded.com/download/#changelog
- https://roumenpetrov.info/secsh/#news20231220
- https://security-tracker.debian.org/tracker/source-package/libssh2
- https://security-tracker.debian.org/tracker/source-package/proftpd-dfsg
- https://security-tracker.debian.org/tracker/source-package/trilead-ssh2
- https://security.gentoo.org/glsa/202312-16
- https://security.gentoo.org/glsa/202312-17
- https://thorntech.com/cve-2023-48795-and-sftp-gateway/
- https://twitter.com/TrueSkrillor/status/1736774389725565005
- https://ubuntu.com/security/CVE-2023-48795
- https://winscp.net/eng/docs/history#6.2.2
- https://www.bitvise.com/ssh-client-version-history#933
- https://www.bitvise.com/ssh-server-version-history
- https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html
- https://www.crushftp.com/crush10wiki/Wiki.jsp?page=Update
- https://www.debian.org/security/2023/dsa-5586
- https://www.debian.org/security/2023/dsa-5588
- https://www.freebsd.org/security/advisories/FreeBSD-SA-23:19.openssh.asc
- https://www.lancom-systems.de/service-support/allgemeine-sicherheitshinweise#c243508
- https://www.netsarang.com/en/xshell-update-history/
- https://www.openssh.com/openbsd.html
- https://www.openssh.com/txt/release-9.6
- https://www.openwall.com/lists/oss-security/2023/12/18/2
- https://www.openwall.com/lists/oss-security/2023/12/20/3
- https://www.paramiko.org/changelog.html
- https://www.reddit.com/r/sysadmin/comments/18idv52/cve202348795_why_is_this_cve_still_undisclosed/
- https://www.suse.com/c/suse-addresses-the-ssh-v2-protocol-terrapin-attack-aka-cve-2023-48795/
- https://www.terrapin-attack.com
- https://www.theregister.com/2023/12/20/terrapin_attack_ssh
- https://www.vandyke.com/products/securecrt/history.txt
- http://seclists.org/fulldisclosure/2024/Mar/21
- https://lists.debian.org/debian-lts-announce/2024/01/msg00013.html
- https://lists.debian.org/debian-lts-announce/2024/01/msg00014.html
- https://lists.debian.org/debian-lts-announce/2024/04/msg00016.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/33XHJUB6ROFUOH2OQNENFROTVH6MHSHA/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3CAYYW35MUTNO65RVAELICTNZZFMT2XS/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3JIMLVBDWOP4FUPXPTB4PGHHIOMGFLQE/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3YQLUQWLIHDB5QCXQEX7HXHAWMOKPP5O/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6Y74KVCPEPT4MVU3LHDWCNNOXOE5ZLUR/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/APYIXIQOVDCRWLHTGB4VYMAUIAQLKYJ3/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BL5KTLOSLH2KHRN4HCXJPK3JUVLDGEL6/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/C3AFMZ6MH2UHHOPIWT5YLSFV3D2VB3AC/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CHHITS4PUOZAKFIUBQAQZC7JWXMOYE4B/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/F7EYCFQCTSGJXWO3ZZ44MGKFC5HA7G3Y/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HYEDEXIKFKTUJIN43RG4B7T5ZS6MHUSP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/I724O3LSRCPO4WNVIXTZCT4VVRMXMMSG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KEOTKBUPZXHE3F352JBYNTSNRXYLWD6P/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KMZCVGUGJZZVDPCVDA7TEB22VUCNEXDD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/L5Y6MNNVAPIJSXJERQ6PKZVCIUXSNJK7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LZQVUHWVWRH73YBXUQJOD6CKHDQBU3DM/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QI3EHAHABFQK7OABNCSF5GMYP6TONTI7/
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2024-0002
- https://security.netapp.com/advisory/ntap-20240105-0004/
- https://support.apple.com/kb/HT214084
- http://www.openwall.com/lists/oss-security/2024/04/17/8
- http://www.openwall.com/lists/oss-security/2024/03/06/3
- https://github.com/projectdiscovery/nuclei-templates/blob/master/javascript/cves/2023/CVE-2023-48795.yaml
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.6-1 and systemd/libudev1@252.6-1
- Fixed in: 252.21-1~deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › systemd/libsystemd0@252.6-1
-
Introduced through: node@18.16.1-bookworm › systemd/libudev1@252.6-1
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.
A vulnerability was found in systemd-resolved. This issue may allow systemd-resolved to accept records of DNSSEC-signed domains even when they have no signature, allowing man-in-the-middles (or the upstream DNS resolver) to manipulate records.
Remediation
Upgrade Debian:12 systemd to version 252.21-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-7008
- https://access.redhat.com/security/cve/CVE-2023-7008
- https://bugzilla.redhat.com/show_bug.cgi?id=2222261
- https://bugzilla.redhat.com/show_bug.cgi?id=2222672
- https://github.com/systemd/systemd/issues/25676
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QHNBXGKJWISJETTTDTZKTBFIBJUOSLKL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4GMDEG5PKONWNHOEYSUDRT6JEOISRMN2/
- https://access.redhat.com/errata/RHSA-2024:2463
- https://access.redhat.com/errata/RHSA-2024:3203
medium severity
new
- Vulnerable module: apr/libapr1
- Introduced through: apr/libapr1@1.7.2-3
Detailed paths
-
Introduced through: node@18.16.1-bookworm › apr/libapr1@1.7.2-3
NVD Description
Note: Versions mentioned in the description apply only to the upstream apr package and not the apr package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Lax permissions set by the Apache Portable Runtime library on Unix platforms would allow local users read access to named shared memory segments, potentially revealing sensitive application data.
This issue does not affect non-Unix platforms, or builds with APR_USE_SHMEM_SHMGET=1 (apr.h)
Users are recommended to upgrade to APR version 1.7.5, which fixes this issue.
Remediation
There is no fixed version for Debian:12 apr.
References
medium severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
- Fixed in: 8:6.9.11.60+dfsg-1.6+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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 discovered in ImageMagick where a specially created SVG file loads itself and causes a segmentation fault. This flaw allows a remote attacker to pass a specially crafted SVG file that leads to a segmentation fault, generating many trash files in "/tmp," resulting in a denial of service. When ImageMagick crashes, it generates a lot of trash files. These trash files can be large if the SVG file contains many render actions. In a denial of service attack, if a remote attacker uploads an SVG file of size t, ImageMagick generates files of size 103*t. If an attacker uploads a 100M SVG, the server will generate about 10G.
Remediation
Upgrade Debian:12 imagemagick to version 8:6.9.11.60+dfsg-1.6+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-1289
- https://bugzilla.redhat.com/show_bug.cgi?id=2176858
- https://github.com/ImageMagick/ImageMagick/commit/c5b23cbf2119540725e6dc81f4deb25798ead6a4
- https://github.com/ImageMagick/ImageMagick/security/advisories/GHSA-j96m-mjp6-99xr
- https://lists.debian.org/debian-lts-announce/2024/02/msg00007.html
medium severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
- Fixed in: 8:6.9.11.60+dfsg-1.6+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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 ouccers as an undefined behaviors of casting double to size_t in svg, mvg and other coders (recurring bugs of CVE-2022-32546).
Remediation
Upgrade Debian:12 imagemagick to version 8:6.9.11.60+dfsg-1.6+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-34151
- https://access.redhat.com/security/cve/CVE-2023-34151
- https://bugzilla.redhat.com/show_bug.cgi?id=2210657
- https://github.com/ImageMagick/ImageMagick/issues/6341
- 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://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/
- https://lists.debian.org/debian-lts-announce/2024/02/msg00007.html
medium severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
- Fixed in: 8:6.9.11.60+dfsg-1.6+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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 heap-buffer-overflow flaw was found in ImageMagick’s PushShortPixel() function of quantum-private.h file. This vulnerability is triggered when an attacker passes a specially crafted TIFF image file to ImageMagick for conversion, potentially leading to a denial of service.
Remediation
Upgrade Debian:12 imagemagick to version 8:6.9.11.60+dfsg-1.6+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-1115
- https://access.redhat.com/security/cve/CVE-2022-1115
- https://bugzilla.redhat.com/show_bug.cgi?id=2067022
- https://github.com/ImageMagick/ImageMagick/commit/c8718305f120293d8bf13724f12eed885d830b09
- https://github.com/ImageMagick/ImageMagick/issues/4974
- https://github.com/ImageMagick/ImageMagick6/commit/1f860f52bd8d58737ad883072203391096b30b51
medium severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
- Fixed in: 8:6.9.11.60+dfsg-1.6+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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 heap buffer overflow issue was found in ImageMagick. When an application processes a malformed TIFF file, it could lead to undefined behavior or a crash causing a denial of service.
Remediation
Upgrade Debian:12 imagemagick to version 8:6.9.11.60+dfsg-1.6+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-3213
- https://access.redhat.com/security/cve/CVE-2022-3213
- https://bugzilla.redhat.com/show_bug.cgi?id=2126824
- https://github.com/ImageMagick/ImageMagick/commit/30ccf9a0da1f47161b5935a95be854fe84e6c2a2
- https://github.com/ImageMagick/ImageMagick6/commit/1aea203eb36409ce6903b9e41fe7cb70030e8750
medium severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
- Fixed in: 8:6.9.11.60+dfsg-1.6+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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 heap-based buffer overflow issue was discovered in ImageMagick's ImportMultiSpectralQuantum() function in MagickCore/quantum-import.c. An attacker could pass specially crafted file to convert, triggering an out-of-bounds read error, allowing an application to crash, resulting in a denial of service.
Remediation
Upgrade Debian:12 imagemagick to version 8:6.9.11.60+dfsg-1.6+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-1906
- https://access.redhat.com/security/cve/CVE-2023-1906
- https://bugzilla.redhat.com/show_bug.cgi?id=2185714
- https://github.com/ImageMagick/ImageMagick/commit/d7a8bdd7bb33cf8e58bc01b4a4f2ea5466f8c6b3
- https://github.com/ImageMagick/ImageMagick/security/advisories/GHSA-35q2-86c7-9247
- https://github.com/ImageMagick/ImageMagick6/commit/e30c693b37c3b41723f1469d1226a2c814ca443d
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6655G3GPS42WQM32DJHUCZALI2URQSCO/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6655G3GPS42WQM32DJHUCZALI2URQSCO/
medium severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
- Fixed in: 8:6.9.11.60+dfsg-1.6+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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 heap-based buffer overflow vulnerability was found in coders/tiff.c in ImageMagick. This issue may allow a local attacker to trick the user into opening a specially crafted file, resulting in an application crash and denial of service.
Remediation
Upgrade Debian:12 imagemagick to version 8:6.9.11.60+dfsg-1.6+deb12u1 or higher.
References
medium severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
- Fixed in: 8:6.9.11.60+dfsg-1.6+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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 heap use-after-free flaw was found in coders/bmp.c in ImageMagick.
Remediation
Upgrade Debian:12 imagemagick to version 8:6.9.11.60+dfsg-1.6+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-5341
- https://access.redhat.com/security/cve/CVE-2023-5341
- https://bugzilla.redhat.com/show_bug.cgi?id=2241774
- https://github.com/ImageMagick/ImageMagick/commit/aa673b2e4defc7cad5bec16c4fc8324f71e531f1
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LICYTADFJAFPZW3Y2MKNCJIUYODPAG4L/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YAULDP3GG5KI3XITQ5XSMRSILCBZS2VK/
- https://lists.debian.org/debian-lts-announce/2024/02/msg00007.html
medium severity
- Vulnerable module: librsvg/gir1.2-rsvg-2.0
- Introduced through: librsvg/gir1.2-rsvg-2.0@2.54.5+dfsg-1, librsvg/librsvg2-2@2.54.5+dfsg-1 and others
- Fixed in: 2.54.7+dfsg-1~deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › librsvg/gir1.2-rsvg-2.0@2.54.5+dfsg-1
-
Introduced through: node@18.16.1-bookworm › librsvg/librsvg2-2@2.54.5+dfsg-1
-
Introduced through: node@18.16.1-bookworm › librsvg/librsvg2-common@2.54.5+dfsg-1
-
Introduced through: node@18.16.1-bookworm › librsvg/librsvg2-dev@2.54.5+dfsg-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream librsvg package and not the librsvg package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A directory traversal problem in the URL decoder of librsvg before 2.56.3 could be used by local or remote attackers to disclose files (on the local filesystem outside of the expected area), as demonstrated by href=".?../../../../../../../../../../etc/passwd" in an xi:include element.
Remediation
Upgrade Debian:12 librsvg to version 2.54.7+dfsg-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-38633
- http://seclists.org/fulldisclosure/2023/Jul/43
- http://www.openwall.com/lists/oss-security/2023/07/27/1
- https://bugzilla.suse.com/show_bug.cgi?id=1213502
- https://gitlab.gnome.org/GNOME/librsvg/-/issues/996
- https://gitlab.gnome.org/GNOME/librsvg/-/releases/2.56.3
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/R5BCXT5GW6RCL45ZUHUZR4CJG2BAFDVC/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/422NTIHIEBRASIG2DWXYBH4ADYMHY626/
- http://www.openwall.com/lists/oss-security/2023/09/06/10
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/422NTIHIEBRASIG2DWXYBH4ADYMHY626/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/R5BCXT5GW6RCL45ZUHUZR4CJG2BAFDVC/
- https://news.ycombinator.com/item?id=37415799
- https://security.netapp.com/advisory/ntap-20230831-0011/
- https://www.canva.dev/blog/engineering/when-url-parsers-disagree-cve-2023-38633/
- https://www.debian.org/security/2023/dsa-5484
medium severity
- Vulnerable module: libx11/libx11-6
- Introduced through: libx11/libx11-6@2:1.8.4-2+deb12u1, libx11/libx11-data@2:1.8.4-2+deb12u1 and others
- Fixed in: 2:1.8.4-2+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libx11/libx11-6@2:1.8.4-2+deb12u1
-
Introduced through: node@18.16.1-bookworm › libx11/libx11-data@2:1.8.4-2+deb12u1
-
Introduced through: node@18.16.1-bookworm › libx11/libx11-dev@2:1.8.4-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in libX11 due to an infinite loop within the PutSubImage() function. This flaw allows a local user to consume all available system resources and cause a denial of service condition.
Remediation
Upgrade Debian:12 libx11 to version 2:1.8.4-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-43786
- https://access.redhat.com/security/cve/CVE-2023-43786
- https://bugzilla.redhat.com/show_bug.cgi?id=2242253
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/63IBRFLQVZSMOAZBZOBKFWJP26ILRAGQ/
- https://security.netapp.com/advisory/ntap-20231103-0006/
- http://www.openwall.com/lists/oss-security/2024/01/24/9
- https://access.redhat.com/errata/RHSA-2024:2145
- https://access.redhat.com/errata/RHSA-2024:2973
medium severity
- Vulnerable module: libx11/libx11-6
- Introduced through: libx11/libx11-6@2:1.8.4-2+deb12u1, libx11/libx11-data@2:1.8.4-2+deb12u1 and others
- Fixed in: 2:1.8.4-2+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libx11/libx11-6@2:1.8.4-2+deb12u1
-
Introduced through: node@18.16.1-bookworm › libx11/libx11-data@2:1.8.4-2+deb12u1
-
Introduced through: node@18.16.1-bookworm › libx11/libx11-dev@2:1.8.4-2+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in libX11 due to a boundary condition within the _XkbReadKeySyms() function. This flaw allows a local user to trigger an out-of-bounds read error and read the contents of memory on the system.
Remediation
Upgrade Debian:12 libx11 to version 2:1.8.4-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-43785
- https://access.redhat.com/security/cve/CVE-2023-43785
- https://bugzilla.redhat.com/show_bug.cgi?id=2242252
- https://security.netapp.com/advisory/ntap-20231103-0006/
- https://access.redhat.com/errata/RHSA-2024:2145
- https://access.redhat.com/errata/RHSA-2024:2973
medium severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2
- Fixed in: 1:9.2p1-2+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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 ssh-agent in OpenSSH before 9.6, certain destination constraints can be incompletely applied. When destination constraints are specified during addition of PKCS#11-hosted private keys, these constraints are only applied to the first key, even if a PKCS#11 token returns multiple keys.
Remediation
Upgrade Debian:12 openssh to version 1:9.2p1-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-51384
- https://www.openssh.com/txt/release-9.6
- https://www.openwall.com/lists/oss-security/2023/12/18/2
- http://seclists.org/fulldisclosure/2024/Mar/21
- https://github.com/openssh/openssh-portable/commit/881d9c6af9da4257c69c327c4e2f1508b2fa754b
- https://security.netapp.com/advisory/ntap-20240105-0005/
- https://support.apple.com/kb/HT214084
- https://www.debian.org/security/2023/dsa-5586
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.9-1, openssl/libssl-dev@3.0.9-1 and others
- Fixed in: 3.0.13-1~deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssl@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl-dev@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl3@3.0.9-1
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: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack
Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly.
A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue.
OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass().
We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant.
The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.13-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-0727
- https://github.com/openssl/openssl/commit/09df4395b5071217b76dc7d3d2e630eb8c5a79c2
- https://github.com/openssl/openssl/commit/775acfdbd0c6af9ac855f34969cdab0c0c90844a
- https://github.com/openssl/openssl/commit/d135eeab8a5dbf72b3da5240bab9ddb7678dbd2c
- https://github.openssl.org/openssl/extended-releases/commit/03b3941d60c4bce58fab69a0c22377ab439bc0e8
- https://github.openssl.org/openssl/extended-releases/commit/aebaa5883e31122b404e450732dc833dc9dee539
- https://www.openssl.org/news/secadv/20240125.txt
- https://security.netapp.com/advisory/ntap-20240208-0006/
- http://www.openwall.com/lists/oss-security/2024/03/11/1
medium severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1.2
- Fixed in: 1.34+dfsg-1.2+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tar@1.34+dfsg-1.2
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.
GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approximately 11 whitespace characters.
Remediation
Upgrade Debian:12 tar to version 1.34+dfsg-1.2+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2022-48303
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CRY7VEL4AIG3GLIEVCTOXRZNSVYDYYUD/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/X5VQYCO52Z7GAVCLRYUITN7KXHLRZQS4/
- https://savannah.gnu.org/bugs/?62387
- https://savannah.gnu.org/patch/?10307
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CRY7VEL4AIG3GLIEVCTOXRZNSVYDYYUD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X5VQYCO52Z7GAVCLRYUITN7KXHLRZQS4/
medium severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6, tiff/libtiff6@4.5.0-6 and others
- Fixed in: 4.5.0-6+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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 memory leak flaw was found in Libtiff's tiffcrop utility. This issue occurs when tiffcrop operates on a TIFF image file, allowing an attacker to pass a crafted TIFF image file to tiffcrop utility, which causes this memory leak issue, resulting an application crash, eventually leading to a denial of service.
Remediation
Upgrade Debian:12 tiff to version 4.5.0-6+deb12u1 or higher.
References
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10, curl/libcurl3-gnutls@7.88.1-10 and others
- Fixed in: 7.88.1-10+deb12u5
Detailed paths
-
Introduced through: node@18.16.1-bookworm › curl@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl3-gnutls@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4-openssl-dev@7.88.1-10
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 saving HSTS data to an excessively long file name, curl could end up removing all contents, making subsequent requests using that file unaware of the HSTS status they should otherwise use.
Remediation
Upgrade Debian:12 curl to version 7.88.1-10+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-46219
- https://curl.se/docs/CVE-2023-46219.html
- https://hackerone.com/reports/2236133
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UOGXU25FMMT2X6UUITQ7EZZYMJ42YWWD/
- https://www.debian.org/security/2023/dsa-5587
- https://security.netapp.com/advisory/ntap-20240119-0007/
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9, glibc/libc-dev-bin@2.36-9 and others
- Fixed in: 2.36-9+deb12u4
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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.
An integer overflow was found in the __vsyslog_internal function of the glibc library. This function is called by the syslog and vsyslog functions. This issue occurs when these functions are called with a very long message, leading to an incorrect calculation of the buffer size to store the message, resulting in undefined behavior. This issue affects glibc 2.37 and newer.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-6780
- http://packetstormsecurity.com/files/176932/glibc-syslog-Heap-Based-Buffer-Overflow.html
- http://seclists.org/fulldisclosure/2024/Feb/3
- https://access.redhat.com/security/cve/CVE-2023-6780
- https://bugzilla.redhat.com/show_bug.cgi?id=2254396
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/D2FIH77VHY3KCRROCXOT6L27WMZXSJ2G/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MWQ6BZJ6CV5UAW4VZSKJ6TO4KIW2KWAQ/
- https://security.gentoo.org/glsa/202402-01
- https://www.openwall.com/lists/oss-security/2024/01/30/6
- https://www.qualys.com/2024/01/30/cve-2023-6246/syslog.txt
medium severity
- Vulnerable module: node
- Introduced through: node@18.16.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to HTTP Request Smuggling via content length ofuscation. An attacker can smuggle an HTTP request by including a space before a Content-Length header.
Remediation
Upgrade node to version 18.20.1, 20.12.1, 21.7.2 or higher.
References
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.9-1, openssl/libssl-dev@3.0.9-1 and others
- Fixed in: 3.0.10-1~deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssl@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl-dev@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl3@3.0.9-1
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: Checking excessively long DH keys or parameters may be very slow.
Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.
The function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p.
An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.
The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().
Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the "-check" option.
The OpenSSL SSL/TLS implementation is not affected by this issue.
The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.10-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-3817
- http://seclists.org/fulldisclosure/2023/Jul/43
- http://www.openwall.com/lists/oss-security/2023/07/31/1
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=6a1eb62c29db6cb5eec707f9338aee00f44e26f5
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=869ad69aadd985c7b8ca6f4e5dd0eb274c9f3644
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9002fd07327a91f35ba6c1307e71fa6fd4409b7f
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=91ddeba0f2269b017dc06c46c993a788974b1aa5
- https://www.openssl.org/news/secadv/20230731.txt
- https://lists.debian.org/debian-lts-announce/2023/08/msg00019.html
- https://security.netapp.com/advisory/ntap-20230818-0014/
- http://www.openwall.com/lists/oss-security/2023/09/22/9
- http://www.openwall.com/lists/oss-security/2023/09/22/11
- https://security.netapp.com/advisory/ntap-20231027-0008/
- http://www.openwall.com/lists/oss-security/2023/11/06/2
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20240621-0006/
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.9-1, openssl/libssl-dev@3.0.9-1 and others
- Fixed in: 3.0.10-1~deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssl@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl-dev@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl3@3.0.9-1
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: The AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries which are unauthenticated as a consequence.
Impact summary: Applications that use the AES-SIV algorithm and want to authenticate empty data entries as associated data can be mislead by removing adding or reordering such empty entries as these are ignored by the OpenSSL implementation. We are currently unaware of any such applications.
The AES-SIV algorithm allows for authentication of multiple associated data entries along with the encryption. To authenticate empty data the application has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with NULL pointer as the output buffer and 0 as the input buffer length. The AES-SIV implementation in OpenSSL just returns success for such a call instead of performing the associated data authentication operation. The empty data thus will not be authenticated.
As this issue does not affect non-empty associated data authentication and we expect it to be rare for an application to use empty associated data entries this is qualified as Low severity issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.10-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-2975
- http://www.openwall.com/lists/oss-security/2023/07/15/1
- http://www.openwall.com/lists/oss-security/2023/07/19/5
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=00e2f5eea29994d19293ec4e8c8775ba73678598
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=6a83f0c958811f07e0d11dfc6b5a6a98edfd5bdc
- https://security.netapp.com/advisory/ntap-20230725-0004/
- https://www.openssl.org/news/secadv/20230714.txt
- https://security.gentoo.org/glsa/202402-08
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.9-1, openssl/libssl-dev@3.0.9-1 and others
- Fixed in: 3.0.13-1~deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssl@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl-dev@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl3@3.0.9-1
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: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow.
Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.
While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters.
Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q.
An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.
DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().
Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application.
The OpenSSL SSL/TLS implementation is not affected by this issue.
The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.13-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-5678
- http://www.openwall.com/lists/oss-security/2023/11/06/2
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=34efaef6c103d636ab507a0cc34dca4d3aecc055
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=710fee740904b6290fef0dd5536fbcedbc38ff0c
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=db925ae2e65d0d925adef429afc37f75bd1c2017
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ddeb4b6c6d527e54ce9a99cba785c0f7776e54b6
- https://www.openssl.org/news/secadv/20231106.txt
- https://security.netapp.com/advisory/ntap-20231130-0010/
- http://www.openwall.com/lists/oss-security/2024/03/11/1
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.9-1, openssl/libssl-dev@3.0.9-1 and others
- Fixed in: 3.0.10-1~deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssl@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl-dev@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl3@3.0.9-1
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: Checking excessively long DH keys or parameters may be very slow.
Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.
The function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length.
However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large.
An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack.
The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().
Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the '-check' option.
The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.10-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-3446
- http://www.openwall.com/lists/oss-security/2023/07/19/4
- http://www.openwall.com/lists/oss-security/2023/07/19/5
- http://www.openwall.com/lists/oss-security/2023/07/19/6
- https://www.openssl.org/news/secadv/20230719.txt
- http://www.openwall.com/lists/oss-security/2023/07/31/1
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=1fa20cf2f506113c761777127a38bce5068740eb
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=8780a896543a654e757db1b9396383f9d8095528
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9a0a4d3c1e7138915563c0df4fe6a3f9377b839c
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=fc9867c1e03c22ebf56943be205202e576aabf23
- https://lists.debian.org/debian-lts-announce/2023/08/msg00019.html
- https://security.netapp.com/advisory/ntap-20230803-0011/
- https://security.gentoo.org/glsa/202402-08
- http://www.openwall.com/lists/oss-security/2024/05/16/1
medium severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › python3.11@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/python3.11-minimal@3.11.2-6
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.
An issue was discovered in Python before 3.8.18, 3.9.x before 3.9.18, 3.10.x before 3.10.13, and 3.11.x before 3.11.5. It primarily affects servers (such as HTTP servers) that use TLS client authentication. If a TLS server-side socket is created, receives data into the socket buffer, and then is closed quickly, there is a brief window where the SSLSocket instance will detect the socket as "not connected" and won't initiate a handshake, but buffered data will still be readable from the socket buffer. This data will not be authenticated if the server-side TLS peer is expecting client certificate authentication, and is indistinguishable from valid TLS stream data. Data is limited in size to the amount that will fit in the buffer. (The TLS connection cannot directly be used for data exfiltration because the vulnerable code path requires that the connection be closed on initialization of the SSLSocket.)
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-40217
- https://mail.python.org/archives/list/security-announce@python.org/thread/PEPLII27KYHLF4AK3ZQGKYNCRERG4YXY/
- https://www.python.org/dev/security/
- https://lists.debian.org/debian-lts-announce/2023/09/msg00022.html
- https://security.netapp.com/advisory/ntap-20231006-0014/
- https://lists.debian.org/debian-lts-announce/2023/10/msg00017.html
- https://mail.python.org/archives/list/security-announce%40python.org/thread/PEPLII27KYHLF4AK3ZQGKYNCRERG4YXY/
medium severity
- Vulnerable module: mariadb/libmariadb-dev
- Introduced through: mariadb/libmariadb-dev@1:10.11.3-1, mariadb/libmariadb-dev-compat@1:10.11.3-1 and others
- Fixed in: 1:10.11.6-0+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › mariadb/libmariadb-dev@1:10.11.3-1
-
Introduced through: node@18.16.1-bookworm › mariadb/libmariadb-dev-compat@1:10.11.3-1
-
Introduced through: node@18.16.1-bookworm › mariadb/libmariadb3@1:10.11.3-1
-
Introduced through: node@18.16.1-bookworm › mariadb/mariadb-common@1:10.11.3-1
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.
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 5.7.43 and prior, 8.0.34 and prior and 8.1.0. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
Remediation
Upgrade Debian:12 mariadb to version 1:10.11.6-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-22084
- https://www.oracle.com/security-alerts/cpuoct2023.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OR7GNQAJZ7NMHT4HRDNROR3DS272KKET/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UCGSAQFWYIJRIYLZLHPS3MRUS4AQ5JQH/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YZL2AT2ZUKB6K22UTISHEZ4JKG4VZ3VO/
- https://security.netapp.com/advisory/ntap-20231027-0009/
- https://lists.debian.org/debian-lts-announce/2024/01/msg00017.html
medium severity
- Vulnerable module: postgresql-15/libpq-dev
- Introduced through: postgresql-15/libpq-dev@15.3-0+deb12u1 and postgresql-15/libpq5@15.3-0+deb12u1
- Fixed in: 15.5-0+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq-dev@15.3-0+deb12u1
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq5@15.3-0+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream postgresql-15 package and not the postgresql-15 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in PostgreSQL involving the pg_cancel_backend role that signals background workers, including the logical replication launcher, autovacuum workers, and the autovacuum launcher. Successful exploitation requires a non-core extension with a less-resilient background worker and would affect that specific background worker only. This issue may allow a remote high privileged user to launch a denial of service (DoS) attack.
Remediation
Upgrade Debian:12 postgresql-15 to version 15.5-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-5870
- https://access.redhat.com/errata/RHSA-2023:7545
- https://access.redhat.com/errata/RHSA-2023:7579
- https://access.redhat.com/errata/RHSA-2023:7580
- https://access.redhat.com/errata/RHSA-2023:7581
- https://access.redhat.com/errata/RHSA-2023:7616
- https://access.redhat.com/errata/RHSA-2023:7656
- https://access.redhat.com/errata/RHSA-2023:7666
- https://access.redhat.com/errata/RHSA-2023:7667
- https://access.redhat.com/errata/RHSA-2023:7694
- https://access.redhat.com/errata/RHSA-2023:7695
- https://access.redhat.com/errata/RHSA-2023:7714
- https://access.redhat.com/errata/RHSA-2023:7770
- https://access.redhat.com/errata/RHSA-2023:7772
- https://access.redhat.com/security/cve/CVE-2023-5870
- https://bugzilla.redhat.com/show_bug.cgi?id=2247170
- https://www.postgresql.org/about/news/postgresql-161-155-1410-1313-1217-and-1122-released-2749/
- https://www.postgresql.org/support/security/CVE-2023-5870/
- https://access.redhat.com/errata/RHSA-2023:7784
- https://access.redhat.com/errata/RHSA-2023:7785
- https://access.redhat.com/errata/RHSA-2023:7883
- https://access.redhat.com/errata/RHSA-2023:7884
- https://access.redhat.com/errata/RHSA-2023:7885
- https://access.redhat.com/errata/RHSA-2024:0304
- https://security.netapp.com/advisory/ntap-20240119-0003/
- https://access.redhat.com/errata/RHSA-2024:0332
- https://access.redhat.com/errata/RHSA-2024:0337
medium severity
- Vulnerable module: postgresql-15/libpq-dev
- Introduced through: postgresql-15/libpq-dev@15.3-0+deb12u1 and postgresql-15/libpq5@15.3-0+deb12u1
- Fixed in: 15.5-0+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq-dev@15.3-0+deb12u1
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq5@15.3-0+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream postgresql-15 package and not the postgresql-15 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A vulnerability was found in PostgreSQL with the use of the MERGE command, which fails to test new rows against row security policies defined for UPDATE and SELECT. If UPDATE and SELECT policies forbid some rows that INSERT policies do not forbid, a user could store such rows.
Remediation
Upgrade Debian:12 postgresql-15 to version 15.5-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-39418
- https://access.redhat.com/security/cve/CVE-2023-39418
- https://bugzilla.redhat.com/show_bug.cgi?id=2228112
- https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=cb2ae5741f2458a474ed3c31458d242e678ff229
- https://www.postgresql.org/support/security/CVE-2023-39418/
- https://access.redhat.com/errata/RHSA-2023:7785
- https://access.redhat.com/errata/RHSA-2023:7883
- https://access.redhat.com/errata/RHSA-2023:7884
- https://access.redhat.com/errata/RHSA-2023:7885
- https://security.netapp.com/advisory/ntap-20230915-0002/
- https://www.debian.org/security/2023/dsa-5553
medium severity
- Vulnerable module: postgresql-15/libpq-dev
- Introduced through: postgresql-15/libpq-dev@15.3-0+deb12u1 and postgresql-15/libpq5@15.3-0+deb12u1
- Fixed in: 15.5-0+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq-dev@15.3-0+deb12u1
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq5@15.3-0+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream postgresql-15 package and not the postgresql-15 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A memory disclosure vulnerability was found in PostgreSQL that allows remote users to access sensitive information by exploiting certain aggregate function calls with 'unknown'-type arguments. Handling 'unknown'-type values from string literals without type designation can disclose bytes, potentially revealing notable and confidential information. This issue exists due to excessive data output in aggregate function calls, enabling remote users to read some portion of system memory.
Remediation
Upgrade Debian:12 postgresql-15 to version 15.5-0+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-5868
- https://access.redhat.com/errata/RHSA-2023:7545
- https://access.redhat.com/errata/RHSA-2023:7579
- https://access.redhat.com/errata/RHSA-2023:7580
- https://access.redhat.com/errata/RHSA-2023:7581
- https://access.redhat.com/errata/RHSA-2023:7616
- https://access.redhat.com/errata/RHSA-2023:7656
- https://access.redhat.com/errata/RHSA-2023:7666
- https://access.redhat.com/errata/RHSA-2023:7667
- https://access.redhat.com/errata/RHSA-2023:7694
- https://access.redhat.com/errata/RHSA-2023:7695
- https://access.redhat.com/errata/RHSA-2023:7714
- https://access.redhat.com/errata/RHSA-2023:7770
- https://access.redhat.com/errata/RHSA-2023:7772
- https://access.redhat.com/security/cve/CVE-2023-5868
- https://bugzilla.redhat.com/show_bug.cgi?id=2247168
- https://www.postgresql.org/about/news/postgresql-161-155-1410-1313-1217-and-1122-released-2749/
- https://www.postgresql.org/support/security/CVE-2023-5868/
- https://access.redhat.com/errata/RHSA-2023:7784
- https://access.redhat.com/errata/RHSA-2023:7785
- https://access.redhat.com/errata/RHSA-2023:7883
- https://access.redhat.com/errata/RHSA-2023:7884
- https://access.redhat.com/errata/RHSA-2023:7885
- https://access.redhat.com/errata/RHSA-2024:0304
- https://security.netapp.com/advisory/ntap-20240119-0003/
- https://access.redhat.com/errata/RHSA-2024:0332
- https://access.redhat.com/errata/RHSA-2024:0337
low severity
- Vulnerable module: aom/libaom3
- Introduced through: aom/libaom3@3.6.0-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › aom/libaom3@3.6.0-1
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, glibc/libc-dev-bin@2.36-9 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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://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@lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/
- 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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tar@1.34+dfsg-1.2
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, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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.7, the program processes BMP images without verifying that biWidth and biHeight in the bitmap-information header match the actual input, leading to a heap-based buffer over-read in bmp2tiff.
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: node@18.16.1-bookworm › openexr/libopenexr-3-1-30@3.1.5-5
-
Introduced through: node@18.16.1-bookworm › 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://takeonme.org/cves/CVE-2023-5841.html
- 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/
low severity
- Vulnerable module: wget/wget
- Introduced through: wget/wget@1.21.3-1+b2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › wget/wget@1.21.3-1+b2
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.
url.c in GNU Wget through 1.24.5 mishandles semicolons in the userinfo subcomponent of a URI, and thus there may be insecure behavior in which data that was supposed to be in the userinfo subcomponent is misinterpreted to be part of the host subcomponent.
Remediation
There is no fixed version for Debian:12 wget.
References
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › git@1:2.39.2-1.1
-
Introduced through: node@18.16.1-bookworm › git/git-man@1:2.39.2-1.1
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: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9, glibc/libc-dev-bin@2.36-9 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libheif/libheif1@1.15.1-1
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 UncompressedImageCodec::decode_uncompressed_image.
Remediation
There is no fixed version for Debian:12 libheif.
References
low severity
- Vulnerable module: libheif/libheif1
- Introduced through: libheif/libheif1@1.15.1-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libheif/libheif1@1.15.1-1
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 component /libheif/exif.cc.
Remediation
There is no fixed version for Debian:12 libheif.
References
low severity
- Vulnerable module: libheif/libheif1
- Introduced through: libheif/libheif1@1.15.1-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libheif/libheif1@1.15.1-1
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: libheif/libheif1
- Introduced through: libheif/libheif1@1.15.1-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libheif/libheif1@1.15.1-1
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 UncompressedImageCodec::get_luma_bits_per_pixel_from_configuration_unci.
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: node@18.16.1-bookworm › libwmf/libwmf-0.2-7@0.2.12-5.1
-
Introduced through: node@18.16.1-bookworm › libwmf/libwmf-dev@0.2.12-5.1
-
Introduced through: node@18.16.1-bookworm › 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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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, perl/libperl5.36@5.36.0-7 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › perl@5.36.0-7
-
Introduced through: node@18.16.1-bookworm › perl/libperl5.36@5.36.0-7
-
Introduced through: node@18.16.1-bookworm › perl/perl-base@5.36.0-7
-
Introduced through: node@18.16.1-bookworm › perl/perl-modules-5.36@5.36.0-7
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
- 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://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/
- https://github.com/chansen/p5-http-tiny/pull/153
low severity
- Vulnerable module: perl
- Introduced through: perl@5.36.0-7, perl/libperl5.36@5.36.0-7 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › perl@5.36.0-7
-
Introduced through: node@18.16.1-bookworm › perl/libperl5.36@5.36.0-7
-
Introduced through: node@18.16.1-bookworm › perl/perl-base@5.36.0-7
-
Introduced through: node@18.16.1-bookworm › perl/perl-modules-5.36@5.36.0-7
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
- 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://metacpan.org/dist/CPAN/changes
- https://www.openwall.com/lists/oss-security/2023/04/18/14
- 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/
- 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://security.netapp.com/advisory/ntap-20240621-0007/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.40-2, binutils/binutils-common@2.40-2 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › binutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-common@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libbinutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf-nobfd0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libgprofng0@2.40-2
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 get_count function in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.31, allows remote attackers to cause a denial of service (malloc called with the result of an integer-overflowing calculation) or possibly have unspecified other impact via a crafted string, as demonstrated by c++filt.
Remediation
There is no fixed version for Debian:12 binutils.
References
- https://security-tracker.debian.org/tracker/CVE-2018-18483
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87602
- https://sourceware.org/bugzilla/show_bug.cgi?id=23767
- http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00072.html
- http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00008.html
- http://www.securityfocus.com/bid/105689
- https://usn.ubuntu.com/4326-1/
- https://usn.ubuntu.com/4336-1/
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-18483
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › git@1:2.39.2-1.1
-
Introduced through: node@18.16.1-bookworm › git/git-man@1:2.39.2-1.1
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 revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, a specially crafted .gitmodules file with submodule URLs that are longer than 1024 characters can used to exploit a bug in config.c::git_config_copy_or_rename_section_in_file(). This bug can be used to inject arbitrary configuration into a user's $GIT_DIR/config when attempting to remove the configuration section associated with that submodule. When the attacker injects configuration values which specify executables to run (such as core.pager, core.editor, core.sshCommand, etc.) this can lead to a remote code execution. A fix A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid running git submodule deinit on untrusted repositories or without prior inspection of any submodule sections in $GIT_DIR/config.
Remediation
There is no fixed version for Debian:12 git.
References
- https://security-tracker.debian.org/tracker/CVE-2023-29007
- https://github.com/git/git/blob/9ce9dea4e1c2419cca126d29fa7730baa078a11b/Documentation/RelNotes/2.30.9.txt
- https://github.com/git/git/commit/528290f8c61222433a8cf02fb7cfffa8438432b4
- https://github.com/git/git/security/advisories/GHSA-v48j-4xgg-4844
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PI7FZ4NNR5S5J5K6AMVQBH2JFP6NE4L7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YFZWGQKB6MM5MNF2DLFTD7KS2KWPICKL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RKOXOAZ42HLXHXTW6JZI4L5DAIYDTYCU/
- https://security.gentoo.org/glsa/202312-15
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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 heap-based buffer overflow was found in openjpeg in color.c:379:42 in sycc420_to_rgb when decompressing a crafted .j2k file. An attacker could use this to execute arbitrary code with the permissions of the application compiled against openjpeg.
Remediation
There is no fixed version for Debian:12 openjpeg2.
References
- https://security-tracker.debian.org/tracker/CVE-2021-3575
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EZ54FGM2IGAP4AWSJ22JKHOPHCR3FGYU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QB6AI7CWXWMEDZIQY4LQ6DMIEXMDOHUP/
- https://access.redhat.com/errata/RHSA-2021:4251
- https://access.redhat.com/security/cve/CVE-2021-3575
- https://bugzilla.redhat.com/show_bug.cgi?id=1957616
- https://github.com/uclouvain/openjpeg/issues/1347
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EZ54FGM2IGAP4AWSJ22JKHOPHCR3FGYU/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QB6AI7CWXWMEDZIQY4LQ6DMIEXMDOHUP/
- https://ubuntu.com/security/CVE-2021-3575
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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://security.gentoo.org/glsa/202212-06
- https://access.redhat.com/errata/RHSA-2024:3166
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: node@18.16.1-bookworm › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: node@18.16.1-bookworm › 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 4.8, in certain circumstances affecting at least Gentoo, Arch Linux, and Void Linux, allows local users to obtain root access because setuid programs are misconfigured. Specifically, this affects shadow 4.8 when compiled using --with-libpam but without explicitly passing --disable-account-tools-setuid, and without a PAM configuration suitable for use with setuid account management tools. This combination leads to account management tools (groupadd, groupdel, groupmod, useradd, userdel, usermod) that can easily be used by unprivileged local users to escalate privileges to root in multiple ways. This issue became much more relevant in approximately December 2019 when an unrelated bug was fixed (i.e., the chmod calls to suidusbins were fixed in the upstream Makefile which is now included in the release version 4.8).
Remediation
There is no fixed version for Debian:12 shadow.
References
- https://security-tracker.debian.org/tracker/CVE-2019-19882
- https://security.gentoo.org/glsa/202008-09
- https://github.com/shadow-maint/shadow/commit/edf7547ad5aa650be868cf2dac58944773c12d75
- https://github.com/shadow-maint/shadow/pull/199
- https://github.com/void-linux/void-packages/pull/17580
- https://bugs.archlinux.org/task/64836
- https://bugs.gentoo.org/702252
low severity
- Vulnerable module: aom/libaom3
- Introduced through: aom/libaom3@3.6.0-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › aom/libaom3@3.6.0-1
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: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1 and expat/libexpat1-dev@2.5.0-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › expat/libexpat1@2.5.0-1
-
Introduced through: node@18.16.1-bookworm › expat/libexpat1-dev@2.5.0-1
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
- https://github.com/libexpat/libexpat/pull/789
- 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://lists.debian.org/debian-lts-announce/2024/04/msg00006.html
- http://www.openwall.com/lists/oss-security/2024/03/20/5
- https://security.netapp.com/advisory/ntap-20240614-0003/
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › git@1:2.39.2-1.1
-
Introduced through: node@18.16.1-bookworm › git/git-man@1:2.39.2-1.1
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 revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to git apply --reject, a path outside the working tree can be overwritten with partially controlled contents (corresponding to the rejected hunk(s) from the given patch). A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid using git apply with --reject when applying patches from an untrusted source. Use git apply --stat to inspect a patch before applying; avoid applying one that create a conflict where a link corresponding to the *.rej file exists.
Remediation
There is no fixed version for Debian:12 git.
References
- https://security-tracker.debian.org/tracker/CVE-2023-25652
- http://www.openwall.com/lists/oss-security/2023/04/25/2
- https://github.com/git/git/commit/18e2b1cfc80990719275d7b08e6e50f3e8cbc902
- https://github.com/git/git/commit/668f2d53613ac8fd373926ebe219f2c29112d93e
- https://github.com/git/git/security/advisories/GHSA-2hvf-7c8p-28fx
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PI7FZ4NNR5S5J5K6AMVQBH2JFP6NE4L7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YFZWGQKB6MM5MNF2DLFTD7KS2KWPICKL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RKOXOAZ42HLXHXTW6JZI4L5DAIYDTYCU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BSXOGVVBJLYX26IAYX6PJSYQB36BREWH/
- https://security.gentoo.org/glsa/202312-15
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › git@1:2.39.2-1.1
-
Introduced through: node@18.16.1-bookworm › git/git-man@1:2.39.2-1.1
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://github.com/git/git/blob/2dc94da3744bfbbf145eca587a0f5ff480cc5867/Documentation/git-clone.txt#L185-L191
- https://wwws.nightwatchcybersecurity.com/2022/02/11/gitbleed/
- https://www.aquasec.com/blog/undetected-hard-code-secrets-expose-corporations/
- https://lore.kernel.org/git/xmqq4k14qe9g.fsf%40gitster.g/
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9, glibc/libc-dev-bin@2.36-9 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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, glibc/libc-dev-bin@2.36-9 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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: node@18.16.1-bookworm › 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://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@lists.fedoraproject.org/message/KWCHWSICWVZSAXP2YAXM65JC2GR53547/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YZ5M2GSAIHFPLHYJXUPQ2QDJCLWXUGO3/
- https://security.netapp.com/advisory/ntap-20230725-0006/
- 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/
low severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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: node@18.16.1-bookworm › 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, krb5/libgssapi-krb5-2@1.20.1-2 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › krb5/krb5-multidev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssapi-krb5-2@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssrpc4@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libk5crypto3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5clnt-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5srv-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkdb5-10@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-dev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5support0@1.20.1-2
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: node@18.16.1-bookworm › 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
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.2 and libxml2/libxml2-dev@2.9.14+dfsg-1.2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libxml2@2.9.14+dfsg-1.2
-
Introduced through: node@18.16.1-bookworm › libxml2/libxml2-dev@2.9.14+dfsg-1.2
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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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: node@18.16.1-bookworm › 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: node@18.16.1-bookworm › 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
- https://access.redhat.com/security/cve/CVE-2023-2953
- https://bugs.openldap.org/show_bug.cgi?id=9904
- http://seclists.org/fulldisclosure/2023/Jul/47
- http://seclists.org/fulldisclosure/2023/Jul/48
- http://seclists.org/fulldisclosure/2023/Jul/52
- 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: node@18.16.1-bookworm › 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: node@18.16.1-bookworm › 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6952
- https://security-tracker.debian.org/tracker/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: node@18.16.1-bookworm › 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6951
- https://security-tracker.debian.org/tracker/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, perl/libperl5.36@5.36.0-7 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › perl@5.36.0-7
-
Introduced through: node@18.16.1-bookworm › perl/libperl5.36@5.36.0-7
-
Introduced through: node@18.16.1-bookworm › perl/perl-base@5.36.0-7
-
Introduced through: node@18.16.1-bookworm › perl/perl-modules-5.36@5.36.0-7
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
new
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › python3.11@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/python3.11-minimal@3.11.2-6
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.
There is a LOW severity vulnerability affecting CPython, specifically the 'http.cookies' standard library module.
When parsing cookies that contained backslashes for quoted characters in the cookie value, the parser would use an algorithm with quadratic complexity, resulting in excess CPU resources being used while parsing the value.
Remediation
There is no fixed version for Debian:12 python3.11.
References
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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
new
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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 null pointer dereference flaw was found in Libtiff via tif_dirinfo.c. This issue may allow an attacker to trigger memory allocation failures through certain means, such as restricting the heap space size or injecting faults, causing a segmentation fault. This can cause an application crash, eventually leading to a denial of service.
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, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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 segment fault (SEGV) flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFReadRGBATileExt() API. This flaw allows a remote attacker to cause a heap-buffer overflow, leading to a denial of service.
Remediation
There is no fixed version for Debian:12 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2023-52356
- https://access.redhat.com/security/cve/CVE-2023-52356
- https://bugzilla.redhat.com/show_bug.cgi?id=2251344
- https://gitlab.com/libtiff/libtiff/-/issues/622
- https://gitlab.com/libtiff/libtiff/-/merge_requests/546
- https://lists.debian.org/debian-lts-announce/2024/03/msg00011.html
- 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
- http://seclists.org/fulldisclosure/2024/Jul/16
- http://seclists.org/fulldisclosure/2024/Jul/17
- 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
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
- https://access.redhat.com/errata/RHSA-2024:5079
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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: node@18.16.1-bookworm › 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: node@18.16.1-bookworm › 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: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2 and sqlite3/libsqlite3-dev@3.40.1-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › sqlite3/libsqlite3-0@3.40.1-2
-
Introduced through: node@18.16.1-bookworm › sqlite3/libsqlite3-dev@3.40.1-2
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 vulnerability was found in SQLite SQLite3 up to 3.43.0 and classified as critical. This issue affects the function sessionReadRecord of the file ext/session/sqlite3session.c of the component make alltest Handler. The manipulation leads to heap-based buffer overflow. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248999.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2023-7104
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/D6C2HN4T2S6GYNTAUXLH45LQZHK7QPHP/
- https://sqlite.org/forum/forumpost/5bcbf4571c
- https://sqlite.org/src/info/0e4e7a05c4204b47
- https://vuldb.com/?ctiid.248999
- https://vuldb.com/?id.248999
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AYONA2XSNFMXLAW4IHLFI5UVV3QRNG5K/
- https://security.netapp.com/advisory/ntap-20240112-0008/
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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: node@18.16.1-bookworm › binutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-common@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libbinutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf-nobfd0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libgprofng0@2.40-2
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: node@18.16.1-bookworm › binutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-common@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libbinutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf-nobfd0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libgprofng0@2.40-2
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: node@18.16.1-bookworm › binutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-common@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libbinutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf-nobfd0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libgprofng0@2.40-2
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: node@18.16.1-bookworm › cairo/libcairo-gobject2@1.16.0-7
-
Introduced through: node@18.16.1-bookworm › cairo/libcairo-script-interpreter2@1.16.0-7
-
Introduced through: node@18.16.1-bookworm › cairo/libcairo2@1.16.0-7
-
Introduced through: node@18.16.1-bookworm › cairo/libcairo2-dev@1.16.0-7
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: node@18.16.1-bookworm › cairo/libcairo-gobject2@1.16.0-7
-
Introduced through: node@18.16.1-bookworm › cairo/libcairo-script-interpreter2@1.16.0-7
-
Introduced through: node@18.16.1-bookworm › cairo/libcairo2@1.16.0-7
-
Introduced through: node@18.16.1-bookworm › cairo/libcairo2-dev@1.16.0-7
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: node@18.16.1-bookworm › cairo/libcairo-gobject2@1.16.0-7
-
Introduced through: node@18.16.1-bookworm › cairo/libcairo-script-interpreter2@1.16.0-7
-
Introduced through: node@18.16.1-bookworm › cairo/libcairo2@1.16.0-7
-
Introduced through: node@18.16.1-bookworm › cairo/libcairo2-dev@1.16.0-7
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: node@18.16.1-bookworm › 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
new
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10, curl/libcurl3-gnutls@7.88.1-10 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › curl@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl3-gnutls@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4-openssl-dev@7.88.1-10
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's ASN1 parser code has the GTime2str() function, used for parsing an
ASN.1 Generalized Time field. If given an syntactically incorrect field, the
parser might end up using -1 for the length of the time fraction, leading to
a strlen() getting performed on a pointer to a heap buffer area that is not
(purposely) null terminated.
This flaw most likely leads to a crash, but can also lead to heap contents getting returned to the application when CURLINFO_CERTINFO is used.
Remediation
There is no fixed version for Debian:12 curl.
References
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: node@18.16.1-bookworm › djvulibre/libdjvulibre-dev@3.5.28-2+b1
-
Introduced through: node@18.16.1-bookworm › djvulibre/libdjvulibre-text@3.5.28-2
-
Introduced through: node@18.16.1-bookworm › 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://sourceforge.net/p/djvu/bugs/344/
- 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/
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: node@18.16.1-bookworm › djvulibre/libdjvulibre-dev@3.5.28-2+b1
-
Introduced through: node@18.16.1-bookworm › djvulibre/libdjvulibre-text@3.5.28-2
-
Introduced through: node@18.16.1-bookworm › 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://sourceforge.net/p/djvu/bugs/345/
- 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/
low severity
- Vulnerable module: imagemagick
- Introduced through: imagemagick@8:6.9.11.60+dfsg-1.6, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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: node@18.16.1-bookworm › jbigkit/libjbig-dev@2.1-6.1
-
Introduced through: node@18.16.1-bookworm › 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: libheif/libheif1
- Introduced through: libheif/libheif1@1.15.1-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libheif/libheif1@1.15.1-1
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.
A Segmentation fault caused by a floating point exception exists in libheif 1.15.1 using crafted heif images via the heif::Fraction::round() function in box.cc, which causes a denial of service.
Remediation
There is no fixed version for Debian:12 libheif.
References
- https://security-tracker.debian.org/tracker/CVE-2023-29659
- https://github.com/strukturag/libheif/issues/794
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CKAE6NQBA3Q7GS6VTNDZRZZZVPPEFUEZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LGKHDCS4HRZE3UGXYYDYPTIPNIBRLQ5L/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CKAE6NQBA3Q7GS6VTNDZRZZZVPPEFUEZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LGKHDCS4HRZE3UGXYYDYPTIPNIBRLQ5L/
low severity
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.2 and libxml2/libxml2-dev@2.9.14+dfsg-1.2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libxml2@2.9.14+dfsg-1.2
-
Introduced through: node@18.16.1-bookworm › libxml2/libxml2-dev@2.9.14+dfsg-1.2
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.2 and libxml2/libxml2-dev@2.9.14+dfsg-1.2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libxml2@2.9.14+dfsg-1.2
-
Introduced through: node@18.16.1-bookworm › libxml2/libxml2-dev@2.9.14+dfsg-1.2
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: node@18.16.1-bookworm › ncurses/libncurses-dev@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/libncurses5-dev@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/libncurses6@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/libncursesw5-dev@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/libncursesw6@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/libtinfo6@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/ncurses-base@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/ncurses-bin@6.4-4
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.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/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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.
Division-by-zero vulnerabilities in the functions opj_pi_next_cprl, opj_pi_next_pcrl, and opj_pi_next_rpcl in pi.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
- https://security-tracker.debian.org/tracker/CVE-2016-10506
- https://security.gentoo.org/glsa/201710-26
- https://github.com/uclouvain/openjpeg/commit/d27ccf01c68a31ad62b33d2dc1ba2bb1eeaafe7b
- https://github.com/uclouvain/openjpeg/issues/731
- https://github.com/uclouvain/openjpeg/issues/732
- https://github.com/uclouvain/openjpeg/issues/777
- https://github.com/uclouvain/openjpeg/issues/778
- https://github.com/uclouvain/openjpeg/issues/779
- https://github.com/uclouvain/openjpeg/issues/780
- http://www.securityfocus.com/bid/100573
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2016-10506
low severity
- Vulnerable module: openjpeg2/libopenjp2-7
- Introduced through: openjpeg2/libopenjp2-7@2.5.0-2 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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: node@18.16.1-bookworm › pixman/libpixman-1-0@0.42.2-1
-
Introduced through: node@18.16.1-bookworm › 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, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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 libtiff. A specially crafted tiff file can lead to a segmentation fault due to a buffer overflow in the Fax3Encode function in libtiff/tif_fax3.c, resulting in a denial of service.
Remediation
There is no fixed version for Debian:12 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2023-3618
- https://access.redhat.com/security/cve/CVE-2023-3618
- https://bugzilla.redhat.com/show_bug.cgi?id=2215865
- https://lists.debian.org/debian-lts-announce/2023/07/msg00034.html
- https://security.netapp.com/advisory/ntap-20230824-0012/
- https://support.apple.com/kb/HT214036
- https://support.apple.com/kb/HT214037
- https://support.apple.com/kb/HT214038
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
- https://gitlab.com/libtiff/libtiff/-/issues/128
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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
- 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
- http://seclists.org/fulldisclosure/2024/Jul/16
- http://seclists.org/fulldisclosure/2024/Jul/17
- 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
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
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: node@18.16.1-bookworm › libwmf/libwmf-0.2-7@0.2.12-5.1
-
Introduced through: node@18.16.1-bookworm › libwmf/libwmf-dev@0.2.12-5.1
-
Introduced through: node@18.16.1-bookworm › 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
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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: node@18.16.1-bookworm › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: node@18.16.1-bookworm › 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, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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/wget
- Introduced through: wget/wget@1.21.3-1+b2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › wget/wget@1.21.3-1+b2
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: dav1d/libdav1d6
- Introduced through: dav1d/libdav1d6@1.0.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › dav1d/libdav1d6@1.0.0-2
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://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@lists.fedoraproject.org/message/3WGSO7UMOF4MVLQ5H6KIV7OG6ONS377B/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LXZ6CUNJFDJLCFOZHY2TIGMCAEITLCRP/
- https://security.gentoo.org/glsa/202310-05
- 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/
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:9.2p1-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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: node@18.16.1-bookworm › binutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-common@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libbinutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf-nobfd0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libgprofng0@2.40-2
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: node@18.16.1-bookworm › binutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-common@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libbinutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf-nobfd0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libgprofng0@2.40-2
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: node@18.16.1-bookworm › binutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-common@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/binutils-x86-64-linux-gnu@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libbinutils@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf-nobfd0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libctf0@2.40-2
-
Introduced through: node@18.16.1-bookworm › binutils/libgprofng0@2.40-2
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: node@18.16.1-bookworm › cairo/libcairo-gobject2@1.16.0-7
-
Introduced through: node@18.16.1-bookworm › cairo/libcairo-script-interpreter2@1.16.0-7
-
Introduced through: node@18.16.1-bookworm › cairo/libcairo2@1.16.0-7
-
Introduced through: node@18.16.1-bookworm › cairo/libcairo2-dev@1.16.0-7
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 and expat/libexpat1-dev@2.5.0-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › expat/libexpat1@2.5.0-1
-
Introduced through: node@18.16.1-bookworm › expat/libexpat1-dev@2.5.0-1
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: node@18.16.1-bookworm › gcc-12@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/cpp-12@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/g++-12@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libasan8@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libatomic1@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libcc1-0@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libgcc-12-dev@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libgomp1@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libitm1@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/liblsan0@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libquadmath0@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libstdc++-12-dev@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libstdc++6@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libtsan2@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libubsan1@12.2.0-14
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, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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: 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: node@18.16.1-bookworm › libpng1.6/libpng-dev@1.6.39-2
-
Introduced through: node@18.16.1-bookworm › 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: node@18.16.1-bookworm › openexr/libopenexr-3-1-30@3.1.5-5
-
Introduced through: node@18.16.1-bookworm › 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, pam/libpam-modules-bin@1.5.2-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › pam/libpam-modules@1.5.2-6
-
Introduced through: node@18.16.1-bookworm › pam/libpam-modules-bin@1.5.2-6
-
Introduced through: node@18.16.1-bookworm › pam/libpam-runtime@1.5.2-6
-
Introduced through: node@18.16.1-bookworm › pam/libpam0g@1.5.2-6
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: node@18.16.1-bookworm › 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: node@18.16.1-bookworm › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: node@18.16.1-bookworm › 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/security/cve/CVE-2023-4641
- https://bugzilla.redhat.com/show_bug.cgi?id=2215945
- https://access.redhat.com/errata/RHSA-2024:0417
- https://access.redhat.com/errata/RHSA-2024:2577
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2 and sqlite3/libsqlite3-dev@3.40.1-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › sqlite3/libsqlite3-0@3.40.1-2
-
Introduced through: node@18.16.1-bookworm › sqlite3/libsqlite3-dev@3.40.1-2
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 heap use-after-free issue has been identified in SQLite in the jsonParseAddNodeArray() function in sqlite3.c. This flaw allows a local attacker to leverage a victim to pass specially crafted malicious input to the application, potentially causing a crash and leading to a denial of service.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2024-0232
- https://access.redhat.com/security/cve/CVE-2024-0232
- https://bugzilla.redhat.com/show_bug.cgi?id=2243754
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QDCMYQ3J45NHQ4EJREM3BJNNKB5BK4Y7/
- https://security.netapp.com/advisory/ntap-20240315-0007/
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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.5.0 is vulnerable to Buffer Overflow in uv_encode() when libtiff reads a corrupted little-endian TIFF file and specifies the output to be big-endian.
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, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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.5.0 is vulnerable to Buffer Overflow via /libtiff/tools/tiffcrop.c:8499. Incorrect updating of buffer size after rotateImage() in tiffcrop cause heap-buffer-overflow and SEGV.
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, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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 null pointer dereference issue was found in Libtiff's tif_dir.c file. This issue may allow an attacker to pass a crafted TIFF image file to the tiffcp utility which triggers a runtime error that causes undefined behavior. This will result in an application crash, eventually leading to a denial of service.
Remediation
There is no fixed version for Debian:12 tiff.
References
- https://security-tracker.debian.org/tracker/CVE-2023-2908
- https://access.redhat.com/security/cve/CVE-2023-2908
- https://bugzilla.redhat.com/show_bug.cgi?id=2218830
- https://gitlab.com/libtiff/libtiff/-/commit/9bd48f0dbd64fb94dc2b5b05238fde0bfdd4ff3f
- https://gitlab.com/libtiff/libtiff/-/merge_requests/479
- https://lists.debian.org/debian-lts-announce/2023/07/msg00034.html
- https://security.netapp.com/advisory/ntap-20230731-0004/
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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.
loadImage() in tools/tiffcrop.c in LibTIFF through 4.5.0 has a heap-based use after free via a crafted TIFF image.
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, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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: util-linux/bsdutils
- Introduced through: util-linux/bsdutils@1:2.38.1-5+b1, util-linux/libblkid-dev@2.38.1-5+b1 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › util-linux/bsdutils@1:2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/libblkid-dev@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/libblkid1@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/libmount-dev@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/libmount1@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/libsmartcols1@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/libuuid1@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/mount@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/util-linux@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/util-linux-extra@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/uuid-dev@2.38.1-5+b1
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://security.netapp.com/advisory/ntap-20220331-0002/
- https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w%40ws.net.home/T/#u
- https://security.gentoo.org/glsa/202401-08
low severity
- Vulnerable module: patch
- Introduced through: patch@2.7.6-7
Detailed paths
-
Introduced through: node@18.16.1-bookworm › 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
- http://support.apple.com/kb/HT4723
- http://lists.apple.com/archives/security-announce/2011//Jun/msg00000.html
- https://security-tracker.debian.org/tracker/CVE-2010-4651
- 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: glib2.0/libglib2.0-0
- Introduced through: glib2.0/libglib2.0-0@2.74.6-2, glib2.0/libglib2.0-bin@2.74.6-2 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glib2.0/libglib2.0-0@2.74.6-2
-
Introduced through: node@18.16.1-bookworm › glib2.0/libglib2.0-bin@2.74.6-2
-
Introduced through: node@18.16.1-bookworm › glib2.0/libglib2.0-data@2.74.6-2
-
Introduced through: node@18.16.1-bookworm › glib2.0/libglib2.0-dev@2.74.6-2
-
Introduced through: node@18.16.1-bookworm › glib2.0/libglib2.0-dev-bin@2.74.6-2
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, glibc/libc-dev-bin@2.36-9 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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, glibc/libc-dev-bin@2.36-9 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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, imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › imagemagick@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6-common@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/imagemagick-6.q16@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-arch-config@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-6-extra@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickcore-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6-headers@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-6@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-6.q16-dev@8:6.9.11.60+dfsg-1.6
-
Introduced through: node@18.16.1-bookworm › imagemagick/libmagickwand-dev@8:6.9.11.60+dfsg-1.6
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: node@18.16.1-bookworm › libwmf/libwmf-0.2-7@0.2.12-5.1
-
Introduced through: node@18.16.1-bookworm › libwmf/libwmf-dev@0.2.12-5.1
-
Introduced through: node@18.16.1-bookworm › 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 and libxslt/libxslt1.1@1.1.35-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libxslt/libxslt1-dev@1.1.35-1
-
Introduced through: node@18.16.1-bookworm › libxslt/libxslt1.1@1.1.35-1
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
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › python3.11@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/python3.11-minimal@3.11.2-6
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 email module of Python through 3.11.3 incorrectly parses e-mail addresses that contain a special character. The wrong portion of an RFC2822 header is identified as the value of the addr-spec. In some applications, an attacker can bypass a protection mechanism in which application access is granted only after verifying receipt of e-mail to a specific domain (e.g., only @company.example.com addresses may be used for signup). This occurs in email/_parseaddr.py in recent versions of Python.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2023-27043
- http://python.com
- https://github.com/python/cpython/issues/102988
- http://python.org
- https://python-security.readthedocs.io/vuln/email-parseaddr-realname.html
- https://security.netapp.com/advisory/ntap-20230601-0003/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4ZAEFSFZDNBNJPNOUTLG5COISGQDLMGV/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ORLXS5YTKN65E2Q2NWKXMFS5FWQHRNZW/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PHVGRKQAGANCSGFI3QMYOCIMS4IFOZA5/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PU6Y2S5CBN5BWCBDAJFTGIBZLK3S2G3J/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SINP4OVYNB2AGDYI2GS37EMW3H3F7XPZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XWMBD4LNHWEXRI6YVFWJMTJQUL5WOFTS/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VZXC32CJ7TWDPJO6GY2XIQRO7JZX5FLP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/75DTHSTNOFFNAWHXKMDXS7EJWC6W2FUC/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ARI7VDSNTQVXRQFM6IK5GSSLEIYV4VZH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NEUNZSZ3CVSM2QWVYH3N2XGOCDWNYUA3/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/P2W2BZQIHMCKRI5FNBJERFYMS5PK6TAH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RDDC2VOX7OQC6OHMYTVD4HLFZIV6PYBC/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YQVY5C5REXWJIORJIL2FIL3ALOEJEF72/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SOX7BCN6YL7B3RFPEEXPIU5CMTEHJOKR/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/N6M5I6OQHJABNEYY555HUMMKX3Y4P25Z/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/P2MAICLFDDO3QVNHTZ2OCERZQ34R2PIC/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HXYVPEZUA3465AEFX5JVFVP7KIFZMF3N/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BQAKLUJMHFGVBRDPEY57BJGNCE5UUPHW/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QDRDDPDN3VFIYXJIYEABY6USX5EU66AG/
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.6-1 and systemd/libudev1@252.6-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › systemd/libsystemd0@252.6-1
-
Introduced through: node@18.16.1-bookworm › systemd/libudev1@252.6-1
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.6-1 and systemd/libudev1@252.6-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › systemd/libsystemd0@252.6-1
-
Introduced through: node@18.16.1-bookworm › systemd/libudev1@252.6-1
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.6-1 and systemd/libudev1@252.6-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › systemd/libsystemd0@252.6-1
-
Introduced through: node@18.16.1-bookworm › systemd/libudev1@252.6-1
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: mariadb/libmariadb-dev
- Introduced through: mariadb/libmariadb-dev@1:10.11.3-1, mariadb/libmariadb-dev-compat@1:10.11.3-1 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › mariadb/libmariadb-dev@1:10.11.3-1
-
Introduced through: node@18.16.1-bookworm › mariadb/libmariadb-dev-compat@1:10.11.3-1
-
Introduced through: node@18.16.1-bookworm › mariadb/libmariadb3@1:10.11.3-1
-
Introduced through: node@18.16.1-bookworm › mariadb/mariadb-common@1:10.11.3-1
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.
Vulnerability in the MySQL Server product of Oracle MySQL (component: Client: mysqldump). Supported versions that are affected are 8.0.36 and prior and 8.3.0 and prior. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where MySQL Server executes to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Server accessible data as well as unauthorized read access to a subset of MySQL Server accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L).
Remediation
There is no fixed version for Debian:12 mariadb.
References
- https://security-tracker.debian.org/tracker/CVE-2024-21096
- https://www.oracle.com/security-alerts/cpuapr2024.html
- https://security.netapp.com/advisory/ntap-20240426-0013/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KFYBDWDBE4YICSV34LJZGYRVSG6QIRKE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CKWVBZ6DBRFMLDXTHJUZ6LU7MJ5RTNA7/
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: node@18.16.1-bookworm › gcc-12@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/cpp-12@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/g++-12@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libasan8@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libatomic1@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libcc1-0@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libgcc-12-dev@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libgomp1@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libitm1@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/liblsan0@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libquadmath0@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libstdc++-12-dev@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libstdc++6@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libtsan2@12.2.0-14
-
Introduced through: node@18.16.1-bookworm › gcc-12/libubsan1@12.2.0-14
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: node@18.16.1-bookworm › 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: node@18.16.1-bookworm › 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: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.6-1 and systemd/libudev1@252.6-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › systemd/libsystemd0@252.6-1
-
Introduced through: node@18.16.1-bookworm › systemd/libudev1@252.6-1
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, glibc/libc-dev-bin@2.36-9 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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
Detailed paths
-
Introduced through: node@18.16.1-bookworm › gnutls28/libgnutls30@3.7.9-2
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: node@18.16.1-bookworm › libwmf/libwmf-0.2-7@0.2.12-5.1
-
Introduced through: node@18.16.1-bookworm › libwmf/libwmf-dev@0.2.12-5.1
-
Introduced through: node@18.16.1-bookworm › 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
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssh/openssh-client@1:9.2p1-2
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 and sqlite3/libsqlite3-dev@3.40.1-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › sqlite3/libsqlite3-0@3.40.1-2
-
Introduced through: node@18.16.1-bookworm › sqlite3/libsqlite3-dev@3.40.1-2
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: node@18.16.1-bookworm › 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: node
- Introduced through: node@18.16.1
- Fixed in: 18.18.2
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Information Exposure during the Cookie headers handling process. An attacker can potentially leak sensitive information to a third-party site or a malicious actor who can control the redirection target (i.e., an open redirector) by exploiting the disconnect between the spec's assumptions and the implementation of fetch.
Note:
This is only exploitable if the attacker can control the redirection target.
Remediation
Upgrade node to version 18.18.2, 20.8.1 or higher.
References
low severity
- Vulnerable module: node
- Introduced through: node@18.16.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Permissive Cross-domain Policy with Untrusted Domains due to not clearing Proxy-Authentication headers on cross-origin redirects. An attacker can intercept the improperly cleared headers.
Remediation
Upgrade node to version 18.19.1, 20.11.1, 21.6.2 or higher.
References
low severity
- Vulnerable module: apt
- Introduced through: apt@2.6.1 and apt/libapt-pkg6.0@2.6.1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › apt@2.6.1
-
Introduced through: node@18.16.1-bookworm › 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: curl
- Introduced through: curl@7.88.1-10, curl/libcurl3-gnutls@7.88.1-10 and others
- Fixed in: 7.88.1-10+deb12u4
Detailed paths
-
Introduced through: node@18.16.1-bookworm › curl@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl3-gnutls@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4-openssl-dev@7.88.1-10
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.
This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met.
libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers.
libcurl provides a function call that duplicates en easy handle called curl_easy_duphandle.
If a transfer has cookies enabled when the handle is duplicated, the
cookie-enable state is also cloned - but without cloning the actual
cookies. If the source handle did not read any cookies from a specific file on
disk, the cloned version of the handle would instead store the file name as
none (using the four ASCII letters, no quotes).
Subsequent use of the cloned handle that does not explicitly set a source to
load cookies from would then inadvertently load cookies from a file named
none - if such a file exists and is readable in the current directory of the
program using libcurl. And if using the correct file format of course.
Remediation
Upgrade Debian:12 curl to version 7.88.1-10+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-38546
- https://curl.se/docs/CVE-2023-38546.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OGMXNRNSJ4ETDK6FRNU3J7SABXPWCHSQ/
- https://support.apple.com/kb/HT214057
- https://support.apple.com/kb/HT214058
- https://support.apple.com/kb/HT214063
- https://support.apple.com/kb/HT214036
- http://seclists.org/fulldisclosure/2024/Jan/34
- http://seclists.org/fulldisclosure/2024/Jan/37
- http://seclists.org/fulldisclosure/2024/Jan/38
- https://forum.vmssoftware.com/viewtopic.php?f=8&t=8868
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: node@18.16.1-bookworm › gnupg2/dirmngr@2.2.40-1.1
-
Introduced through: node@18.16.1-bookworm › gnupg2/gnupg@2.2.40-1.1
-
Introduced through: node@18.16.1-bookworm › gnupg2/gnupg-l10n@2.2.40-1.1
-
Introduced through: node@18.16.1-bookworm › gnupg2/gnupg-utils@2.2.40-1.1
-
Introduced through: node@18.16.1-bookworm › gnupg2/gpg@2.2.40-1.1
-
Introduced through: node@18.16.1-bookworm › gnupg2/gpg-agent@2.2.40-1.1
-
Introduced through: node@18.16.1-bookworm › gnupg2/gpg-wks-client@2.2.40-1.1
-
Introduced through: node@18.16.1-bookworm › gnupg2/gpg-wks-server@2.2.40-1.1
-
Introduced through: node@18.16.1-bookworm › gnupg2/gpgconf@2.2.40-1.1
-
Introduced through: node@18.16.1-bookworm › gnupg2/gpgsm@2.2.40-1.1
-
Introduced through: node@18.16.1-bookworm › gnupg2/gpgv@2.2.40-1.1
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: node
- Introduced through: node@18.16.1
- Fixed in: 18.18.2
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Information Exposure via WebAssembly export names, which can be used to inject JavaScript that can expose data and functions that shouldn't be accessible to the WebAssembly application.
Note:
This vulnerability is exploitable when using the --experimental-wasm-modules CLI option.
Remediation
Upgrade node to version 18.18.2, 20.8.1 or higher.
References
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: node@18.16.1-bookworm › procps@2:4.0.2-3
-
Introduced through: node@18.16.1-bookworm › 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: node@18.16.1-bookworm › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: node@18.16.1-bookworm › 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: unzip
- Introduced through: unzip@6.0-28
Detailed paths
-
Introduced through: node@18.16.1-bookworm › 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: node
- Introduced through: node@18.16.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Authorization Bypass via fs.fchown or fs.fchmod operations which can use a "read-only" file descriptor to change the owner and permissions of a file.
Note: This is only exploitable for users using the experimental permission when the --allow-fs-write flag is used
Remediation
Upgrade node to version 20.15.1, 22.4.1 or higher.
References
low severity
- Vulnerable module: node
- Introduced through: node@18.16.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Authorization Bypass due to a failure to restrict file stats through the fs.lstat API that allows attackers to retrieve stats from files to which they do not have explicit read access.
Note: This is exploitable only for users of the experimental permission model when the --allow-fs-read flag is used.
Remediation
Upgrade node to version 20.15.1, 22.4.1 or higher.
References
low severity
- Vulnerable module: node
- Introduced through: node@18.16.1
Detailed paths
-
Introduced through: docker-image|node@18.16.1-bookworm › node@18.16.1
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Improper Handling of Values. This is because the Permission Model assumes wrongly that any path starting with two backslashes \ has a four-character prefix that can be ignored.
Note: This vulnerability affects only Windows users of the Node.js Permission Model
Remediation
Upgrade node to version 20.15.1, 22.4.1 or higher.
References
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › git@1:2.39.2-1.1
-
Introduced through: node@18.16.1-bookworm › git/git-man@1:2.39.2-1.1
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.
In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a consequence, Git is expected not to localize messages at all, and skips the gettext initialization. However, due to a change in MINGW-packages, the gettext() function's implicit initialization no longer uses the runtime prefix but uses the hard-coded path C:\mingw64\share\locale to look for localized messages. And since any authenticated user has the permission to create folders in C:\ (and since C:\mingw64 does not typically exist), it is possible for low-privilege users to place fake messages in that location where git.exe will pick them up in version 2.40.1.
This vulnerability is relatively hard to exploit and requires social engineering. For example, a legitimate message at the end of a clone could be maliciously modified to ask the user to direct their web browser to a malicious website, and the user might think that the message comes from Git and is legitimate. It does require local write access by the attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or alternatively create a C:\mingw64 folder and leave it empty. Users who have administrative rights may remove the permission to create folders in C:\.
Remediation
There is no fixed version for Debian:12 git.
References
- https://security-tracker.debian.org/tracker/CVE-2023-25815
- http://www.openwall.com/lists/oss-security/2023/04/25/2
- https://axcheron.github.io/exploit-101-format-strings/#writing-to-the-stack
- https://github.com/git-for-windows/git/releases/tag/v2.40.1.windows.1
- https://github.com/git-for-windows/git/security/advisories/GHSA-9w66-8mq8-5vm8
- https://github.com/msys2/MINGW-packages/pull/10461
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PI7FZ4NNR5S5J5K6AMVQBH2JFP6NE4L7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YFZWGQKB6MM5MNF2DLFTD7KS2KWPICKL/
- https://pubs.opengroup.org/onlinepubs/9699919799/functions/printf.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RKOXOAZ42HLXHXTW6JZI4L5DAIYDTYCU/
- https://security.gentoo.org/glsa/202312-15
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10, curl/libcurl3-gnutls@7.88.1-10 and others
- Fixed in: 7.88.1-10+deb12u6
Detailed paths
-
Introduced through: node@18.16.1-bookworm › curl@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl3-gnutls@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4-openssl-dev@7.88.1-10
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 a protocol selection parameter option disables all protocols without adding any then the default set of protocols would remain in the allowed set due to an error in the logic for removing protocols. The below command would perform a request to curl.se with a plaintext protocol which has been explicitly disabled. curl --proto -all,-http http://curl.se The flaw is only present if the set of selected protocols disables the entire set of available protocols, in itself a command with no practical use and therefore unlikely to be encountered in real situations. The curl security team has thus assessed this to be low severity bug.
Remediation
Upgrade Debian:12 curl to version 7.88.1-10+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2004
- https://curl.se/docs/CVE-2024-2004.html
- https://curl.se/docs/CVE-2024-2004.json
- https://hackerone.com/reports/2384833
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GMD6UYKCCRCYETWQZUJ65ZRFULT6SHLI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2D44YLAUFJU6BZ4XFG2FYV7SBKXB5IZ6/
- http://www.openwall.com/lists/oss-security/2024/03/27/1
- https://security.netapp.com/advisory/ntap-20240524-0006/
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10, curl/libcurl3-gnutls@7.88.1-10 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › curl@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl3-gnutls@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4-openssl-dev@7.88.1-10
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
- https://curl.se/docs/CVE-2024-2379.html
- https://curl.se/docs/CVE-2024-2379.json
- https://hackerone.com/reports/2410774
- http://www.openwall.com/lists/oss-security/2024/03/27/2
- 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
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
low severity
- Vulnerable module: curl
- Introduced through: curl@7.88.1-10, curl/libcurl3-gnutls@7.88.1-10 and others
- Fixed in: 7.88.1-10+deb12u6
Detailed paths
-
Introduced through: node@18.16.1-bookworm › curl@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl3-gnutls@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4@7.88.1-10
-
Introduced through: node@18.16.1-bookworm › curl/libcurl4-openssl-dev@7.88.1-10
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 an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated headers and instead leaks the memory. Further, this error condition fails silently and is therefore not easily detected by an application.
Remediation
Upgrade Debian:12 curl to version 7.88.1-10+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2398
- https://curl.se/docs/CVE-2024-2398.html
- https://curl.se/docs/CVE-2024-2398.json
- https://hackerone.com/reports/2402845
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GMD6UYKCCRCYETWQZUJ65ZRFULT6SHLI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2D44YLAUFJU6BZ4XFG2FYV7SBKXB5IZ6/
- http://www.openwall.com/lists/oss-security/2024/03/27/3
- https://security.netapp.com/advisory/ntap-20240503-0009/
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
low severity
- Vulnerable module: dav1d/libdav1d6
- Introduced through: dav1d/libdav1d6@1.0.0-2
- Fixed in: 1.0.0-2+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › dav1d/libdav1d6@1.0.0-2
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.
An integer overflow in dav1d AV1 decoder that can occur when decoding videos with large frame size. This can lead to memory corruption within the AV1 decoder. We recommend upgrading past version 1.4.0 of dav1d.
Remediation
Upgrade Debian:12 dav1d to version 1.0.0-2+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-1580
- https://code.videolan.org/videolan/dav1d/-/blob/master/NEWS
- https://code.videolan.org/videolan/dav1d/-/releases/1.4.0
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5EPMUNDMEBGESOJ2ZNCWYEAYOOEKNWOO/
- https://support.apple.com/kb/HT214093
- https://support.apple.com/kb/HT214095
- https://support.apple.com/kb/HT214096
- https://support.apple.com/kb/HT214097
- https://support.apple.com/kb/HT214098
- https://support.apple.com/kb/HT214094
- http://seclists.org/fulldisclosure/2024/Mar/36
- http://seclists.org/fulldisclosure/2024/Mar/37
- http://seclists.org/fulldisclosure/2024/Mar/38
- http://seclists.org/fulldisclosure/2024/Mar/39
- http://seclists.org/fulldisclosure/2024/Mar/40
- http://seclists.org/fulldisclosure/2024/Mar/41
low severity
- Vulnerable module: elfutils/libelf1
- Introduced through: elfutils/libelf1@0.188-2.1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › 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 and expat/libexpat1-dev@2.5.0-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › expat/libexpat1@2.5.0-1
-
Introduced through: node@18.16.1-bookworm › expat/libexpat1-dev@2.5.0-1
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
- 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://security.netapp.com/advisory/ntap-20240322-0001/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VK2O34GH43NTHBZBN7G5Y6YKJKPUCTBE/
- http://www.openwall.com/lists/oss-security/2024/03/15/1
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › git@1:2.39.2-1.1
-
Introduced through: node@18.16.1-bookworm › git/git-man@1:2.39.2-1.1
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 revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary code during the operation. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid cloning repositories from untrusted sources.
Remediation
There is no fixed version for Debian:12 git.
References
- https://security-tracker.debian.org/tracker/CVE-2024-32004
- https://git-scm.com/docs/git-clone
- https://github.com/git/git/commit/f4aa8c8bb11dae6e769cd930565173808cbb69c8
- https://github.com/git/git/security/advisories/GHSA-xfc6-vwr8-r389
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › git@1:2.39.2-1.1
-
Introduced through: node@18.16.1-bookworm › git/git-man@1:2.39.2-1.1
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 revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository's object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a "proper" clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.
Remediation
There is no fixed version for Debian:12 git.
References
- https://security-tracker.debian.org/tracker/CVE-2024-32020
- https://github.com/git/git/commit/1204e1a824c34071019fe106348eaa6d88f9528d
- https://github.com/git/git/commit/9e65df5eab274bf74c7b570107aacd1303a1e703
- https://github.com/git/git/security/advisories/GHSA-5rfh-556j-fhgj
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › git@1:2.39.2-1.1
-
Introduced through: node@18.16.1-bookworm › git/git-man@1:2.39.2-1.1
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 revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the objects/ directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary user-owned files on the same filesystem in the target Git repository's objects/ directory. When cloning a repository over the filesystem (without explicitly specifying the file:// protocol or --no-local), the optimizations for local cloning
will be used, which include attempting to hard link the object files instead of copying them. While the code includes checks against symbolic links in the source repository, which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check, and then a symlink during the operation, this will allow the adversary to bypass the check and create hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.
Remediation
There is no fixed version for Debian:12 git.
References
- https://security-tracker.debian.org/tracker/CVE-2024-32021
- https://github.com/git/git/security/advisories/GHSA-mvxm-9j2h-qjx7
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
low severity
- Vulnerable module: git
- Introduced through: git@1:2.39.2-1.1 and git/git-man@1:2.39.2-1.1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › git@1:2.39.2-1.1
-
Introduced through: node@18.16.1-bookworm › git/git-man@1:2.39.2-1.1
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 revision control system. The Git project recommends to avoid working in untrusted repositories, and instead to clone it first with git clone --no-local to obtain a clean copy. Git has specific protections to make that a safe operation even with an untrusted source repository, but vulnerabilities allow those protections to be bypassed. In the context of cloning local repositories owned by other users, this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for CVE-2024-32004 are not enough: For example, when obtaining a .zip file containing a full copy of a Git repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run within the context of that repository. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid using Git in repositories that have been obtained via archives from untrusted sources.
Remediation
There is no fixed version for Debian:12 git.
References
- https://security-tracker.debian.org/tracker/CVE-2024-32465
- https://git-scm.com/docs/git#_security
- https://git-scm.com/docs/git-clone
- https://github.com/git/git/commit/7b70e9efb18c2cc3f219af399bd384c5801ba1d7
- https://github.com/git/git/security/advisories/GHSA-vm9j-46j9-qvq4
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
low severity
- Vulnerable module: glib2.0/libglib2.0-0
- Introduced through: glib2.0/libglib2.0-0@2.74.6-2, glib2.0/libglib2.0-bin@2.74.6-2 and others
- Fixed in: 2.74.6-2+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glib2.0/libglib2.0-0@2.74.6-2
-
Introduced through: node@18.16.1-bookworm › glib2.0/libglib2.0-bin@2.74.6-2
-
Introduced through: node@18.16.1-bookworm › glib2.0/libglib2.0-data@2.74.6-2
-
Introduced through: node@18.16.1-bookworm › glib2.0/libglib2.0-dev@2.74.6-2
-
Introduced through: node@18.16.1-bookworm › glib2.0/libglib2.0-dev-bin@2.74.6-2
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.
An issue was discovered in GNOME GLib before 2.78.5, and 2.79.x and 2.80.x before 2.80.1. When a GDBus-based client subscribes to signals from a trusted system service such as NetworkManager on a shared computer, other users of the same computer can send spoofed D-Bus signals that the GDBus-based client will wrongly interpret as having been sent by the trusted system service. This could lead to the GDBus-based client behaving incorrectly, with an application-dependent impact.
Remediation
Upgrade Debian:12 glib2.0 to version 2.74.6-2+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-34397
- https://gitlab.gnome.org/GNOME/glib/-/issues/3268
- https://www.openwall.com/lists/oss-security/2024/05/07/5
- https://lists.debian.org/debian-lts-announce/2024/05/msg00008.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IRSFYAE5X23TNRWX7ZWEJOMISLCDSYNS/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UNFJHISR4O6VFOHBFWH5I5WWMG37H63A/
- https://security.netapp.com/advisory/ntap-20240531-0008/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LCDY3KA7G7D3DRXYTT46K6LFHS2KHWBH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LL6HSJDXCXMLEIJBYV6CPOR4K2NTCTXW/
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9, glibc/libc-dev-bin@2.36-9 and others
- Fixed in: 2.36-9+deb12u6
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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 iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2961
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0004
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/P3I4KYS6EU6S7QZ47WFNTPVAHFIUQNEL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YAMJQI3Y6BHWV3CUTYBXOZONCUJNOB2Z/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BTJFBGHDYG5PEIFD5WSSSKSFZ2AZWC5N/
- http://www.openwall.com/lists/oss-security/2024/04/24/2
- http://www.openwall.com/lists/oss-security/2024/04/17/9
- http://www.openwall.com/lists/oss-security/2024/04/18/4
- https://lists.debian.org/debian-lts-announce/2024/05/msg00001.html
- http://www.openwall.com/lists/oss-security/2024/05/27/1
- http://www.openwall.com/lists/oss-security/2024/05/27/2
- http://www.openwall.com/lists/oss-security/2024/05/27/6
- http://www.openwall.com/lists/oss-security/2024/05/27/3
- http://www.openwall.com/lists/oss-security/2024/05/27/4
- http://www.openwall.com/lists/oss-security/2024/05/27/5
- https://security.netapp.com/advisory/ntap-20240531-0002/
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://github.com/ambionics/cnext-exploits
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9, glibc/libc-dev-bin@2.36-9 and others
- Fixed in: 2.36-9+deb12u7
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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.
nscd: Stack-based buffer overflow in netgroup cache
If the Name Service Cache Daemon's (nscd) fixed size cache is exhausted by client requests then a subsequent client request for netgroup data may result in a stack-based buffer overflow. This flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-33599
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0005
- https://security.netapp.com/advisory/ntap-20240524-0011/
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- http://www.openwall.com/lists/oss-security/2024/07/22/5
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9, glibc/libc-dev-bin@2.36-9 and others
- Fixed in: 2.36-9+deb12u7
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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.
nscd: Null pointer crashes after notfound response
If the Name Service Cache Daemon's (nscd) cache fails to add a not-found netgroup response to the cache, the client request can result in a null pointer dereference. This flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-33600
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0006
- https://security.netapp.com/advisory/ntap-20240524-0013/
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- http://www.openwall.com/lists/oss-security/2024/07/22/5
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9, glibc/libc-dev-bin@2.36-9 and others
- Fixed in: 2.36-9+deb12u7
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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.
nscd: netgroup cache may terminate daemon on memory allocation failure
The Name Service Cache Daemon's (nscd) netgroup cache uses xmalloc or xrealloc and these functions may terminate the process due to a memory allocation failure resulting in a denial of service to the clients. The flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-33601
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0007
- https://security.netapp.com/advisory/ntap-20240524-0014/
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- http://www.openwall.com/lists/oss-security/2024/07/22/5
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9, glibc/libc-dev-bin@2.36-9 and others
- Fixed in: 2.36-9+deb12u7
Detailed paths
-
Introduced through: node@18.16.1-bookworm › glibc/libc-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc-dev-bin@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6@2.36-9
-
Introduced through: node@18.16.1-bookworm › glibc/libc6-dev@2.36-9
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.
nscd: netgroup cache assumes NSS callback uses in-buffer strings
The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory when the NSS callback does not store all strings in the provided buffer. The flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-33602
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0008
- https://security.netapp.com/advisory/ntap-20240524-0012/
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- http://www.openwall.com/lists/oss-security/2024/07/22/5
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2
- Fixed in: 3.7.9-2+deb12u3
Detailed paths
-
Introduced through: node@18.16.1-bookworm › gnutls28/libgnutls30@3.7.9-2
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.
A flaw was found in GnuTLS. The Minerva attack is a cryptographic vulnerability that exploits deterministic behavior in systems like GnuTLS, leading to side-channel leaks. In specific scenarios, such as when using the GNUTLS_PRIVKEY_FLAG_REPRODUCIBLE flag, it can result in a noticeable step in nonce size from 513 to 512 bits, exposing a potential timing side-channel.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28834
- https://access.redhat.com/security/cve/CVE-2024-28834
- https://bugzilla.redhat.com/show_bug.cgi?id=2269228
- https://lists.gnupg.org/pipermail/gnutls-help/2024-March/004845.html
- https://people.redhat.com/~hkario/marvin/
- https://access.redhat.com/errata/RHSA-2024:1784
- https://minerva.crocs.fi.muni.cz/
- https://access.redhat.com/errata/RHSA-2024:1879
- https://access.redhat.com/errata/RHSA-2024:1997
- https://access.redhat.com/errata/RHSA-2024:2044
- https://access.redhat.com/errata/RHSA-2024:2570
- http://www.openwall.com/lists/oss-security/2024/03/22/1
- http://www.openwall.com/lists/oss-security/2024/03/22/2
- https://access.redhat.com/errata/RHSA-2024:2889
- https://security.netapp.com/advisory/ntap-20240524-0004/
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2
- Fixed in: 3.7.9-2+deb12u3
Detailed paths
-
Introduced through: node@18.16.1-bookworm › gnutls28/libgnutls30@3.7.9-2
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.
A flaw has been discovered in GnuTLS where an application crash can be induced when attempting to verify a specially crafted .pem bundle using the "certtool --verify-chain" command.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28835
- https://access.redhat.com/security/cve/CVE-2024-28835
- https://bugzilla.redhat.com/show_bug.cgi?id=2269084
- https://lists.gnupg.org/pipermail/gnutls-help/2024-March/004845.html
- https://access.redhat.com/errata/RHSA-2024:1879
- https://access.redhat.com/errata/RHSA-2024:2570
- http://www.openwall.com/lists/oss-security/2024/03/22/1
- http://www.openwall.com/lists/oss-security/2024/03/22/2
- https://access.redhat.com/errata/RHSA-2024:2889
low severity
- Vulnerable module: krb5/krb5-multidev
- Introduced through: krb5/krb5-multidev@1.20.1-2, krb5/libgssapi-krb5-2@1.20.1-2 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › krb5/krb5-multidev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssapi-krb5-2@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssrpc4@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libk5crypto3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5clnt-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5srv-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkdb5-10@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-dev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5support0@1.20.1-2
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, krb5/libgssapi-krb5-2@1.20.1-2 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › krb5/krb5-multidev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssapi-krb5-2@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssrpc4@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libk5crypto3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5clnt-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5srv-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkdb5-10@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-dev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5support0@1.20.1-2
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, krb5/libgssapi-krb5-2@1.20.1-2 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › krb5/krb5-multidev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssapi-krb5-2@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libgssrpc4@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libk5crypto3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5clnt-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkadm5srv-mit12@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkdb5-10@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-3@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5-dev@1.20.1-2
-
Introduced through: node@18.16.1-bookworm › krb5/libkrb5support0@1.20.1-2
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: libde265/libde265-0
- Introduced through: libde265/libde265-0@1.0.11-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libde265/libde265-0@1.0.11-1
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
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libde265/libde265-0@1.0.11-1
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
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libde265/libde265-0@1.0.11-1
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: node@18.16.1-bookworm › 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
low severity
- Vulnerable module: libheif/libheif1
- Introduced through: libheif/libheif1@1.15.1-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libheif/libheif1@1.15.1-1
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
- Vulnerable module: libxml2
- Introduced through: libxml2@2.9.14+dfsg-1.2 and libxml2/libxml2-dev@2.9.14+dfsg-1.2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › libxml2@2.9.14+dfsg-1.2
-
Introduced through: node@18.16.1-bookworm › libxml2/libxml2-dev@2.9.14+dfsg-1.2
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/INKSSLW5VMZIXHRPZBAW4TJUX5SQKARG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VRDJCNQP32LV56KESUQ5SNZKAJWSZZRI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/5HVUXKYTBWT3G5DEEQX62STJQBY367NL/
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: node@18.16.1-bookworm › ncurses/libncurses-dev@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/libncurses5-dev@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/libncurses6@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/libncursesw5-dev@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/libncursesw6@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/libtinfo6@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/ncurses-base@6.4-4
-
Introduced through: node@18.16.1-bookworm › ncurses/ncurses-bin@6.4-4
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.
ncurses 6.4-20230610 has a NULL pointer dereference in tgetstr in tinfo/lib_termcap.c.
Remediation
There is no fixed version for Debian:12 ncurses.
References
low severity
- Vulnerable module: nghttp2/libnghttp2-14
- Introduced through: nghttp2/libnghttp2-14@1.52.0-1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › nghttp2/libnghttp2-14@1.52.0-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. The nghttp2 library prior to version 1.61.0 keeps reading the unbounded number of HTTP/2 CONTINUATION frames even after a stream is reset to keep HPACK context in sync. This causes excessive CPU usage to decode HPACK stream. nghttp2 v1.61.0 mitigates this vulnerability by limiting the number of CONTINUATION frames it accepts per stream. There is no workaround for this vulnerability.
Remediation
There is no fixed version for Debian:12 nghttp2.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28182
- https://github.com/nghttp2/nghttp2/commit/00201ecd8f982da3b67d4f6868af72a1b03b14e0
- https://github.com/nghttp2/nghttp2/commit/d71a4668c6bead55805d18810d633fbb98315af9
- https://github.com/nghttp2/nghttp2/security/advisories/GHSA-x6x3-gv8h-m57q
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AGOME6ZXJG7664IPQNVE3DL67E3YP3HY/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/J6ZMXUGB66VAXDW5J6QSTHM5ET25FGSA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PXJO2EASHM2OQQLGVDY5ZSO7UVDVHTDK/
- https://lists.debian.org/debian-lts-announce/2024/04/msg00026.html
- http://www.openwall.com/lists/oss-security/2024/04/03/16
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: node@18.16.1-bookworm › openexr/libopenexr-3-1-30@3.1.5-5
-
Introduced through: node@18.16.1-bookworm › 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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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 and openjpeg2/libopenjp2-7-dev@2.5.0-2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7@2.5.0-2
-
Introduced through: node@18.16.1-bookworm › openjpeg2/libopenjp2-7-dev@2.5.0-2
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
- Vulnerable module: openssl
- Introduced through: openssl@3.0.9-1, openssl/libssl-dev@3.0.9-1 and others
- Fixed in: 3.0.13-1~deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssl@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl-dev@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl3@3.0.9-1
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: Checking excessively long invalid RSA public keys may take a long time.
Impact summary: Applications that use the function EVP_PKEY_public_check() to check RSA public keys may experience long delays. Where the key that is being checked has been obtained from an untrusted source this may lead to a Denial of Service.
When function EVP_PKEY_public_check() is called on RSA public keys, a computation is done to confirm that the RSA modulus, n, is composite. For valid RSA keys, n is a product of two or more large primes and this computation completes quickly. However, if n is an overly large prime, then this computation would take a long time.
An application that calls EVP_PKEY_public_check() and supplies an RSA key obtained from an untrusted source could be vulnerable to a Denial of Service attack.
The function EVP_PKEY_public_check() is not called from other OpenSSL functions however it is called from the OpenSSL pkey command line application. For that reason that application is also vulnerable if used with the '-pubin' and '-check' options on untrusted data.
The OpenSSL SSL/TLS implementation is not affected by this issue.
The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.13-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-6237
- https://github.com/openssl/openssl/commit/0b0f7abfb37350794a4b8960fafc292cd5d1b84d
- https://github.com/openssl/openssl/commit/18c02492138d1eb8b6548cb26e7b625fb2414a2a
- https://github.com/openssl/openssl/commit/a830f551557d3d66a84bbb18a5b889c640c36294
- https://www.openssl.org/news/secadv/20240115.txt
- http://www.openwall.com/lists/oss-security/2024/03/11/1
- https://security.netapp.com/advisory/ntap-20240531-0007/
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.9-1, openssl/libssl-dev@3.0.9-1 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssl@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl-dev@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl3@3.0.9-1
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: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions
Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service
This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation.
This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients.
The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
Remediation
There is no fixed version for Debian:12 openssl.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2511
- https://github.com/openssl/openssl/commit/7e4d731b1c07201ad9374c1cd9ac5263bdf35bce
- https://github.com/openssl/openssl/commit/b52867a9f618bb955bed2a3ce3db4d4f97ed8e5d
- https://github.com/openssl/openssl/commit/e9d7083e241670332e0443da0f0d4ffb52829f08
- https://github.openssl.org/openssl/extended-releases/commit/5f8d25770ae6437db119dfc951e207271a326640
- https://www.openssl.org/news/secadv/20240408.txt
- http://www.openwall.com/lists/oss-security/2024/04/08/5
- https://security.netapp.com/advisory/ntap-20240503-0013/
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.9-1, openssl/libssl-dev@3.0.9-1 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssl@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl-dev@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl3@3.0.9-1
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: Checking excessively long DSA keys or parameters may be very slow.
Impact summary: Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.
The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform
various checks on DSA parameters. Some of those computations take a long time
if the modulus (p parameter) is too large.
Trying to use a very large modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in length for signature verification. However the key and parameter check functions do not limit the modulus size when performing the checks.
An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.
These functions are not called by OpenSSL itself on untrusted DSA keys so only applications that directly call these functions may be vulnerable.
Also vulnerable are the OpenSSL pkey and pkeyparam command line applications
when using the -check option.
The OpenSSL SSL/TLS implementation is not affected by this issue.
The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.
Remediation
There is no fixed version for Debian:12 openssl.
References
- https://security-tracker.debian.org/tracker/CVE-2024-4603
- https://github.com/openssl/openssl/commit/3559e868e58005d15c6013a0c1fd832e51c73397
- https://github.com/openssl/openssl/commit/53ea06486d296b890d565fb971b2764fcd826e7e
- https://github.com/openssl/openssl/commit/9c39b3858091c152f52513c066ff2c5a47969f0d
- https://github.com/openssl/openssl/commit/da343d0605c826ef197aceedc67e8e04f065f740
- https://www.openssl.org/news/secadv/20240516.txt
- http://www.openwall.com/lists/oss-security/2024/05/16/2
- https://security.netapp.com/advisory/ntap-20240621-0001/
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.9-1, openssl/libssl-dev@3.0.9-1 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssl@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl-dev@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl3@3.0.9-1
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Debian:12 openssl.
References
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.9-1, openssl/libssl-dev@3.0.9-1 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › openssl@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl-dev@3.0.9-1
-
Introduced through: node@18.16.1-bookworm › openssl/libssl3@3.0.9-1
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: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer.
Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application.
The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists).
This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem.
In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur.
This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available.
Remediation
There is no fixed version for Debian:12 openssl.
References
- https://security-tracker.debian.org/tracker/CVE-2024-5535
- https://github.com/openssl/openssl/commit/4ada436a1946cbb24db5ab4ca082b69c1bc10f37
- https://github.com/openssl/openssl/commit/99fb785a5f85315b95288921a321a935ea29a51e
- https://github.com/openssl/openssl/commit/cf6f91f6121f4db167405db2f0de410a456f260c
- https://github.com/openssl/openssl/commit/e86ac436f0bd54d4517745483e2315650fae7b2c
- https://github.openssl.org/openssl/extended-releases/commit/9947251413065a05189a63c9b7a6c1d4e224c21c
- https://github.openssl.org/openssl/extended-releases/commit/b78ec0824da857223486660177d3b1f255c65d87
- https://www.openssl.org/news/secadv/20240627.txt
- http://www.openwall.com/lists/oss-security/2024/06/27/1
- http://www.openwall.com/lists/oss-security/2024/06/28/4
- https://security.netapp.com/advisory/ntap-20240712-0005/
low severity
- Vulnerable module: postgresql-15/libpq-dev
- Introduced through: postgresql-15/libpq-dev@15.3-0+deb12u1 and postgresql-15/libpq5@15.3-0+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq-dev@15.3-0+deb12u1
-
Introduced through: node@18.16.1-bookworm › postgresql-15/libpq5@15.3-0+deb12u1
NVD Description
Note: Versions mentioned in the description apply only to the upstream postgresql-15 package and not the postgresql-15 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Missing authorization in PostgreSQL built-in views pg_stats_ext and pg_stats_ext_exprs allows an unprivileged database user to read most common values and other statistics from CREATE STATISTICS commands of other users. The most common values may reveal column values the eavesdropper could not otherwise read or results of functions they cannot execute. Installing an unaffected version only fixes fresh PostgreSQL installations, namely those that are created with the initdb utility after installing that version. Current PostgreSQL installations will remain vulnerable until they follow the instructions in the release notes. Within major versions 14-16, minor versions before PostgreSQL 16.3, 15.7, and 14.12 are affected. Versions before PostgreSQL 14 are unaffected.
Remediation
There is no fixed version for Debian:12 postgresql-15.
References
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › python3.11@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/python3.11-minimal@3.11.2-6
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.
An issue was found in the CPython tempfile.TemporaryDirectory class affecting versions 3.12.1, 3.11.7, 3.10.13, 3.9.18, and 3.8.18 and prior.
The tempfile.TemporaryDirectory class would dereference symlinks during cleanup of permissions-related errors. This means users which can run privileged programs are potentially able to modify permissions of files referenced by symlinks in some circumstances.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-6597
- https://github.com/python/cpython/commit/02a9259c717738dfe6b463c44d7e17f2b6d2cb3a
- https://github.com/python/cpython/commit/5585334d772b253a01a6730e8202ffb1607c3d25
- https://github.com/python/cpython/commit/6ceb8aeda504b079fef7a57b8d81472f15cdd9a5
- https://github.com/python/cpython/commit/81c16cd94ec38d61aa478b9a452436dc3b1b524d
- https://github.com/python/cpython/commit/8eaeefe49d179ca4908d052745e3bb8b6f238f82
- https://github.com/python/cpython/commit/d54e22a669ae6e987199bb5d2c69bb5a46b0083b
- https://github.com/python/cpython/issues/91133
- https://mail.python.org/archives/list/security-announce@python.org/thread/Q5C6ATFC67K53XFV4KE45325S7NS62LD/
- https://lists.debian.org/debian-lts-announce/2024/03/msg00025.html
- http://www.openwall.com/lists/oss-security/2024/03/20/5
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T3IGRX54M7RNCQOXVQO5KQKTGWCOABIM/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U5VHWS52HGD743C47UMCSAK2A773M2YE/
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u3
Detailed paths
-
Introduced through: node@18.16.1-bookworm › python3.11@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/python3.11-minimal@3.11.2-6
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.
A defect was discovered in the Python “ssl” module where there is a memory race condition with the ssl.SSLContext methods “cert_store_stats()” and “get_ca_certs()”. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-0397
- https://github.com/python/cpython/commit/01c37f1d0714f5822d34063ca7180b595abf589d
- https://github.com/python/cpython/commit/29c97287d205bf2f410f4895ebce3f43b5160524
- https://github.com/python/cpython/commit/37324b421b72b7bc9934e27aba85d48d4773002e
- https://github.com/python/cpython/commit/542f3272f56f31ed04e74c40635a913fbc12d286
- https://github.com/python/cpython/commit/b228655c227b2ca298a8ffac44d14ce3d22f6faa
- https://github.com/python/cpython/commit/bce693111bff906ccf9281c22371331aaff766ab
- https://github.com/python/cpython/issues/114572
- https://github.com/python/cpython/pull/114573
- https://mail.python.org/archives/list/security-announce@python.org/thread/BMAK5BCGKYWNJOACVUSLUF6SFGBIM4VP/
- http://www.openwall.com/lists/oss-security/2024/06/17/2
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u2
Detailed paths
-
Introduced through: node@18.16.1-bookworm › python3.11@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/python3.11-minimal@3.11.2-6
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.
An issue was found in the CPython zipfile module affecting versions 3.12.1, 3.11.7, 3.10.13, 3.9.18, and 3.8.18 and prior.
The zipfile module is vulnerable to “quoted-overlap” zip-bombs which exploit the zip format to create a zip-bomb with a high compression ratio. The fixed versions of CPython makes the zipfile module reject zip archives which overlap entries in the archive.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-0450
- https://github.com/python/cpython/commit/30fe5d853b56138dbec62432d370a1f99409fc85
- https://github.com/python/cpython/commit/66363b9a7b9fe7c99eba3a185b74c5fdbf842eba
- https://github.com/python/cpython/commit/a2c59992e9e8d35baba9695eb186ad6c6ff85c51
- https://github.com/python/cpython/commit/a956e510f6336d5ae111ba429a61c3ade30a7549
- https://github.com/python/cpython/commit/d05bac0b74153beb541b88b4fca33bf053990183
- https://github.com/python/cpython/commit/fa181fcf2156f703347b03a3b1966ce47be8ab3b
- https://github.com/python/cpython/issues/109858
- https://mail.python.org/archives/list/security-announce@python.org/thread/XELNUX2L3IOHBTFU7RQHCY6OUVEWZ2FG/
- https://www.bamsoftware.com/hacks/zipbomb/
- https://lists.debian.org/debian-lts-announce/2024/03/msg00024.html
- https://lists.debian.org/debian-lts-announce/2024/03/msg00025.html
- http://www.openwall.com/lists/oss-security/2024/03/20/5
- https://github.com/python/cpython/commit/70497218351ba44bffc8b571201ecb5652d84675
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T3IGRX54M7RNCQOXVQO5KQKTGWCOABIM/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U5VHWS52HGD743C47UMCSAK2A773M2YE/
low severity
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u3
Detailed paths
-
Introduced through: node@18.16.1-bookworm › python3.11@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/python3.11-minimal@3.11.2-6
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 “ipaddress” module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as “globally reachable” or “private”. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn’t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries.
CPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-4032
- https://github.com/python/cpython/issues/113171
- https://github.com/python/cpython/pull/113179
- https://mail.python.org/archives/list/security-announce@python.org/thread/NRUHDUS2IV2USIZM2CVMSFL6SCKU3RZA/
- https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
- https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml
- https://github.com/python/cpython/commit/22adf29da8d99933ffed8647d3e0726edd16f7f8
- https://github.com/python/cpython/commit/40d75c2b7f5c67e254d0a025e0f2e2c7ada7f69f
- https://github.com/python/cpython/commit/895f7e2ac23eff4743143beef0f0c5ac71ea27d3
- https://github.com/python/cpython/commit/ba431579efdcbaed7a96f2ac4ea0775879a332fb
- https://github.com/python/cpython/commit/c62c9e518b784fe44432a3f4fc265fb95b651906
- https://github.com/python/cpython/commit/f86b17ac511e68192ba71f27e752321a3252cee3
- http://www.openwall.com/lists/oss-security/2024/06/17/3
- https://security.netapp.com/advisory/ntap-20240726-0004/
low severity
new
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › python3.11@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/python3.11-minimal@3.11.2-6
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.
There is a MEDIUM severity vulnerability affecting CPython.
The email module didn’t properly quote newlines for email headers when serializing an email message allowing for header injection when an email is serialized.
Remediation
There is no fixed version for Debian:12 python3.11.
References
- https://security-tracker.debian.org/tracker/CVE-2024-6923
- https://github.com/python/cpython/issues/121650
- https://github.com/python/cpython/pull/122233
- https://mail.python.org/archives/list/security-announce@python.org/thread/QH3BUOE2DYQBWP7NAQ7UNHPPOELKISRW/
- https://github.com/python/cpython/commit/4766d1200fdf8b6728137aa2927a297e224d5fa7
- https://github.com/python/cpython/commit/4aaa4259b5a6e664b7316a4d60bdec7ee0f124d0
low severity
new
- Vulnerable module: python3.11
- Introduced through: python3.11@3.11.2-6, python3.11/libpython3.11-minimal@3.11.2-6 and others
- Fixed in: 3.11.2-6+deb12u3
Detailed paths
-
Introduced through: node@18.16.1-bookworm › python3.11@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-minimal@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/libpython3.11-stdlib@3.11.2-6
-
Introduced through: node@18.16.1-bookworm › python3.11/python3.11-minimal@3.11.2-6
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.
There is a HIGH severity vulnerability affecting the CPython "zipfile" module affecting "zipfile.Path". Note that the more common API "zipfile.ZipFile" class is unaffected.
When iterating over names of entries in a zip archive (for example, methods of "zipfile.Path" like "namelist()", "iterdir()", etc) the process can be put into an infinite loop with a maliciously crafted zip archive. This defect applies when reading only metadata or extracting the contents of the zip archive. Programs that are not handling user-controlled zip archives are not affected.
Remediation
Upgrade Debian:12 python3.11 to version 3.11.2-6+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-8088
- https://github.com/python/cpython/commit/795f2597a4be988e2bb19b69ff9958e981cb894e
- https://github.com/python/cpython/commit/8c7348939d8a3ecd79d630075f6be1b0c5b41f64
- https://github.com/python/cpython/commit/dcc5182f27c1500006a1ef78e10613bb45788dea
- https://github.com/python/cpython/issues/122905
- https://github.com/python/cpython/pull/122906
- https://mail.python.org/archives/list/security-announce@python.org/thread/GNFCKVI4TCATKQLALJ5SN4L4CSPSMILU/
- https://github.com/python/cpython/commit/e0264a61119d551658d9445af38323ba94fc16db
- https://github.com/python/cpython/issues/123270
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.6-1 and systemd/libudev1@252.6-1
- Fixed in: 252.23-1~deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › systemd/libsystemd0@252.6-1
-
Introduced through: node@18.16.1-bookworm › systemd/libudev1@252.6-1
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.
The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 5155 specification implies that an algorithm must perform thousands of iterations of a hash function in certain situations.
Remediation
Upgrade Debian:12 systemd to version 252.23-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-50868
- https://datatracker.ietf.org/doc/html/rfc5155
- https://docs.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-01.html
- https://kb.isc.org/docs/cve-2023-50868
- https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/
- https://www.isc.org/blogs/2024-bind-security-release/
- https://gitlab.nic.cz/knot/knot-resolver/-/releases/v5.7.1
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html
- https://access.redhat.com/security/cve/CVE-2023-50868
- https://bugzilla.suse.com/show_bug.cgi?id=1219826
- http://www.openwall.com/lists/oss-security/2024/02/16/2
- http://www.openwall.com/lists/oss-security/2024/02/16/3
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SVYA42BLXUCIDLD35YIJPJSHDIADNYMP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BUIP7T7Z4T3UHLXFWG6XIVDP4GYPD3AI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNNHZSZPG2E7NBMBNYPGHCFI4V4XRWNQ/
- https://lists.debian.org/debian-lts-announce/2024/02/msg00006.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TEXGOYGW7DBS3N2QSSQONZ4ENIRQEAPG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UQESRWMJCF4JEYJEAKLRM6CT55GLJAB7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HVRDSJVZKMCXKKPP6PNR62T7RWZ3YSDZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RGS7JN6FZXUSTC2XKQHH27574XOULYYJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6FV5O347JTX7P5OZA6NGO4MKTXRXMKOZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IGSLGKUAQTW5JPPZCMF5YPEYALLRUZZ6/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZDZFMEKQTZ4L7RY46FCENWFB5MDT263R/
- https://security.netapp.com/advisory/ntap-20240307-0008/
- https://lists.debian.org/debian-lts-announce/2024/05/msg00011.html
low severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1.2
- Fixed in: 1.34+dfsg-1.2+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tar@1.34+dfsg-1.2
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.
In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c.
Remediation
Upgrade Debian:12 tar to version 1.34+dfsg-1.2+deb12u1 or higher.
References
low severity
- Vulnerable module: tiff/libtiff-dev
- Introduced through: tiff/libtiff-dev@4.5.0-6, tiff/libtiff6@4.5.0-6 and others
Detailed paths
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff-dev@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiff6@4.5.0-6
-
Introduced through: node@18.16.1-bookworm › tiff/libtiffxx6@4.5.0-6
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 the libtiff library. An out-of-memory issue in the TIFFReadEncodedStrip function can be triggered when processing a crafted tiff file, allowing attackers to perform memory allocation of arbitrary sizes, resulting in a denial of service.
Remediation
There is no fixed version for Debian:12 tiff.
References
low severity
- Vulnerable module: util-linux/libblkid-dev
- Introduced through: util-linux/libblkid-dev@2.38.1-5+b1, util-linux/libblkid1@2.38.1-5+b1 and others
- Fixed in: 2.38.1-5+deb12u1
Detailed paths
-
Introduced through: node@18.16.1-bookworm › util-linux/libblkid-dev@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/libblkid1@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/libmount-dev@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/libmount1@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/libsmartcols1@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/libuuid1@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/mount@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/util-linux@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/util-linux-extra@2.38.1-5+b1
-
Introduced through: node@18.16.1-bookworm › util-linux/uuid-dev@2.38.1-5+b1
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.
wall in util-linux through 2.40, often installed with setgid tty permissions, allows escape sequences to be sent to other users' terminals through argv. (Specifically, escape sequences received from stdin are blocked, but escape sequences received from argv are not blocked.) There may be plausible scenarios where this leads to account takeover.
Remediation
Upgrade Debian:12 util-linux to version 2.38.1-5+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28085
- https://github.com/skyler-ferrante/CVE-2024-28085
- https://github.com/util-linux/util-linux/security/advisories/GHSA-xv2h-c6ww-mrjq
- https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/
- https://people.rit.edu/sjf5462/6831711781/wall_2_27_2024.txt
- https://www.openwall.com/lists/oss-security/2024/03/27/5
- https://lists.debian.org/debian-lts-announce/2024/04/msg00005.html
- http://www.openwall.com/lists/oss-security/2024/03/27/6
- http://www.openwall.com/lists/oss-security/2024/03/27/9
- http://www.openwall.com/lists/oss-security/2024/03/28/1
- http://www.openwall.com/lists/oss-security/2024/03/27/5
- http://www.openwall.com/lists/oss-security/2024/03/27/7
- http://www.openwall.com/lists/oss-security/2024/03/27/8
- http://www.openwall.com/lists/oss-security/2024/03/28/2
- http://www.openwall.com/lists/oss-security/2024/03/28/3
- https://security.netapp.com/advisory/ntap-20240531-0003/