Slackware64-14.1 ChangeLog (2023-01-18)

Wed Jan 18 06:11:54 UTC 2023

  • patches/packages/git-2.30.7-x86_64-1_slack14.1.txz
    This release fixes two security issues:
    * CVE-2022-41903:
    git log has the ability to display commits using an arbitrary
    format with its –format specifiers. This functionality is also
    exposed to git archive via the export-subst gitattribute.
    When processing the padding operators (e.g., %<(, %<|(, %>(,
    %»(, or %><( ), an integer overflow can occur in
    pretty.c::format_and_pad_commit() where a size_t is improperly
    stored as an int, and then added as an offset to a subsequent
    memcpy() call.
    This overflow can be triggered directly by a user running a
    command which invokes the commit formatting machinery (e.g., git
    log –format=…). It may also be triggered indirectly through
    git archive via the export-subst mechanism, which expands format
    specifiers inside of files within the repository during a git
    archive.
    This integer overflow can result in arbitrary heap writes, which
    may result in remote code execution.
    * CVE-2022-23521:
    gitattributes are a mechanism to allow defining attributes for
    paths. These attributes can be defined by adding a `.gitattributes`
    file to the repository, which contains a set of file patterns and
    the attributes that should be set for paths matching this pattern.
    When parsing gitattributes, multiple integer overflows can occur
    when there is a huge number of path patterns, a huge number of
    attributes for a single pattern, or when the declared attribute
    names are huge.
    These overflows can be triggered via a crafted `.gitattributes` file
    that may be part of the commit history. Git silently splits lines
    longer than 2KB when parsing gitattributes from a file, but not when
    parsing them from the index. Consequentially, the failure mode
    depends on whether the file exists in the working tree, the index or
    both.
    This integer overflow can result in arbitrary heap reads and writes,
    which may result in remote code execution.
    For more information, see:
    https://www.cve.org/CVERecord?id=CVE-2022-41903
    https://www.cve.org/CVERecord?id=CVE-2022-23521
    (* Security fix *)
  • patches/packages/httpd-2.4.55-x86_64-1_slack14.1.txz
    This update fixes bugs and the following security issues:
    mod_proxy allows a backend to trigger HTTP response splitting.
    mod_proxy_ajp possible request smuggling.
    mod_dav out of bounds read, or write of zero byte.
    For more information, see:
    https://downloads.apache.org/httpd/CHANGES_2.4.55
    https://www.cve.org/CVERecord?id=CVE-2022-37436
    https://www.cve.org/CVERecord?id=CVE-2022-36760
    https://www.cve.org/CVERecord?id=CVE-2006-20001
    (* Security fix *)
  • patches/packages/libXpm-3.5.15-x86_64-1_slack14.1.txz
    This update fixes security issues:
    Infinite loop on unclosed comments.
    Runaway loop with width of 0 and enormous height.
    Compression commands depend on $PATH.
    For more information, see:
    https://www.cve.org/CVERecord?id=CVE-2022-46285
    https://www.cve.org/CVERecord?id=CVE-2022-44617
    https://www.cve.org/CVERecord?id=CVE-2022-4883
    (* Security fix *)
  • news/2023/01/18/slackware64-14.1-changelog.txt
  • Last modified: 12 months ago
  • by Giuseppe Di Terlizzi