-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
change: cve.js for new data structure #4281
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Snapshot WarningsEnsure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice. OpenSSF Scorecard
Scanned Files |
Conventional Commits Report
🚀 Conventional commits found. |
🔍 Vulnerabilities of
|
digest | sha256:0a0417f3e4b416ba15272d5ed8283c97950dee4754a80595712c82939ae34148 |
vulnerabilities | |
size | 67 MB |
packages | 198 |
📦 Base Image greenbone/gsad:edge
digest | sha256:342d7f5c47e1b3192a8ee2103e4c2b79b476088005c8df79805319713e4a6a48 |
vulnerabilities |
glibc
|
Affected range | >=2.31-13+deb11u11 |
Fixed version | Not Fixed |
EPSS Score | 0.10% |
EPSS Percentile | 42nd percentile |
Description
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
- glibc (unimportant)
- eglibc (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=24269
Affected range | >=2.31-13+deb11u11 |
Fixed version | Not Fixed |
EPSS Score | 0.35% |
EPSS Percentile | 72nd percentile |
Description
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.
- glibc (unimportant)
Not treated as a security issue by upstream
https://sourceware.org/bugzilla/show_bug.cgi?id=22853
Affected range | >=2.31-13+deb11u11 |
Fixed version | Not Fixed |
EPSS Score | 2.33% |
EPSS Percentile | 89th percentile |
Description
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.
- glibc (unimportant)
Not treated as a security issue by upstream
https://sourceware.org/bugzilla/show_bug.cgi?id=22852
Affected range | >=2.31-13+deb11u11 |
Fixed version | Not Fixed |
EPSS Score | 0.84% |
EPSS Percentile | 82nd percentile |
Description
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.
- glibc (unimportant)
Not treated as a security issue by upstream
https://sourceware.org/bugzilla/show_bug.cgi?id=22851
Affected range | >=2.31-13+deb11u11 |
Fixed version | Not Fixed |
EPSS Score | 0.59% |
EPSS Percentile | 78th percentile |
Description
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.
- glibc (unimportant)
Not treated as a security issue by upstream
https://sourceware.org/bugzilla/show_bug.cgi?id=22850
Affected range | >=2.31-13+deb11u11 |
Fixed version | Not Fixed |
EPSS Score | 0.30% |
EPSS Percentile | 69th percentile |
Description
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.
- glibc (unimportant)
- eglibc (unimportant)
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34141
https://lists.gnu.org/archive/html/bug-gnulib/2019-01/msg00108.html
No treated as vulnerability: https://sourceware.org/glibc/wiki/Security%20Exceptions
Affected range | >=2.31-13+deb11u11 |
Fixed version | Not Fixed |
EPSS Score | 0.88% |
EPSS Percentile | 82nd percentile |
Description
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.
- glibc (unimportant)
- eglibc (unimportant)
That's standard POSIX behaviour implemented by (e)glibc. Applications using
glob need to impose limits for themselves
systemd 247.3-7+deb11u6
(deb)
pkg:deb/debian/systemd@247.3-7%2Bdeb11u6?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=247.3-7+deb11u5 |
Fixed version | Not Fixed |
EPSS Score | 0.14% |
EPSS Percentile | 50th percentile |
Description
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."
- systemd (unimportant)
Disputed by upstream
/~https://github.com/kastel-security/Journald/blob/main/journald-publication.pdf
Affected range | >=247.3-7+deb11u5 |
Fixed version | Not Fixed |
EPSS Score | 0.11% |
EPSS Percentile | 45th percentile |
Description
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."
- systemd (unimportant)
Disputed by upstream
/~https://github.com/kastel-security/Journald/blob/main/journald-publication.pdf
Affected range | >=247.3-7+deb11u5 |
Fixed version | Not Fixed |
EPSS Score | 0.09% |
EPSS Percentile | 41st percentile |
Description
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."
- systemd (unimportant)
Disputed by upstream
/~https://github.com/kastel-security/Journald/blob/main/journald-publication.pdf
Affected range | >=247.3-7+deb11u5 |
Fixed version | Not Fixed |
EPSS Score | 0.19% |
EPSS Percentile | 57th percentile |
Description
An exploitable denial-of-service vulnerability exists in Systemd 245. A specially crafted DHCP FORCERENEW packet can cause a server running the DHCP client to be vulnerable to a DHCP ACK spoofing attack. An attacker can forge a pair of FORCERENEW and DCHP ACK packets to reconfigure the server.
- systemd 249.4-2 (unimportant)
https://talosintelligence.com/vulnerability_reports/TALOS-2020-1142
Talos Security Advisory for Systemd DHCP (TALOS-2020-1142/CVE-2020-13529) systemd/systemd#16774
https://bugzilla.redhat.com/show_bug.cgi?id=1959397
Fixed by: systemd/systemd@38e980a (v249-rc2)
Generic DHCP protocol issue, negligible security impact
Affected range | >=247.3-7+deb11u5 |
Fixed version | Not Fixed |
EPSS Score | 0.04% |
EPSS Percentile | 5th percentile |
Description
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.
- systemd (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725357)
[wheezy] - systemd (/etc/tmpfiles.d not supported in Wheezy)
https://bugzilla.redhat.com/show_bug.cgi?id=859060
only relevant to systems running systemd along with selinux
pcre3 2:8.39-13
(deb)
pkg:deb/debian/pcre3@2:8.39-13?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=2:8.39-13 |
Fixed version | Not Fixed |
EPSS Score | 0.58% |
EPSS Percentile | 78th percentile |
Description
libpcre in PCRE before 8.43 allows a subject buffer over-read in JIT when UTF is disabled, and \X or \R has more than one fixed quantifier, a related issue to CVE-2019-20454.
- pcre3 (unimportant)
Fixed by: https://vcs.pcre.org/pcre?view=revision&revision=1740 (8.43)
Only an issue when UTF support disabled
Affected range | >=2:8.39-13 |
Fixed version | Not Fixed |
EPSS Score | 0.65% |
EPSS Percentile | 79th percentile |
Description
Stack-based buffer overflow in the pcre32_copy_substring function in pcre_get.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (WRITE of size 268) or possibly have unspecified other impact via a crafted file.
- pcre3 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858679; unimportant)
[jessie] - pcre3 (Minor issue; 32bit character support not enabled)
[wheezy] - pcre3 (Vulnerable code not present)
https://bugs.exim.org/show_bug.cgi?id=2057
https://blogs.gentoo.org/ago/2017/03/20/libpcre-two-stack-based-buffer-overflow-write-in-pcre32_copy_substring-pcre_get-c/
pcre32 support enabled only in pcre3/1:8.35-4
Fixed by: http://vcs.pcre.org/pcre?view=revision&revision=1691 (8.41)
Affected range | >=2:8.39-13 |
Fixed version | Not Fixed |
EPSS Score | 0.65% |
EPSS Percentile | 79th percentile |
Description
Stack-based buffer overflow in the pcre32_copy_substring function in pcre_get.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (WRITE of size 4) or possibly have unspecified other impact via a crafted file.
- pcre3 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858678; unimportant)
[jessie] - pcre3 (Minor issue; 32bit character support not enabled)
[wheezy] - pcre3 (Vulnerable code not present)
https://bugs.exim.org/show_bug.cgi?id=2055
https://blogs.gentoo.org/ago/2017/03/20/libpcre-two-stack-based-buffer-overflow-write-in-pcre32_copy_substring-pcre_get-c/
pcre32 support enabled only in pcre3/1:8.35-4
Fixed by: http://vcs.pcre.org/pcre?view=revision&revision=1691 (8.41)
Affected range | >=2:8.39-13 |
Fixed version | Not Fixed |
EPSS Score | 0.11% |
EPSS Percentile | 46th percentile |
Description
In PCRE 8.41, after compiling, a pcretest load test PoC produces a crash overflow in the function match() in pcre_exec.c because of a self-recursive call. NOTE: third parties dispute the relevance of this report, noting that there are options that can be used to limit the amount of stack that is used
- pcre3 (unimportant)
Affected range | >=2:8.39-13 |
Fixed version | Not Fixed |
EPSS Score | 0.32% |
EPSS Percentile | 70th percentile |
Description
In PCRE 8.41, the OP_KETRMAX feature in the match function in pcre_exec.c allows stack exhaustion (uncontrolled recursion) when processing a crafted regular expression.
- pcre3 (unimportant)
http://openwall.com/lists/oss-security/2017/07/11/3
openldap 2.4.57+dfsg-3+deb11u1
(deb)
pkg:deb/debian/openldap@2.4.57%2Bdfsg-3%2Bdeb11u1?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=2.4.57+dfsg-3+deb11u1 |
Fixed version | Not Fixed |
EPSS Score | 0.16% |
EPSS Percentile | 53rd percentile |
Description
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.
- openldap (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965184)
https://bugs.openldap.org/show_bug.cgi?id=9266
https://bugzilla.redhat.com/show_bug.cgi?id=1740070
RedHat/CentOS applied patch: https://git.centos.org/rpms/openldap/raw/67459960064be9d226d57c5f82aaba0929876813/f/SOURCES/openldap-tlso-dont-check-cn-when-bad-san.patch
OpenLDAP upstream did dispute the issue as beeing valid, as the current libldap
behaviour does conform with RFC4513. RFC6125 does not superseed the rules for
verifying service identity provided in specifications for existing application
protocols published prior to RFC6125, like RFC4513 for LDAP.
Affected range | >=2.4.57+dfsg-3+deb11u1 |
Fixed version | Not Fixed |
EPSS Score | 0.49% |
EPSS Percentile | 76th percentile |
Description
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.
- openldap (unimportant)
http://www.openldap.org/its/index.cgi/Incoming?id=8759
nops slapd-module not built
Affected range | >=2.4.57+dfsg-3+deb11u1 |
Fixed version | Not Fixed |
EPSS Score | 0.05% |
EPSS Percentile | 23rd percentile |
Description
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.
- openldap (unimportant)
http://www.openldap.org/its/index.cgi?findid=8703
Negligible security impact, but filed #877512
Affected range | >=2.4.57+dfsg-3+deb11u1 |
Fixed version | Not Fixed |
EPSS Score | 0.30% |
EPSS Percentile | 69th percentile |
Description
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.
- openldap (unimportant)
Debian builds with GNUTLS, not NSS
shadow 1:4.8.1-1
(deb)
pkg:deb/debian/shadow@1:4.8.1-1?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=1:4.8.1-1 |
Fixed version | Not Fixed |
EPSS Score | 0.04% |
EPSS Percentile | 18th percentile |
Description
shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.
Affected range | >=1:4.8.1-1 |
Fixed version | Not Fixed |
EPSS Score | 0.06% |
EPSS Percentile | 27th percentile |
Description
shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees
- shadow 1:4.12.3+dfsg1-1 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778950)
Has CVE-2013-4235 been fixed ? shadow-maint/shadow#317
Address CVE-2013-4235 shadow-maint/shadow#545
Fixed by: shadow-maint/shadow@e9ae247 (4.12.2)
Fixed by: shadow-maint/shadow@f6f8bcd (4.12.2)
Fixed by: shadow-maint/shadow@dab764d (4.12.2)
Fixed by: shadow-maint/shadow@1d28127 (4.12.2)
Fixed by: shadow-maint/shadow@f606314 (4.12.2)
Fixed by: shadow-maint/shadow@6cbec2d (4.12.2)
Fixed by: shadow-maint/shadow@faeab50 (4.12.2)
Regression fix: shadow-maint/shadow@f3bdb28 (4.13)
Regression fix: shadow-maint/shadow@10cd68e (4.13)
Regression fix: shadow-maint/shadow@cde221b (4.13)
Affected range | >=1:4.8.1-1 |
Fixed version | Not Fixed |
EPSS Score | 0.17% |
EPSS Percentile | 55th percentile |
Description
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.
- shadow (unimportant)
See #290803, on Debian LOG_UNKFAIL_ENAB in login.defs is set to no so
unknown usernames are not recorded on login failures
krb5 1.18.3-6+deb11u5
(deb)
pkg:deb/debian/krb5@1.18.3-6%2Bdeb11u5?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=1.18.3-6+deb11u5 |
Fixed version | Not Fixed |
EPSS Score | 0.04% |
EPSS Percentile | 11th percentile |
Description
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.
- krb5 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064965; unimportant)
NOTE: /~https://github.com/LuMingYinDetect/krb5_defects/blob/main/krb5_detect_2.md
NOTE: Fixed by: krb5/krb5@c5f9c81
NOTE: Codepath cannot be triggered via API calls, negligible security impact
NOTE: https://mailman.mit.edu/pipermail/kerberos/2024-March/023095.html
Affected range | >=1.18.3-6+deb11u5 |
Fixed version | Not Fixed |
EPSS Score | 0.04% |
EPSS Percentile | 11th percentile |
Description
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.
- krb5 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064965; unimportant)
NOTE: /~https://github.com/LuMingYinDetect/krb5_defects/blob/main/krb5_detect_1.md
NOTE: Fixed by: krb5/krb5@c5f9c81
NOTE: Unused codepath, negligible security impact
NOTE: https://mailman.mit.edu/pipermail/kerberos/2024-March/023095.html
Affected range | >=1.18.3-6+deb11u5 |
Fixed version | Not Fixed |
EPSS Score | 0.09% |
EPSS Percentile | 39th percentile |
Description
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.
- krb5 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889684)
/~https://github.com/poojamnit/Kerberos-V5-1.16-Vulnerabilities/tree/master/Integer%20Overflow
non-issue, codepath is only run on trusted input, potential integer
overflow is non-issue
sqlite3 3.34.1-3+deb11u1
(deb)
pkg:deb/debian/sqlite3@3.34.1-3%2Bdeb11u1?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=3.34.1-3 |
Fixed version | Not Fixed |
Description
sqlite3 v3.40.1 was discovered to contain a segmentation violation at /sqlite3_aflpp/shell.c.
REJECTED
Affected range | >=3.34.1-3 |
Fixed version | Not Fixed |
EPSS Score | 0.33% |
EPSS Percentile | 71st percentile |
Description
SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API.
- sqlite3 3.39.2-1 (unimportant)
- sqlite (unimportant)
https://sqlite.org/forum/forumpost/3607259d3c
Debian sqlite3 packages not compiled with -DSQLITE_ENABLE_STAT4
https://blog.trailofbits.com/2022/10/25/sqlite-vulnerability-july-2022-library-api/
Affected range | >=3.34.1-3 |
Fixed version | Not Fixed |
EPSS Score | 0.28% |
EPSS Percentile | 68th percentile |
Description
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.
- sqlite3 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005974)
- sqlite (unimportant)
/~https://github.com/guyinatuxedo/sqlite3_record_leaking
https://bugzilla.redhat.com/show_bug.cgi?id=2054793
https://sqlite.org/forum/forumpost/056d557c2f8c452ed5bb9c215414c802b215ce437be82be047726e521342161e
Negligible security impact
libpcap 1.10.0-2
(deb)
pkg:deb/debian/libpcap@1.10.0-2?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=1.10.0-2 |
Fixed version | Not Fixed |
EPSS Score | 0.04% |
EPSS Percentile | 11th percentile |
Description
Remote packet capture support is disabled by default in libpcap. When a user builds libpcap with remote packet capture support enabled, one of the functions that become available is pcap_findalldevs_ex(). One of the function arguments can be a filesystem path, which normally means a directory with input data files. When the specified path cannot be used as a directory, the function receives NULL from opendir(), but does not check the return value and passes the NULL value to readdir(), which causes a NULL pointer derefence.
- libpcap 1.10.5-1 (unimportant)
NOTE: the-tcpdump-group/libpcap@0f8a103 (master)
NOTE: the-tcpdump-group/libpcap@8a633ee (libpcap-1.10.5)
NOTE: Builts in Debian do not enable remote package capture (--enable-remote)
Affected range | >=1.10.0-2 |
Fixed version | Not Fixed |
EPSS Score | 0.04% |
EPSS Percentile | 11th percentile |
Description
In affected libpcap versions during the setup of a remote packet capture the internal function sock_initaddress() calls getaddrinfo() and possibly freeaddrinfo(), but does not clearly indicate to the caller function whether freeaddrinfo() still remains to be called after the function returns. This makes it possible in some scenarios that both the function and its caller call freeaddrinfo() for the same allocated memory block. A similar problem was reported in Apple libpcap, to which Apple assigned CVE-2023-40400.
- libpcap 1.10.5-1 (unimportant)
the-tcpdump-group/libpcap@262e4f3 (master)
the-tcpdump-group/libpcap@2aa69b0 (libpcap-1.10.5)
Builts in Debian do not enable remote package capture (--enable-remote)
perl 5.32.1-4+deb11u4
(deb)
pkg:deb/debian/perl@5.32.1-4%2Bdeb11u4?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=5.32.1-4+deb11u3 |
Fixed version | Not Fixed |
EPSS Score | 0.29% |
EPSS Percentile | 69th percentile |
Description
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.
- libhttp-tiny-perl 0.088-1 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962407; unimportant)
[experimental] - perl 5.38.0~rc2-1- perl 5.38.2-2 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954089)
https://www.openwall.com/lists/oss-security/2023/04/18/14
verify_SSL being true by default (redux) chansen/p5-http-tiny#134
https://blog.hackeriet.no/perl-http-tiny-insecure-tls-default-affects-cpan-modules/
https://hackeriet.github.io/cpan-http-tiny-overview/
Applications need to explicitly opt in to enable verification.
Affected range | >=5.32.1-4+deb11u3 |
Fixed version | Not Fixed |
EPSS Score | 0.16% |
EPSS Percentile | 53rd percentile |
Description
_is_safe in the File::Temp module for Perl does not properly handle symlinks.
gcc-9 9.3.0-22
(deb)
pkg:deb/debian/gcc-9@9.3.0-22?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=9.3.0-22 |
Fixed version | Not Fixed |
EPSS Score | 0.06% |
EPSS Percentile | 30th percentile |
Description
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.
- gcc-13 13.2.0-4 (unimportant)
- gcc-12 12.3.0-9 (unimportant)
- gcc-11 11.4.0-4 (unimportant)
- gcc-10 10.5.0-3 (unimportant)
- gcc-9 9.5.0-6 (unimportant)
- gcc-8 (unimportant)
- gcc-7 (unimportant)
GHSA-x7ch-h5rf-w2mf
Not considered a security issue by GCC upstream
https://developer.arm.com/Arm%20Security%20Center/GCC%20Stack%20Protector%20Vulnerability%20AArch64
gnutls28 3.7.1-5+deb11u6
(deb)
pkg:deb/debian/gnutls28@3.7.1-5%2Bdeb11u6?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=3.7.1-5+deb11u5 |
Fixed version | Not Fixed |
EPSS Score | 1.43% |
EPSS Percentile | 86th percentile |
Description
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.
- sun-java6 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645881)
[lenny] - sun-java6 (Non-free not supported)
[squeeze] - sun-java6 (Non-free not supported)- openjdk-6 6b23~pre11-1
- openjdk-7 7~b147-2.0-1
- iceweasel (Vulnerable code not present)
http://blog.mozilla.com/security/2011/09/27/attack-against-tls-protected-communications/- chromium-browser 15.0.874.106~r107270-1
[squeeze] - chromium-browser- lighttpd 1.4.30-1
strictly speaking this is no lighttpd issue, but lighttpd adds a workaround- curl 7.24.0-1
http://curl.haxx.se/docs/adv_20120124B.html- python2.6 2.6.8-0.1 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684511)
[squeeze] - python2.6 (Minor issue)- python2.7 2.7.3~rc1-1
- python3.1 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678998)
[squeeze] - python3.1 (Minor issue)- python3.2 3.2.3~rc1-1
http://bugs.python.org/issue13885
python3.1 is fixed starting 3.1.5- cyassl
- gnutls26 (unimportant)
- gnutls28 (unimportant)
No mitigation for gnutls, it is recommended to use TLS 1.1 or 1.2 which is supported since 2.0.0- haskell-tls (unimportant)
No mitigation for haskell-tls, it is recommended to use TLS 1.1, which is supported since 0.2- matrixssl (low)
[squeeze] - matrixssl (Minor issue)
[wheezy] - matrixssl (Minor issue)
matrixssl fix this upstream in 3.2.2- bouncycastle 1.49+dfsg-1
[squeeze] - bouncycastle (Minor issue)
[wheezy] - bouncycastle (Minor issue)
No mitigation for bouncycastle, it is recommended to use TLS 1.1, which is supported since 1.4.9- nss 3.13.1.with.ckbi.1.88-1
https://bugzilla.mozilla.org/show_bug.cgi?id=665814
https://hg.mozilla.org/projects/nss/rev/7f7446fcc7ab- polarssl (unimportant)
No mitigation for polarssl, it is recommended to use TLS 1.1, which is supported in all releases- tlslite
[wheezy] - tlslite (Minor issue)- pound 2.6-2
Pound 2.6-2 added an anti_beast.patch to mitigate BEAST attacks.- erlang 1:15.b-dfsg-1
[squeeze] - erlang (Minor issue)- asterisk 1:13.7.2
dfsg-1dfsg-2+deb8u1
[jessie] - asterisk 1:11.13.1
[wheezy] - asterisk (Minor issue)
[squeeze] - asterisk (Not supported in Squeeze LTS)
http://downloads.digium.com/pub/security/AST-2016-001.html
https://issues.asterisk.org/jira/browse/ASTERISK-24972
patch for 11 (jessie): https://code.asterisk.org/code/changelog/asterisk?cs=f233bcd81d85626ce5bdd27b05bc95d131faf3e4
all versions vulnerable, backport required for wheezy
tar 1.34+dfsg-1+deb11u1
(deb)
pkg:deb/debian/tar@1.34%2Bdfsg-1%2Bdeb11u1?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=1.34+dfsg-1+deb11u1 |
Fixed version | Not Fixed |
EPSS Score | 0.69% |
EPSS Percentile | 80th percentile |
Description
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.
This is intended behaviour, after all tar is an archiving tool and you
need to give -p as a command line flag
- tar (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=328228; unimportant)
gcc-10 10.2.1-6
(deb)
pkg:deb/debian/gcc-10@10.2.1-6?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=10.2.1-6 |
Fixed version | Not Fixed |
EPSS Score | 0.06% |
EPSS Percentile | 30th percentile |
Description
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.
- gcc-13 13.2.0-4 (unimportant)
- gcc-12 12.3.0-9 (unimportant)
- gcc-11 11.4.0-4 (unimportant)
- gcc-10 10.5.0-3 (unimportant)
- gcc-9 9.5.0-6 (unimportant)
- gcc-8 (unimportant)
- gcc-7 (unimportant)
GHSA-x7ch-h5rf-w2mf
Not considered a security issue by GCC upstream
https://developer.arm.com/Arm%20Security%20Center/GCC%20Stack%20Protector%20Vulnerability%20AArch64
hiredis 0.14.1-1
(deb)
pkg:deb/debian/hiredis@0.14.1-1?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=0.14.1-1 |
Fixed version | Not Fixed |
EPSS Score | 0.29% |
EPSS Percentile | 69th percentile |
Description
Hiredis is a minimalistic C client library for the Redis database. In affected versions Hiredis is vulnurable to integer overflow if provided maliciously crafted or corrupted
RESP
mult-bulk
protocol data. When parsingmulti-bulk
(array-like) replies, hiredis fails to check ifcount * sizeof(redisReply*)
can be represented inSIZE_MAX
. If it can not, and thecalloc()
call doesn't itself make this check, it would result in a short allocation and subsequent buffer overflow. Users of hiredis who are unable to update may set the maxelements context option to a value small enough that no overflow is possible.
- hiredis 0.14.1-2 (unimportant)
GHSA-hfm9-39pp-55p2
redis/hiredis@76a7b10 (v1.0.1)
Only a hardening for insecure libcs:
redis/hiredis@76a7b10#commitcomment-57544143
libxml2 2.9.10+dfsg-6.7+deb11u5
(deb)
pkg:deb/debian/libxml2@2.9.10%2Bdfsg-6.7%2Bdeb11u5?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=2.9.10+dfsg-6.7+deb11u4 |
Fixed version | Not Fixed |
EPSS Score | 0.04% |
EPSS Percentile | 12th percentile |
Description
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.
- libxml2 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071162)
NOTE: https://gitlab.gnome.org/GNOME/libxml2/-/issues/720
NOTE: Fixed by: https://gitlab.gnome.org/GNOME/libxml2/-/commit/8ddc7f13337c9fe7c6b6e616f404b0fffb8a5145 (v2.11.8)
NOTE: Fixed by: https://gitlab.gnome.org/GNOME/libxml2/-/commit/2876ac5392a4e891b81e40e592c3ac6cb46016ce (v2.12.7)
NOTE: Crash in CLI tool, no security impact
openssl 1.1.1w-0+deb11u2
(deb)
pkg:deb/debian/openssl@1.1.1w-0%2Bdeb11u2?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=1.1.1w-0+deb11u1 |
Fixed version | Not Fixed |
EPSS Score | 0.07% |
EPSS Percentile | 31st percentile |
Description
OpenSSL 0.9.8i on the Gaisler Research LEON3 SoC on the Xilinx Virtex-II Pro FPGA uses a Fixed Width Exponentiation (FWE) algorithm for certain signature calculations, and does not verify the signature before providing it to a caller, which makes it easier for physically proximate attackers to determine the private key via a modified supply voltage for the microprocessor, related to a "fault-based attack."
http://www.eecs.umich.edu/~valeria/research/publications/DATE10RSA.pdf
openssl/openssl#24540
Fault injection based attacks are not within OpenSSLs threat model according
to the security policy: https://www.openssl.org/policies/general/security-policy.html
libgcrypt20 1.8.7-6
(deb)
pkg:deb/debian/libgcrypt20@1.8.7-6?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=1.8.7-6 |
Fixed version | Not Fixed |
EPSS Score | 0.33% |
EPSS Percentile | 71st percentile |
Description
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.
- libgcrypt20 (unimportant)
- libgcrypt11 (unimportant)
- gnupg1 (unimportant)
- gnupg (unimportant)
/~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
GnuPG uses ElGamal in hybrid mode only.
This is not a vulnerability in libgcrypt, but in an application using
it in an insecure manner, see also
https://lists.gnupg.org/pipermail/gcrypt-devel/2018-February/004401.html
pcre2 10.36-2+deb11u1
(deb)
pkg:deb/debian/pcre2@10.36-2%2Bdeb11u1?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=10.36-2+deb11u1 |
Fixed version | Not Fixed |
EPSS Score | 0.07% |
EPSS Percentile | 34th percentile |
Description
Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input.
- pcre2 10.42-1 (unimportant)
[Bug report] Endless looping in pcre2test (v10.41, commit id:3a1ad4 ) PCRE2Project/pcre2#141
PCRE2Project/pcre2@94e1c00
Infinite loop in CLI tool, no security impact
util-linux 2.36.1-8+deb11u2
(deb)
pkg:deb/debian/util-linux@2.36.1-8%2Bdeb11u2?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=2.36.1-8+deb11u2 |
Fixed version | Not Fixed |
EPSS Score | 0.05% |
EPSS Percentile | 19th percentile |
Description
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.
- util-linux (unimportant)
https://bugzilla.redhat.com/show_bug.cgi?id=2053151
https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w@ws.net.home/T/#u
util-linux/util-linux@faa5a3a
util-linux in Debian does build with readline support but chfn and chsh are provided
by src:shadow and util-linux is configured with --disable-chfn-chsh
coreutils 8.32-4+b1
(deb)
pkg:deb/debian/coreutils@8.32-4%2Bb1?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=8.32-4 |
Fixed version | Not Fixed |
EPSS Score | 0.04% |
EPSS Percentile | 5th percentile |
Description
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.
- coreutils (unimportant)
http://lists.gnu.org/archive/html/coreutils/2017-12/msg00045.html
https://www.openwall.com/lists/oss-security/2018/01/04/3
Documentation patches proposed:
https://lists.gnu.org/archive/html/coreutils/2017-12/msg00072.html
https://lists.gnu.org/archive/html/coreutils/2017-12/msg00073.html
Neutralised by kernel hardening
glib2.0 2.66.8-1+deb11u5
(deb)
pkg:deb/debian/glib2.0@2.66.8-1%2Bdeb11u5?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=2.66.8-1+deb11u4 |
Fixed version | Not Fixed |
EPSS Score | 0.16% |
EPSS Percentile | 53rd percentile |
Description
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.
- glib2.0 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655044)
gnupg2 2.2.27-2+deb11u2
(deb)
pkg:deb/debian/gnupg2@2.2.27-2%2Bdeb11u2?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=2.2.27-2+deb11u2 |
Fixed version | Not Fixed |
EPSS Score | 0.05% |
EPSS Percentile | 19th percentile |
Description
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.
- gnupg2 (unimportant)
https://bugzilla.redhat.com/show_bug.cgi?id=2127010
https://dev.gnupg.org/D556
https://dev.gnupg.org/T5993
https://www.openwall.com/lists/oss-security/2022/07/04/8
GnuPG upstream is not implementing this change.
apt 2.2.4
(deb)
pkg:deb/debian/apt@2.2.4?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=2.2.4 |
Fixed version | Not Fixed |
EPSS Score | 0.31% |
EPSS Percentile | 70th percentile |
Description
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.
- apt (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642480)
Not exploitable in Debian, since no keyring URI is defined
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4281 +/- ##
==========================================
- Coverage 62.73% 62.71% -0.02%
==========================================
Files 1120 1120
Lines 99101 99141 +40
Branches 6654 6661 +7
==========================================
+ Hits 62169 62177 +8
- Misses 36802 36834 +32
Partials 130 130 ☔ View full report in Codecov by Sentry. |
aa7dc0c
to
0c2aff7
Compare
059b2a8
to
e4477f2
Compare
2f9361c
to
2c595be
Compare
What
cve.js
andcpe.js
to new data structure.Why
References
GEA-730
Checklist