6.7.0 Yellowbrick Release Notes
Release Date: 10/25/2023
- AWS Upgrades from Version 6.6.x
- Azure Upgrades from Version 6.6.x
- Upgrades from Version 5.x (Not Supported)
- Changes in Behavior in This Version
- Azure has new limits on node group maximums
- Default Time Zone for Data Warehouse Instances
- Behavior of the CHAR Data Type
- Default Behavior of WLM Restart Rules
- Changes in Compatibility in This Version
- Client tools tzdata compatibility
- ybtools Compatibility
- BAR2 and Replication Compatibility
- Known Issues in This Version
- What's New in This Version
- Java version update to Java 11, bug fixes
- Offline Installer
- Standard or Scaled Shared Services
- Proxy Support for Azure Deployments
- ybtools Clients on Ubuntu
- Issues Fixed in This Version
- CVE Fixes in This Version
Yellowbrick Data Warehouse Version 6.7.0 is supported for AWS and Microsoft Azure cloud deployments. This version of Yellowbrick Data Warehouse is installed on Cloud Data Warehouse Manager (CDWM) Version 3.67.
Cloud Provider | CDWM Version | Yellowbrick Data Warehouse Version | Kubernetes Version |
---|---|---|---|
AWS | 3.67.5-1014.1095721a | 6.7.0-6125.45cd1f43 | EKS 1.24 |
Azure | 3.67.5-1014.1095721a | 6.7.0-6125.45cd1f43 | AKS 1.25 |
Upgrade Requirements
Read the following information before beginning an upgrade to Version 6.7.0.
- Contact Customer Support to review the process and schedule the upgrade.
- Only upgrades from Version 6.6.x to 6.7.0 are supported. These upgrades apply to both CDWM and data warehouse instances.
- YBD Instances and cluster must be running and not suspended before being upgraded.
- Existing installations using the standard installation method can only be upgraded using the standard method. Similarly, installations using the offline method must be upgraded using the same offline method. Cross-method upgrades are not supported.
Note: Before attempting to upgrade data warehouse instances, make sure they are running. You cannot upgrade suspended instances.
AWS Upgrades from Version 6.6.x
Version 6.7.0 requires EKS 1.24. Please use the EKS migration tool to upgrade to version 1.24 before upgrading to Version 6.7.0.
Before beginning the CDWM upgrade, suspend all instances managed by the CDWM.
Push the CDWM and YBD images to the AWS ECR and check that the required files are in the S3 bucket.
In AWS CloudFormation > Stacks, search for your root stack for your env; click update and then
Select
Replace current template
and update the Amazon S3 URL to point to the location of the yb-cdw.template.yaml file for the 3.67.5-1014.1095721a build.Update and verify information on stack details page.
In the
Yellowbrick software
section, the URL for the chart repository and CloudFormation S3 key prefix must be updated.On the final review page, confirm that the only changes/overrides will be to the CFS3KeyPrefix and ChartRepository values. All other key values remain the same.
Submit to start the deployment process and once it completes verify that the CDWM is reporting the correct version of 3.67.5-1014.1095721a.
Once the upgrade to 3.67.x is completed; verify that the YBD instances were all resumed and each upgraded to 6.7.0-6125.45cd1f43.
Azure Upgrades from Version 6.6.x
You have to upgrade from 6.6.x to 6.7.0, upgrade from prior versions is not allowed.
You can upgrade directly from 6.6.x to Version 6.7.0. Note that Version 6.7.0 requires AKS version 1.25, but this version is supplied as part of the Yellowbrick upgrade.
For each Yellowbrick upgrade:
- Before beginning the CDWM upgrade, suspend all instances managed by the CDWM.
- Promote the CDWM and YBD images to the ACR.
- Upgrade CDWM in Yellowbrick Manager.
- Upgrade your data warehouse instances in Yellowbrick Manager. Before upgrading data warehouse instances, make sure they are running. You cannot upgrade suspended instances.
- Once the upgrade process completes, check that the CDWM is reporting the correct version of 3.67.5-1014.1095721a and YBD version 6.7.0-6125.45cd1f43.
Upgrades from Version 5.x (Not Supported)
You cannot upgrade from Version 5.x to Version 6. However, you can replicate databases from some older releases to Version 6; see BAR2 and Replication Compatibility.
Changes in Behavior in This Version
- 6.7.0
Azure has new limits on node group maximums
This change from Azure will reduce the maximum number of nodes as follows
Type Maximum inst32 10 inst48 10 compiler 10 bulk 50 large worker 125 small worker 125 controller 10(default) system 10(default) - 6.3.0
Default Time Zone for Data Warehouse Instances
In Version 6.3.0, the timezone and log_timezone configuration settings default to UTC for all new data warehouse instances.
- 6.3.0
Behavior of the CHAR Data Type
The CHAR data type implementation has changed in Version 6.x. The pg_char_compatibility_mode parameter is now set to FULL and cannot be set to any other value. See Upcoming Behavioral Changes to the CHAR Data Type.
- 6.3.0
Default Behavior of WLM Restart Rules
By default, a subset of recoverable error codes triggers an attempted restart, and an attempted restart occurs only once per query. For details, see Restarting Queries.
Changes in Compatibility in This Version
- 6.7.0
Client tools tzdata compatibility
When executing ybload and load table SQL, the outcome of loading a timestamp with timezone data to a timestamp column may vary based on the tzdata version. Differences between the JRE’s tzdata version and the Yellowbrick database’s tzdata version can lead to inconsistencies between timestamp directly inserted into the database and those loaded using ybload or load table SQL.
For example, in the case of JRE with tzdata version 2022b, Chile's Daylight Saving Time (DST) transition is delayed by a week in September 2022. As a result, a timestamp such as 04-09-2022 12:00:00 Chile/Continental might be directly inserted into the database as 2022-04-09 15:00:00+00 while being loaded as 2022-04-09 16:00:00+00 due to differences in timezone conversions.
It is recommended to check tzdata version used JRE in the environment, using the tzupdater tool provided by Oracle.
- 6.7.0
ybtools Compatibility
Yellowbrick recommends that you always upgrade ybtools to match the Yellowbrick server version you are running (for example, upgrade to ybtools Version 6.7 before connecting to a Version 6.7 data warehouse). In most cases, using an older version of ybtools, such as 6.6, to connect to a Version 6.7 Data Warehouse will work but is not recommended.
Using Version 6.7 of ybtools with an older server version (such as Version 6.6) may result in error messages for some commands or a mismatch between client and server features.
Important:
On CentOS and Red Hat client platforms, you must first remove any existing 5.x version of ybtools. Then you can proceed with the installation of the Version 6.0 ybtools. You cannot upgrade directly from an earlier 5.x version of ybtools to Version 6.0. - 6.7.0
BAR2 and Replication Compatibility
Important: The source and target systems used for database backup and restore (BAR2) and database replication must be compatible. To support full functionality, the source and target systems should both be running a 6.7 version of Yellowbrick software.
Nonetheless, you can back up and restore a database, or replicate a database, from:
- 5.2.x to 6.5.x
- 5.4.3 or later to 6.5.x
- 6.1.x to 6.5.x
- 6.2.x to 6.5.x
- 6.3.x to 6.5.x
- 6.4.x to 6.5.x
- 6.5.x to 6.6.x
Although you can start replication from a 5.2, 5.4, 6.1, 6.2... or 6.6 source to a 6.7 target, and you can fail over to the 6.7 target, you cannot fail back to the 5.2, 5.4, 6.1, 6.2, 6.3, 6.4 or 6.6 source. In general, you cannot fail back to a Yellowbrick version with a catalog version that is earlier than the current catalog version.
Known Issues in This Version
You may encounter the following issues in Version 6.7.0. Use the workarounds provided in the description and contact Customer Support for additional information.
Issue # | Description |
---|---|
31195 | sys.log_query and historical query data in yellowbrick manager doesn't get updated, data keeps growing |
31293 | Query details requires default cluster to be up and running; inability to use arbitrary cluster from the dropdown. |
31290 | Query history information may not get rendered if there isn't a default cluster running. |
21036 | Load table doesn't support Parquet INT96 data type as a timestamp. |
What's New in This Version
6.7.0 | Java version update to Java 11, bug fixesVersion 6.7.0 provides critical bug fixes. Java 11 is the minimum required java version for Java based client tools. Please refer to Installing JRE. Please see issues fixed in this version. |
6.6.0 | Offline InstallerThis provides an installer that allows customers installing into networks with no public internet access. Commands
Options
Example The result of this would appear as:
Use the http URL for the |
6.3.0 | Standard or Scaled Shared ServicesVersion 6.3 on AWS gives customers the flexibility to install Yellowbrick into a smaller cloud hardware footprint. The Standard Shared Services option creates fewer AWS node groups to run Yellowbrick software. The Scaled Shared Services option is intended for larger data warehouse environments that anticipate more than 100 active users and need more than 5TB of primary data storage. This feature is supported on AWS only; it is not yet supported for Azure deployments. |
6.3.0 | Proxy Support for Azure DeploymentsDuring Yellowbrick deployment on Azure, you can set options to route AKS-required network traffic through HTTP/HTTPS proxies. |
6.3.0 | ybtools Clients on UbuntuVersion 6.3.0 supports ybtools on Ubuntu 16.04 LTS, 18.04 LTS, and 20.04 LTS. |
Issues Fixed in This Version
The following issues are addressed in this version:
Release | Issue # | Description |
---|---|---|
6.7.0 | 33739 | When using the Cloudformation installer to create a VPC network, the option CreateNATGateways must be set to “true” under all network conditions. |
6.7.0 | 33799 | Azure installation on full private/ UDR fails AKS 1.25 creation due to node count limit. Cluster's upper limit node count is 452 which exceeds the limit for Kubenet 400. If Autoscaler is enabled, the max-count from each node pool is counted towards this total. |
6.7.0 | 29590 | Restore may fail if backup media was moved. e.g. from on-premise to s3 or Azure. |
6.7.0 | 33577 | Use of LEFT(varchar f() , N) or RIGHT(varchar f(), N), N < 30 in a CTAS can cause system instability and possible outage. |
6.7.0 | 33374 | Duplicated targetList entries result in errors for distribution |
6.7.0 | 33092 | Issue was caused by the evaluation of a very deep expression comprised of thousands of OR expressions during the storage engine pushdown phase. This caused the corruption of internal data structures thus leading to a crash. Resolution - Cap the number of OR expressions during storage engine pushdown. |
6.7.0 | 32529 | Some types of correlated sub-queries could lead to DB error. In some rare circumstances, it could cause a DB restart. Queries of this type will now error out with - "This form of correlated subquery is not supported" |
6.7.0 | 29487 | Support Neteeza built-in functions LE_DST() (LEvenshtein DiSTance) and DLE_DST() (Damerau-LEvenshtein DiSTance). |
6.7.0 | 31381 | PostgreSQL CVE-2202-2625 |
6.7.0 | 29549 | In some instances, the planner significantly underestimated LEFT joins containing a WHERE clause condition, resulting in poor planning and performance during execution. |
6.7.0 | 28851 | Sometimes on a busy cluster, we could timeout one of the sockets while sending data which caused error KE037 Something went wrong try again later. Fixed by recording and returning the known PG status (00000 or P0003) |
6.7.0 | 16535 | The issue where a TO_CHAR function call with a string casted to a timestamp with time zone as an argument would incorrectly return nothing has been fixed. |
6.6.0 | 22160 | Upgraded server side log4j.jar file to version 2.17.1 |
6.6.0 | 33592 | Upgrade without administrative privileges |
6.5.1 | 32571, 32542 | The Java-based client tools (ybload, ybunload, ybbackup, ybrestore) do not support the --auth-token connection option. Support for this option is added in this release. |
6.5.1 | 29045 | BAR2: Could not create temp directory for caching of metadata for use with ybbar |
6.5.1 | 31970 | Could not handle object store path containing spaces on YbFileInfo/Ybload |
6.5.1 | 32533 | Could not support JSON lookup for not null column |
6.5.1 | 32538 | Unable to connect using --auth-token on all java based client tools (i.e. ybload) |
6.5.1 | 32721 | Accomodate user specified start/end time for diagnostics |
6.4.0 | 31836 | During AWS deployment, the Kubernetes external-dns software attempts to create DNS records in the most-specific variant when multiple Route 53 zones are present in a hierarchy. The documentation now states that you must either specify values for the most-specific variant, or values for a different DNS zone that does not have overlaps. |
6.4.0 | 29683 | In Version 6.4.0, the database row store alert message has been improved to indicate that it is the catalog row store that is becoming full. |
6.3.0 | 32092 | The GETBIT function returned wrong results when used with BIGINT columns. |
6.3.0 | 31831 | The YBCLUSTER environment variable was not supported for ybsql connections. This variable is now supported for all ybtools clients. |
6.3.0 | 31747 | The description of the contents of a backup bundle was improved in the Version 6.3.0 documentation. |
6.3.0 | 31180 | TIMEZONE, TIMEZONE_HOUR, and TIMEZONE_MINUTE date parts were not supported in EXTRACT and DATE_PART functions applied to TIMESTAMPTZ data types. These date parts are now supported. |
6.3.0 | 25808 | The Yellowbrick Manager Query Editor returned incorrect time zone information for casts to TIMESTAMP and TIMESTAMPTZ. |
CVE Fixes in This Version
The following CVEs are addressed in this version:
Release | CVE Fix | Description |
---|---|---|
6.7.0 | CVE-2015-20107 | In Python (aka CPython) up to 3.10.8, the mailcap module does not add escape characters into commands discovered in the system mailcap file. This may allow attackers to inject shell commands into applications that call mailcap.findmatch with untrusted input (if they lack validation of user-provided filenames or arguments). The fix is also back-ported to 3.7, 3.8, 3.9 |
6.7.0 | CVE-2020-10735 | A flaw was found in python. In algorithms with quadratic time complexity using non-binary bases, when using int("text"), a system could take 50ms to parse an int string with 100,000 digits and 5s for 1,000,000 digits (float, decimal, int.from_bytes(), and int() for binary bases 2, 4, 8, 16, and 32 are not affected). The highest threat from this vulnerability is to system availability. |
6.7.0 | CVE-2020-19185 | Buffer Overflow vulnerability in one_one_mapping function in progs/dump_entry.c:1373 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command. |
6.7.0 | CVE-2020-19186 | Buffer Overflow vulnerability in _nc_find_entry function in tinfo/comp_hash.c:66 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command. |
6.7.0 | CVE-2020-19187 | Buffer Overflow vulnerability in fmt_entry function in progs/dump_entry.c:1100 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command. |
6.7.0 | CVE-2020-19188 | Buffer Overflow vulnerability in fmt_entry function in progs/dump_entry.c:1116 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command. |
6.7.0 | CVE-2020-19189 | Buffer Overflow vulnerability in postprocess_terminfo function in tinfo/parse_entry.c:997 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command. |
6.7.0 | CVE-2020-19190 | Buffer Overflow vulnerability in _nc_find_entry in tinfo/comp_hash.c:70 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command. |
6.7.0 | CVE-2020-27619 | In Python 3 through 3.9.0, the Lib/test/multibytecodec_support.py CJK codec tests call eval() on content retrieved via HTTP. |
6.7.0 | CVE-2020-35448 | An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.35.1. A heap-based buffer over-read can occur in bfd_getl_signed_32 in libbfd.c because sh_entsize is not validated in _bfd_elf_slurp_secondary_reloc_section in elf.c. |
6.7.0 | CVE-2021-20197 | There is an open race window when writing output in the following utilities in GNU binutils version 2.35 and earlier:ar, objcopy, strip, ranlib. When these utilities are run as a privileged user (presumably as part of a script updating binaries across different users), an unprivileged user can trick these utilities into getting ownership of arbitrary files through a symlink. |
6.7.0 | CVE-2021-20284 | A flaw was found in GNU Binutils 2.35.1, where there is a heap-based buffer overflow in _bfd_elf_slurp_secondary_reloc_section in elf.c due to the number of symbols not calculated correctly. The highest threat from this vulnerability is to system availability. |
6.7.0 | CVE-2021-29921 | In Python before 3,9,5, the ipaddress library mishandles leading zero characters in the octets of an IP address string. This (in some situations) allows attackers to bypass access control that is based on IP addresses. |
6.7.0 | CVE-2021-33294 | In elfutils 0.183, an infinite loop was found in the function handle_symtab in readelf.c .Which allows attackers to cause a denial of service (infinite loop) via crafted file. |
6.7.0 | CVE-2021-3426 | There's a flaw in Python 3's pydoc. A local or adjacent attacker who discovers or is able to convince another local or adjacent user to start a pydoc server could access the server and use it to disclose sensitive information belonging to the other user that they would not normally be able to access. The highest risk of this flaw is to data confidentiality. This flaw affects Python versions before 3.8.9, Python versions before 3.9.3 and Python versions before 3.10.0a7. |
6.7.0 | CVE-2021-3487 | There's a flaw in the BFD library of binutils in versions before 2.36. An attacker who supplies a crafted file to an application linked with BFD, and using the DWARF functionality, could cause an impact to system availability by way of excessive memory consumption. |
6.7.0 | CVE-2021-3530 | A flaw was discovered in GNU libiberty within demangle_path() in rust-demangle.c, as distributed in GNU Binutils version 2.36. A crafted symbol can cause stack memory to be exhausted leading to a crash. |
6.7.0 | CVE-2021-3549 | An out of bounds flaw was found in GNU binutils objdump utility version 2.36. An attacker could use this flaw and pass a large section to avr_elf32_load_records_from_section() probably resulting in a crash or in some cases memory corruption. The highest threat from this vulnerability is to integrity as well as system availability. |
6.7.0 | CVE-2021-36368 | DISPUTED An issue was discovered in OpenSSH before 8.9. If a client is using public-key authentication with agent forwarding but without -oLogLevel=verbose, and an attacker has silently modified the server to support the None authentication option, then the user cannot determine whether FIDO authentication is going to confirm that the user wishes to connect to that server, or that the user wishes to allow that server to connect to a different server on the user's behalf. NOTE the vendor's position is "this is not an authentication bypass, since nothing is being bypassed. |
6.7.0 | CVE-2021-3733 | There's a flaw in urllib's AbstractBasicAuthHandler class. An attacker who controls a malicious HTTP server that an HTTP client (such as web browser) connects to, could trigger a Regular Expression Denial of Service (ReDOS) during an authentication request with a specially crafted payload that is sent by the server to the client. The greatest threat that this flaw poses is to application availability. |
6.7.0 | CVE-2021-3737 | A flaw was found in python. An improperly handled HTTP response in the HTTP client code of python may allow a remote attacker, who controls the HTTP server, to make the client script enter an infinite loop, consuming CPU time. The highest threat from this vulnerability is to system availability. |
6.7.0 | CVE-2021-3826 | Heap/stack buffer overflow in the dlang_lname function in d-demangle.c in libiberty allows attackers to potentially cause a denial of service (segmentation fault and crash) via a crafted mangled symbol. |
6.7.0 | CVE-2021-41617 | sshd in OpenSSH 6.2 through 8.x before 8.8, when certain non-default configurations are used, allows privilege escalation because supplemental groups are not initialized as expected. Helper programs for AuthorizedKeysCommand and AuthorizedPrincipalsCommand may run with privileges associated with group memberships of the sshd process, if the configuration specifies running the command as a different user. |
6.7.0 | CVE-2021-45078 | stab_xcoff_builtin_type in stabs.c in GNU Binutils through 2.37 allows attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact, as demonstrated by an out-of-bounds write. NOTE this issue exists because of an incorrect fix for CVE-2018-12699. |
6.7.0 | CVE-2021-46195 | GCC v12.0 was discovered to contain an uncontrolled recursion via the component libiberty/rust-demangle.c. This vulnerability allows attackers to cause a Denial of Service (DoS) by consuming excessive CPU and memory resources. |
6.7.0 | CVE-2022-2208 | NULL Pointer Dereference in GitHub repository vim/vim prior to 8.2.5163. |
6.7.0 | CVE-2022-2210 | Out-of-bounds Write in GitHub repository vim/vim prior to 8.2. |
6.7.0 | CVE-2022-2257 | Out-of-bounds Read in GitHub repository vim/vim prior to 9.0. |
6.7.0 | CVE-2022-2264 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0. |
6.7.0 | CVE-2022-2284 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0. |
6.7.0 | CVE-2022-2285 | Integer Overflow or Wraparound in GitHub repository vim/vim prior to 9.0. |
6.7.0 | CVE-2022-2286 | Out-of-bounds Read in GitHub repository vim/vim prior to 9.0. |
6.7.0 | CVE-2022-2287 | Out-of-bounds Read in GitHub repository vim/vim prior to 9.0. |
6.7.0 | CVE-2022-2289 | Use After Free in GitHub repository vim/vim prior to 9.0. |
6.7.0 | CVE-2022-2598 | Out-of-bounds Write to API in GitHub repository vim/vim prior to 9.0.0100. |
6.7.0 | CVE-2022-3016 | Use After Free in GitHub repository vim/vim prior to 9.0.0286. |
6.7.0 | CVE-2022-3037 | Use After Free in GitHub repository vim/vim prior to 9.0.0322. |
6.7.0 | CVE-2022-3099 | Use After Free in GitHub repository vim/vim prior to 9.0.0360. |
6.7.0 | CVE-2022-37454 | The Keccak XKCP SHA-3 reference implementation before fdc6fef has an integer overflow and resultant buffer overflow that allows attackers to execute arbitrary code or eliminate expected cryptographic properties. This occurs in the sponge function interface. |
6.7.0 | CVE-2022-38533 | In GNU Binutils before 2.40, there is a heap-buffer-overflow in the error function bfd_getl32 when called from the strip_main function in strip-new via a crafted file. |
6.7.0 | CVE-2022-40433 | An issue was discovered in function ciMethodBlocks::make_block_at in Oracle JDK (HotSpot VM) 11, 17 and OpenJDK (HotSpot VM) 8, 11, 17, allows attackers to cause a denial of service. |
6.7.0 | CVE-2022-4285 | An illegal memory access flaw was found in the binutils package. Parsing an ELF file containing corrupt symbol version information may result in a denial of service. This issue is the result of an incomplete fix for CVE-2020-16599. |
6.7.0 | CVE-2022-42919 | Python 3.9.x before 3.9.16 and 3.10.x before 3.10.9 on Linux allows local privilege escalation in a non-default configuration. The Python multiprocessing library, when used with the forkserver start method on Linux, allows pickles to be deserialized from any user in the same machine local network namespace, which in many system configurations means any user on the same machine. Pickles can execute arbitrary code. Thus, this allows for local user privilege escalation to the user that any forkserver process is running as. Setting multiprocessing.util.abstract_sockets_supported to False is a workaround. The forkserver start method for multiprocessing is not the default start method. This issue is Linux specific because only Linux supports abstract namespace sockets. CPython before 3.9 does not make use of Linux abstract namespace sockets by default. Support for users manually specifying an abstract namespace socket was added as a bugfix in 3.7.8 and 3.8.3, but users would need to make specific uncommon API calls in order to do that in CPython before 3.9. |
6.7.0 | CVE-2022-45061 | An issue was discovered in Python before 3.11.1. An unnecessary quadratic algorithm exists in one path when processing some inputs to the IDNA (RFC 3490) decoder, such that a crafted, unreasonably long name being presented to the decoder could lead to a CPU denial of service. Hostnames are often supplied by remote servers that could be controlled by a malicious actor; in such a scenario, they could trigger excessive CPU consumption on the client attempting to make use of an attacker-supplied supposed hostname. For example, the attack payload could be placed in the Location header of an HTTP response with status code 302. A fix is planned in 3.11.1, 3.10.9, 3.9.16, 3.8.16, and 3.7.16. |
6.7.0 | CVE-2022-47673 | An issue was discovered in Binutils addr2line before 2.39.3, function parse_module contains multiple out of bound reads which may cause a denial of service or other unspecified impacts. |
6.7.0 | CVE-2022-47696 | An issue was discovered Binutils objdump before 2.39.3 allows attackers to cause a denial of service or other unspecified impacts via function compare_symbols. |
6.7.0 | CVE-2023-1579 | Heap based buffer overflow in binutils-gdb/bfd/libbfd.c in bfd_getl64. |
6.7.0 | CVE-2023-2222 | This vulnerability has not been analyzed by NVD yet. |
6.7.0 | CVE-2023-22603 | ConsultIDs none. Reason This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes none. |
6.7.0 | CVE-2023-22604 | ConsultIDs- none. Reason-This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes- none. |
6.7.0 | CVE-2023-22605 | ConsultIDs- none. Reason- This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes- none |
6.7.0 | CVE-2023-22606 | ConsultIDs- none. Reason- This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes- none |
6.7.0 | CVE-2023-22609 | ConsultIDs- none. Reason- This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes- none |
6.7.0 | CVE-2023-24535 | Parsing invalid messages can panic. Parsing a text-format message which contains a potential number consisting of a minus sign, one or more characters of whitespace, and no further input will cause a panic. |
6.7.0 | CVE-2023-25584 | An out-of-bounds read flaw was found in the parse_module function in bfd/vms-alpha.c in Binutils. |
CVE-2023-25585 | A flaw was found in Binutils. The use of an uninitialized field in the struct module *module may lead to application crash and local denial of service. | |
CVE-2023-25586 | A flaw was found in Binutils. A logic fail in the bfd_init_section_decompress_status function may lead to the use of an uninitialized variable that can cause a crash and local denial of service. | |
6.7.0 | CVE-2023-25588 | A flaw was found in Binutils. The field |
6.7.0 | CVE-2023-32002 | The use of |
6.7.0 | CVE-2023-32006 | The use of |
6.7.0 | CVE-2023-32559 | A privilege escalation vulnerability exists in the experimental policy mechanism in all active release lines- 16.x, 18.x and, 20.x. The use of the deprecated API |
6.7.0 | CVE-2023-38408 | 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. |
6.7.0 | CVE-2023-40217 | 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.) |
6.7.0 | CVE-2023-4863 | 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) |
6.7.0 | CVE-2023-5129 | This CVE- ID has been rejected or withdrawn by its CVE- Numbering Authority. Duplicate of CVE-2023-4863. |
6.7.0 | CVE-2023-5156 | A flaw was found in the GNU C Library. A recent fix for CVE-2023-4806 introduced the potential for a memory leak, which may result in an application crash. |
6.5.0 | CVE-2023-2650 | Possible DoS translating ASN.1 object identifiers |
6.5.0 | CVE-2023-2975 | AES-SIV implementation ignores empty associated data entries |
6.5.0 | CVE-2023-3446 | Excessive time spent checking DH keys and parameters |
6.5.0 | CVE-2023-3817 | Excessive time spent checking DH q parameter value |
6.5.0 | CVE-2023-35945 | Envoy vulnerable to HTTP/2 memory leak in nghttp2 codec |
6.5.0 | CVE-2022-29458 | ncurses 6.3 before patch 20220416 has an out-of-bounds read and segmentation violation in convert_strings in tinfo/read_entry.c in the terminfo library. |
6.5.0 | CVE-2022-3715 | A flaw was found in the bash package, where a heap-buffer overflow can occur in valid parameter_transform. This issue may lead to memory problems. |
6.5.0 | CVE-2022-41409 | Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input. |
6.5.0 | CVE-2022-4899 | A vulnerability was found in zstd v1.4.10, where an attacker can supply empty string as an argument to the command line tool to cause buffer overrun. |
6.5.0 | CVE-2016-1585 | In all versions of AppArmor mount rules are accidentally widened when compiled. |
6.5.0 | CVE-2016-2568 | pkexec, when used with --user nonpriv, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer. |
6.5.0 | CVE-2023-34969 | D-Bus before 1.15.6 sometimes allows unprivileged users to crash dbus-daemon. |
Parent topic:Yellowbrick Documentation