| CVE-2022-34903 | gnupg2 | 2.2.19-3ubuntu2.1 | GnuPG through 2.3.6, in unusual situations where an attacker possesses any secret-key information from a victim's keyring and other constraints (e.g., use of GPGME) are met, allows signature forgery via injection into the status line. |
| CVE-2022-1664 | dpkg | 1.19.7ubuntu3 | Dpkg::Source::Archive in dpkg, the Debian package management system, before version 1.21.8, 1.20.10, 1.19.8, 1.18.26 is prone to a directory traversal vulnerability. When extracting untrusted source packages in v2 and v3 source package formats that include a debian.tar, the in-place extraction can lead to directory traversal situations on specially crafted orig.tar and debian.tar tarballs. |
| CVE-2020-35527 | sqlite3 | 3.31.1-4ubuntu0.2 | In SQLite 3.31.1, there is an out of bounds access problem through ALTER TABLE for views that have a nested FROM clause. |
| CVE-2022-35737 | sqlite3 | 3.31.1-4ubuntu0.2 | 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. |
| CVE-2020-35525 | sqlite3 | 3.31.1-4ubuntu0.2 | In SQlite 3.31.1, a potential null pointer derreference was found in the INTERSEC query processing. |
| CVE-2023-0361 | gnutls28 | 3.6.13-2ubuntu1.6 | A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection. |
| CVE-2022-2509 | gnutls28 | 3.6.13-2ubuntu1.6 | A vulnerability found in gnutls. This security flaw happens because of a double free error occurs during verification of pkcs7 signatures in gnutls_pkcs7_verify function. |
| CVE-2020-16156 | perl | 5.30.0-9ubuntu0.2 | CPAN 2.28 allows Signature Verification Bypass. |
| CVE-2022-42898 | krb5 | 1.17-6ubuntu4.1 | PAC parsing in MIT Kerberos 5 (aka krb5) before 1.19.4 and 1.20.x before 1.20.1 has integer overflows that may lead to remote code execution (in KDC, kadmind, or a GSS or Kerberos application server) on 32-bit platforms (which have a resultant heap-based buffer overflow), and cause a denial of service on other platforms. This occurs in krb5_pac_parse in lib/krb5/krb/pac.c. Heimdal before 7.7.1 has "a similar bug." |
| CVE-2021-37750 | krb5 | 1.17-6ubuntu4.1 | The Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.18.5 and 1.19.x before 1.19.3 has a NULL pointer dereference in kdc/do_tgs_req.c via a FAST inner body that lacks a server field. |
| CVE-2021-36222 | krb5 | 1.17-6ubuntu4.1 | ec_verify in kdc/kdc_preauth_ec.c in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.18.4 and 1.19.x before 1.19.2 allows remote attackers to cause a NULL pointer dereference and daemon crash. This occurs because a return value is not properly managed in a certain situation. |
| CVE-2022-4415 | systemd | 245.4-4ubuntu3.15 | A vulnerability was found in systemd. This security flaw can cause a local information leak due to systemd-coredump not respecting the fs.suid_dumpable kernel setting. |
| CVE-2022-3821 | systemd | 245.4-4ubuntu3.15 | An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c. An attacker could supply specific values for time and accuracy that leads to buffer overrun in format_timespan(), leading to a Denial of Service. |
| CVE-2022-48303 | tar | 1.30+dfsg-7ubuntu0.20.04.2 | 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. |
| CVE-2022-23491 | ca-certificates | 20210119~20.04.2 | Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion. |
| CVE-2022-1292 | openssl | 1.1.1f-1ubuntu2.12 | The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd). |
| CVE-2022-2068 | openssl | 1.1.1f-1ubuntu2.12 | In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze). |
| CVE-2022-4304 | openssl | 1.1.1f-1ubuntu2.12 | A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection. |
| CVE-2022-4450 | openssl | 1.1.1f-1ubuntu2.12 | The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue. |
| CVE-2023-0215 | openssl | 1.1.1f-1ubuntu2.12 | The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL cms and smime command line applications are similarly affected. |
| CVE-2022-2097 | openssl | 1.1.1f-1ubuntu2.12 | AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p). |
| CVE-2022-3116 | heimdal | 7.7.0+dfsg-1ubuntu1 | A flawed logical condition in lib/gssapi/spnego/accept_sec_context.c allows a malicious actor to remotely trigger a NULL pointer dereference using a crafted negTokenInit token. |
| CVE-2022-41916 | heimdal | 7.7.0+dfsg-1ubuntu1 | Heimdal is an implementation of ASN.1/DER, PKIX, and Kerberos. Versions prior to 7.7.1 are vulnerable to a denial of service vulnerability in Heimdal's PKI certificate validation library, affecting the KDC (via PKINIT) and kinit (via PKINIT), as well as any third-party applications using Heimdal's libhx509. Users should upgrade to Heimdal 7.7.1 or 7.8. There are no known workarounds for this issue. |
| CVE-2022-42898 | heimdal | 7.7.0+dfsg-1ubuntu1 | PAC parsing in MIT Kerberos 5 (aka krb5) before 1.19.4 and 1.20.x before 1.20.1 has integer overflows that may lead to remote code execution (in KDC, kadmind, or a GSS or Kerberos application server) on 32-bit platforms (which have a resultant heap-based buffer overflow), and cause a denial of service on other platforms. This occurs in krb5_pac_parse in lib/krb5/krb/pac.c. Heimdal before 7.7.1 has "a similar bug." |
| CVE-2021-44758 | heimdal | 7.7.0+dfsg-1ubuntu1 | Heimdal before 7.7.1 allows attackers to cause a NULL pointer dereference in a SPNEGO acceptor via a preferred_mech_type of GSS_C_NO_OID and a nonzero initial_response value to send_accept. |
| CVE-2022-44640 | heimdal | 7.7.0+dfsg-1ubuntu1 | Heimdal before 7.7.1 allows remote attackers to execute arbitrary code because of an invalid free in the ASN.1 codec used by the Key Distribution Center (KDC). |
| CVE-2022-45142 | heimdal | 7.7.0+dfsg-1ubuntu1 | The fix for CVE-2022-3437 included changing memcmp to be constant time and a workaround for a compiler bug by adding "!= 0" comparisons to the result of memcmp. When these patches were backported to the heimdal-7.7.1 and heimdal-7.8.0 branches (and possibly other branches) a logic inversion sneaked in causing the validation of message integrity codes in gssapi/arcfour to be inverted. |
| CVE-2022-3437 | heimdal | 7.7.0+dfsg-1ubuntu1 | A heap-based buffer overflow vulnerability was found in Samba within the GSSAPI unwrap_des() and unwrap_des3() routines of Heimdal. The DES and Triple-DES decryption routines in the Heimdal GSSAPI library allow a length-limited write buffer overflow on malloc() allocated memory when presented with a maliciously small packet. This flaw allows a remote user to send specially crafted malicious data to the application, possibly resulting in a denial of service (DoS) attack. |
| CVE-2022-0529 | unzip | 6.0-25ubuntu1 | A flaw was found in Unzip. The vulnerability occurs during the conversion of a wide string to a local string that leads to a heap of out-of-bound write. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution. |
| CVE-2022-1271 | xz-utils | 5.2.4-1ubuntu1 | An arbitrary file write vulnerability was found in GNU gzip's zgrep utility. When zgrep is applied on the attacker's chosen file name (for example, a crafted file name), this can overwrite an attacker's content to an arbitrary attacker-selected file. This flaw occurs due to insufficient validation when processing filenames with two or more newlines where selected content and the target file names are embedded in crafted multi-line file names. This flaw allows a remote, low privileged attacker to force zgrep to write arbitrary files on the system. |
| CVE-2022-29155 | openldap | 2.4.49+dfsg-2ubuntu1.8 | In OpenLDAP 2.x before 2.5.12 and 2.6.x before 2.6.2, a SQL injection vulnerability exists in the experimental back-sql backend to slapd, via a SQL statement within an LDAP query. This can occur during an LDAP search operation when the search filter is processed, due to a lack of proper escaping. |
| CVE-2022-1271 | gzip | 1.10-0ubuntu4 | An arbitrary file write vulnerability was found in GNU gzip's zgrep utility. When zgrep is applied on the attacker's chosen file name (for example, a crafted file name), this can overwrite an attacker's content to an arbitrary attacker-selected file. This flaw occurs due to insufficient validation when processing filenames with two or more newlines where selected content and the target file names are embedded in crafted multi-line file names. This flaw allows a remote, low privileged attacker to force zgrep to write arbitrary files on the system. |
| CVE-2022-1304 | e2fsprogs | 1.45.5-2ubuntu1 | An out-of-bounds read/write vulnerability was found in e2fsprogs 1.46.5. This issue leads to a segmentation fault and possibly arbitrary code execution via a specially crafted filesystem. |
| CVE-2022-32221 | curl | 7.68.0-1ubuntu2.7 | When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was used to issue a `PUT` request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequent `POST` request. The problem exists in the logic for a reused handle when it is changed from a PUT to a POST. |
| CVE-2022-27782 | curl | 7.68.0-1ubuntu2.7 | libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, several TLS andSSH settings were left out from the configuration match checks, making themmatch too easily. |
| CVE-2022-27774 | curl | 7.68.0-1ubuntu2.7 | An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacker to extract credentials when follows HTTP(S) redirects is used with authentication could leak credentials to other services that exist on different protocols or port numbers. |
| CVE-2022-32206 | curl | 7.68.0-1ubuntu2.7 | curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to insert a virtually unlimited number of compression steps.The use of such a decompression chain could result in a "malloc bomb", makingcurl end up spending enormous amounts of allocated heap memory, or trying toand returning out of memory errors. |
| CVE-2022-43552 | curl | 7.68.0-1ubuntu2.7 | A use after free vulnerability exists in curl <7.87.0. Curl can be asked to *tunnel* virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl would use a heap-allocated struct after it had been freed, in its transfer shutdown code path. |
| CVE-2022-22576 | curl | 7.68.0-1ubuntu2.7 | An improper authentication vulnerability exists in curl 7.33.0 to and including 7.82.0 which might allow reuse OAUTH2-authenticated connections without properly making sure that the connection was authenticated with the same credentials as set for this transfer. This affects SASL-enabled protocols: SMPTP(S), IMAP(S), POP3(S) and LDAP(S) (openldap only). |
| CVE-2023-23916 | curl | 7.68.0-1ubuntu2.7 | An allocation of resources without limits or throttling vulnerability exists in curl |
| CVE-2022-32208 | curl | 7.68.0-1ubuntu2.7 | When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client. |
| CVE-2023-27535 | curl | 7.68.0-1ubuntu2.7 | FTP too eager connection reuse |
| CVE-2022-37434 | zlib | 1:1.2.11.dfsg-2ubuntu1.2 | zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference). |
| CVE-2018-25032 | zlib | 1:1.2.11.dfsg-2ubuntu1.2 | zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches. |
| CVE-2022-2344 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0045. |
| CVE-2022-1619 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in function cmdline_erase_chars in GitHub repository vim/vim prior to 8.2.4899. This vulnerabilities are capable of crashing software, modify memory, and possible remote execution |
| CVE-2022-1616 | vim | 2:8.1.2269-1ubuntu5.7 | Use after free in append_command in GitHub repository vim/vim prior to 8.2.4895. This vulnerability is capable of crashing software, Bypass Protection Mechanism, Modify Memory, and possible remote execution |
| CVE-2022-0319 | vim | 2:8.1.2269-1ubuntu5.7 | Out-of-bounds Read in vim/vim prior to 8.2. |
| CVE-2022-2980 | vim | 2:8.1.2269-1ubuntu5.7 | NULL Pointer Dereference in GitHub repository vim/vim prior to 9.0.0259. |
| CVE-2022-2923 | vim | 2:8.1.2269-1ubuntu5.7 | NULL Pointer Dereference in GitHub repository vim/vim prior to 9.0.0240. |
| CVE-2022-2343 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0044. |
| CVE-2022-1154 | vim | 2:8.1.2269-1ubuntu5.7 | Use after free in utf_ptr2char in GitHub repository vim/vim prior to 8.2.4646. |
| CVE-2022-1927 | vim | 2:8.1.2269-1ubuntu5.7 | Buffer Over-read in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-1851 | vim | 2:8.1.2269-1ubuntu5.7 | Out-of-bounds Read in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0629 | vim | 2:8.1.2269-1ubuntu5.7 | Stack-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-1720 | vim | 2:8.1.2269-1ubuntu5.7 | Buffer Over-read in function grab_file_name in GitHub repository vim/vim prior to 8.2.4956. This vulnerability is capable of crashing the software, memory modification, and possible remote execution. |
| CVE-2022-1674 | vim | 2:8.1.2269-1ubuntu5.7 | NULL Pointer Dereference in function vim_regexec_string at regexp.c:2733 in GitHub repository vim/vim prior to 8.2.4938. NULL Pointer Dereference in function vim_regexec_string at regexp.c:2733 allows attackers to cause a denial of service (application crash) via a crafted input. |
| CVE-2022-1968 | vim | 2:8.1.2269-1ubuntu5.7 | Use After Free in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0554 | vim | 2:8.1.2269-1ubuntu5.7 | Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-1621 | vim | 2:8.1.2269-1ubuntu5.7 | Heap buffer overflow in vim_strncpy find_word in GitHub repository vim/vim prior to 8.2.4919. This vulnerability is capable of crashing software, Bypass Protection Mechanism, Modify Memory, and possible remote execution |
| CVE-2022-2175 | vim | 2:8.1.2269-1ubuntu5.7 | Buffer Over-read in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-1629 | vim | 2:8.1.2269-1ubuntu5.7 | Buffer Over-read in function find_next_quote in GitHub repository vim/vim prior to 8.2.4925. This vulnerabilities are capable of crashing software, Modify Memory, and possible remote execution |
| CVE-2021-4166 | vim | 2:8.1.2269-1ubuntu5.7 | vim is vulnerable to Out-of-bounds Read |
| CVE-2022-2946 | vim | 2:8.1.2269-1ubuntu5.7 | Use After Free in GitHub repository vim/vim prior to 9.0.0246. |
| CVE-2022-0359 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-2183 | vim | 2:8.1.2269-1ubuntu5.7 | Out-of-bounds Read in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-1420 | vim | 2:8.1.2269-1ubuntu5.7 | Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4774. |
| CVE-2022-0368 | vim | 2:8.1.2269-1ubuntu5.7 | Out-of-bounds Read in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0261 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0318 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in vim/vim prior to 8.2. |
| CVE-2022-2571 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0101. |
| CVE-2022-0361 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0417 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow GitHub repository vim/vim prior to 8.2. |
| CVE-2022-2304 | vim | 2:8.1.2269-1ubuntu5.7 | Stack-based Buffer Overflow in GitHub repository vim/vim prior to 9.0. |
| CVE-2021-4192 | vim | 2:8.1.2269-1ubuntu5.7 | vim is vulnerable to Use After Free |
| CVE-2022-0714 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4436. |
| CVE-2022-0413 | vim | 2:8.1.2269-1ubuntu5.7 | Use After Free in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0392 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in GitHub repository vim prior to 8.2. |
| CVE-2022-0685 | vim | 2:8.1.2269-1ubuntu5.7 | Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4418. |
| CVE-2022-0213 | vim | 2:8.1.2269-1ubuntu5.7 | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2022-2345 | vim | 2:8.1.2269-1ubuntu5.7 | Use After Free in GitHub repository vim/vim prior to 9.0.0046. |
| CVE-2022-0408 | vim | 2:8.1.2269-1ubuntu5.7 | Stack-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0943 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow occurs in vim in GitHub repository vim/vim prior to 8.2.4563. |
| CVE-2022-0351 | vim | 2:8.1.2269-1ubuntu5.7 | Access of Memory Location Before Start of Buffer in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-1942 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0572 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-1620 | vim | 2:8.1.2269-1ubuntu5.7 | NULL Pointer Dereference in function vim_regexec_string at regexp.c:2729 in GitHub repository vim/vim prior to 8.2.4901. NULL Pointer Dereference in function vim_regexec_string at regexp.c:2729 allows attackers to cause a denial of service (application crash) via a crafted input. |
| CVE-2023-0049 | vim | 2:8.1.2269-1ubuntu5.7 | Out-of-bounds Read in GitHub repository vim/vim prior to 9.0.1143. |
| CVE-2023-0433 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.1225. |
| CVE-2023-1170 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.1376. |
| CVE-2022-47024 | vim | 2:8.1.2269-1ubuntu5.7 | A null pointer dereference issue was discovered in function gui_x11_create_blank_mouse in gui_x11.c in vim 8.1.2269 thru 9.0.0339 allows attackers to cause denial of service or other unspecified impacts. |
| CVE-2023-0288 | vim | 2:8.1.2269-1ubuntu5.7 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.1189. |
| CVE-2023-1264 | vim | 2:8.1.2269-1ubuntu5.7 | NULL Pointer Dereference in GitHub repository vim/vim prior to 9.0.1392. |
| CVE-2023-1175 | vim | 2:8.1.2269-1ubuntu5.7 | Incorrect Calculation of Buffer Size in GitHub repository vim/vim prior to 9.0.1378. |
| CVE-2023-0054 | vim | 2:8.1.2269-1ubuntu5.7 | Out-of-bounds Write in GitHub repository vim/vim prior to 9.0.1145. |