Select your language

25 Jun 2024

Ghostscript 10.03.1

Security release!

Fixes for CVE-2024-33869, CVE-2023-52722, CVE-2024-33870, CVE-2024-33871 and CVE-2024-29510

News

Recent Changes in Ghostscript

Version 10.03.1 (2024-05-02)

Highlights in this release include:

  • Fixes for CVE-2024-33869, CVE-2023-52722, CVE-2024-33870, CVE-2024-33871 and CVE-2024-29510

  • IMPORTANT: For the 10.04.0 release (fall/autumn 2024) we will be adding protection for device selection from PostScript input. This will mean that, by default, only the device specified on the command line will be permitted. Similar to the file permissions, there will be a "--permit-devices=" allowing a comma separation list of allowed devices. This will also take a single wildcard "*" allowing any device.

    Any application which relies on allowing PostScript to change devices during a job will have to be aware, and take action to deal with this change.

    The exception is "nulldevice", switching to that requires no special action.

  • A vulnerability was identified in the way Ghostscript/GhostPDL called tesseract for the OCR devices, which could allow arbitrary code execution. As as result, we strongly urge anyone including the OCR devices in their build to update as soon as possible.

  • As of this release (10.03.1) pdfwrite creates PDF files with XRef streams and ObjStm streams. This can result in considerably smaller PDF output files. See Vector Devices for more details.

  • Ghostscript/pdfwrite now supports passing through PDF "Optional Content".

  • Our efforts in code hygiene and maintainability continue.

  • The usual round of bug fixes, compatibility changes, and incremental improvements.

  • (9.53.0) We have added the capability to build with the Tesseract OCR engine. In such a build, new devices are available (pdfocr8/pdfocr24/pdfocr32) which render the output file to an image, OCR that image, and output the image "wrapped" up as a PDF file, with the OCR generated text information included as "invisible" text (in PDF terms, text rendering mode 3).

    Mainly due to time constraints, we only support including Tesseract from source included in our release packages, and not linking to Tesseract/Leptonica shared libraries. Whether we add this capability will be largely dependent on community demand for the feature.

    See Enabling OCR for more details.

For a list of open issues, or to report problems, please visit bugs.ghostscript.com.

Incompatible changes

Included below are incompatible changes from recent releases (the specific release in question is listed in parentheses). We include these, for now, as we are aware that not everyone upgrades with every release.

  • (10.03.1) Almost all the "internal" PostScript procedures defined during the interpreter startup are now "executeonly", further reducing the attack surface of the interpreter.

    The nature of these procedures means there should be no impact for legitimate usage, but it is possible it will impact uses which abuse the previous accessibility (even for legitimate reasons). Such cases may now require "DELAYBIND", See DELAYBIND

  • (10.03.1) The "makeimagedevice" non-standard operator has been removed. It allowed low level access to the graphics library in a way that was, essentially impossible to secure.

  • (10.03.1) The "putdeviceprops", "getdeviceprops", "finddevice", "copydevice", "findprotodevice" non-standard operators have all been removed. They provided functionality that is either accessible through standard operators, or should not be used by user PostScript.

  • (10.03.1) The process of "tidying" the PostScript namespace should have removed only non-standard and undocumented operators. Nevertheless, it is possible that any integrations or utilities that rely on those non-standard and undocumented operators may stop working or may change behaviour.

    If you encounter such a case, please contact us (Discord, #ghostscript IRC channel, or the gs-devel mailing list would be best), and we'll work with you to either find an alternative solution or return the previous functionality, if there is genuinely no other option.

  • (9.55.0) Changes to the device API. This will affect developers and maintainers of Ghostscript devices. Firstly, and most importantly, the way device-specific "procs" are specified has been rewritten to make it (we think!) clearer and less confusing. See The Interface between Ghostscript and Device Drivers and The Great Device Rework Of 2021 for more details.

  • (9.55.0) The command line options -sGraphicsICCProfile=___, -dGraphicsIntent=#, -dGraphicsBlackPt=#, -dGraphicsKPreserve=# have been changed to -sVectorICCProfile=___, -dVectorIntent=#, -dVectorBlackPt=#, -dVectorKPreserve=#.

  • (9.53.0) As of 9.53.0, we have (re-)introduced the patch level to the version number, this helps facilitate a revised policy on handling security-related issues.

    Note for GSView Users: The patch level addition breaks GSView 5 (it is hardcoded to check for versions 704-999. It is possible, but not guaranteed that a GSView update might be forthcoming to resolve this.

  • (9.52) -dALLOWPSTRANSPARENCY: The transparency compositor (and related features), whilst we are improving it, remains sensitive to being driven correctly, and incorrect use can have unexpected/undefined results. Hence, as part of improving security, we limited access to these operators, originally using the -dSAFER feature. As we made "SAFER" the default mode, that became unacceptable, hence the new option -dALLOWPSTRANSPARENCY which enables access to the operators.

  • (9.50) There are a couple of subtle incompatibilities between the old and new SAFER implementations. Firstly, as mentioned in the 9.50 release notes, SAFER now leaves standard PostScript functionality unchanged (except for the file access limitations). Secondly, the interaction with save/restore operations has changed. See SAFER.

    Important Note for Windows Users:
    The file/path pattern matching is case-sensitive, even on Windows. This is a change in behaviour compared to the old code which, on Windows, was case insensitive. This is in recognition of changes in Windows behaviour, in that it now supports (although does not enforce) case sensitivity.

Changelog

From 9.55.0 onwards, in recognition of how unwieldy very large HTML files can become (History9.html had reached 8.1Mb!), we intend to only include the summary highlights (above).

For anyone wanting the full details of the changes in a release, we ask them to look at the history in our public git repository: ghostpdl-10.03.1 log.

If this change does not draw negative feedback, History?.htm file(s) will be removed from the release archives.


Copyright © 2005-2024 Artifex Software, Inc. All rights reserved.

This software is provided AS-IS with no warranty, either express or implied. This software is distributed under license and may not be copied, modified or distributed except as expressly authorized under the terms of that license. Refer to licensing information at https://www.artifex.com or contact Artifex Software, Inc., 39 Mesa Street, Suite 108A, San Francisco, CA 94129, USA,

Ghostscript version 10.03.1, 02 May 2024


17 Jun 2024

Git 2.45.2

Reversal of Git 2.45.1 Security Release

17 Jun 2024

Composer 2.7.7 Security Release

Security release!

This release includes fixes for issues found in a security audit by Cure53 funded by Alpha-Omega.

  • Security: Fixed command injection via malicious git branch name (GHSA-47f6-5gq3-vx9c / CVE-2024-35241)
  • Security: Fixed multiple command injections via malicious git/hg branch names (GHSA-v9qv-c7wm-wgmf / CVE-2024-35242)
  • Security: Fixed secure-http checks that could be bypassed by using malformed URL formats (fa3b958)
  • Security: Fixed Filesystem::isLocalPath including windows-specific checks on linux (3c37a67)
  • Security: Fixed perforce argument escaping (3773f77)
  • Security: Fixed handling of zip bombs when extracting archives (de5f7e3)
  • Security: Fixed Windows command parameter escaping to prevent abuse of unicode characters with best fit encoding conversion, reported by Splitline Huang (3130a74, 04a63b3)
  • Fixed PSR violations for classes not matching the namespace of a rule being hidden, this may lead to new violations being shown (#11957)
  • Fixed UX when a plugin is still in vendor dir but is not required nor allowed anymore after changing branches (#12000)
  • Fixed new platform requirements from composer.json not being checked if the lock file is outdated (#12001)
  • Fixed ability for config command to remove autoload keys (#11967)
  • Fixed empty type support in init command (#11999)
  • Fixed git clone errors when safe.bareRepository is set to strict in the git config (#11969)
  • Fixed regression showing network errors on PHP <8.1 (#11974)
  • Fixed some color bleed from a few warnings (#11972)

09 Jun 2024

Bearsampp 2024.6.9

Enhancement release

[Enhancement] added german language file
[Enhancement] add password manager feature

03 Jun 2024

Bearsampp 2024.6.3 Hotfix

Fixes issue where certain modules were missing by default in full release of Bearsampp and iconography fixes

Fixes issue where certain modules were missing by default in full release of Bearsampp

Updates Iconography back to production version of Bearsampp

29 May 2024

Bearsampp 2024.5.29 Urgent hotfix

This is an urgent hotfix resolving the issue where localhost and applications were not working.

https://github.com/Bearsampp/Bearsampp/releases/download/2024.5.29/Bearsampp-2024.5.29.7z

27 May 2024

Bearsampp 2024.5.27 Released


Get yours today Bearsampp 2024.5.27

21 May 2024

Git 2.45.1 Security Release

Security release!

Git for Windows v2.45.1

Changes since Git for Windows v2.45.0 (April 29th 2024)

Git for Windows for Windows v2.45 is the last version to support for Windows 7 and for Windows 8, see MSYS2's corresponding deprecation announcement (Git for Windows relies on MSYS2 for components such as Bash and Perl).

Please also note that the 32-bit variant of Git for Windows is deprecated; Its last official release is planned for 2025.

New Features

Bug Fixes

  • CVE-2024-32002: Recursive clones on case-insensitive filesystems that support
    symbolic links are susceptible to case confusion that can be exploited to
    execute just-cloned code during the clone operation.
  • CVE-2024-32004: Repositories can be configured to execute arbitrary code
    during local clones. To address this, the ownership checks introduced in
    v2.30.3 are now extended to cover cloning local repositories.
  • CVE-2024-32020: Local clones may end up hardlinking files into the target
    repository's object database when source and target repository reside on the
    same disk. If the source repository is owned by a different user, then those
    hardlinked files may be rewritten at any point in time by the untrusted user.
  • CVE-2024-32021: When cloning a local source repository that contains symlinks
    via the filesystem, Git may create hardlinks to arbitrary user-readable files
    on the same filesystem as the target repository in the objects/ directory.
  • CVE-2024-32465: It is supposed to be safe to clone untrusted repositories,
    even those unpacked from zip archives or tarballs originating from untrusted
    sources, but Git can be tricked to run arbitrary code as part of the clone.

  • Defense-in-depth: submodule: require the submodule path to contain
    directories only.
  • Defense-in-depth: clone: when symbolic links collide with directories, keep
    the latter.
  • Defense-in-depth: clone: prevent hooks from running during a clone.
  • Defense-in-depth: core.hooksPath: add some protection while cloning.
  • Defense-in-depth: fsck: warn about symlink pointing inside a gitdir.
  • Various fix-ups on HTTP tests.
  • HTTP Header redaction code has been adjusted for a newer version of cURL
    library that shows its traces differently from earlier versions.
  • Fix was added to work around a regression in libcURL 8.7.0 (which has already
    been fixed in their tip of the tree).
  • Replace macos-12 used at GitHub CI with macos-13.
  • ci(linux-asan/linux-ubsan): let's save some time
  • Tests with LSan from time to time seem to emit harmless message that makes
    our tests unnecessarily flakey; we work it around by filtering the
    uninteresting output.
  • Update GitHub Actions jobs to avoid warnings against using deprecated version
    of Node.js.
09 May 2024

Git 2.45.0 Released

Changes since Git for Windows v2.44.0 (February 23rd 2024)

Git for Windows for Windows v2.45 is the last version to support for Windows 7 and for Windows 8, see MSYS2's corresponding deprecation announcement (Git for Windows relies on MSYS2 for components such as Bash and Perl).

Please also note that the 32-bit variant of Git for Windows is deprecated; Its last official release is planned for 2025.

New Features

Bug Fixes

Our Supporters

Sorry, this website uses features that your browser doesn't support. Upgrade to a newer version of Firefox, Chrome, Safari, or Edge and you'll be all set.