openSUSE-SU-2025:0091-1: moderate: Security update for restic

openSUSE Security Update: Security update for restic
_______________________________

Announcement ID: openSUSE-SU-2025:0091-1
Rating: moderate
References: #1239264
Cross-References: CVE-2025-22868
CVSS scores:
CVE-2025-22868 (SUSE): 8.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Affected Products:
openSUSE Backports SLE-15-SP6
_______________________________

An update that fixes one vulnerability is now available.

Description:

This update for restic fixes the following issues:

- Fixed CVE-2025-22868: golang.org/x/oauth2/jws: Unexpected memory
consumption during token parsing in golang.org/x/oauth2 (boo#1239264)

- Update to version 0.17.3

- Fix #4971: Fix unusable mount on macOS Sonoma
- Fix #5003: Fix metadata errors during backup of removable disks
on Windows
- Fix #5101: Do not retry load/list operation if SFTP connection is
broken
- Fix #5107: Fix metadata error on Windows for backups using VSS
- Enh #5096: Allow prune --dry-run without lock

- Update to version 0.17.2

- Fix #4004: Support container-level SAS/SAT tokens for Azure backend
- Fix #5047: Resolve potential error during concurrent cache cleanup
- Fix #5050: Return error if tag fails to lock repository
- Fix #5057: Exclude irregular files from backups
- Fix #5063: Correctly backup extended metadata when using VSS on Windows

- Update to version 0.17.1

- Fix #2004: Correctly handle volume names in backup command on Windows
- Fix #4945: Include missing backup error text with --json
- Fix #4953: Correctly handle long paths on older Windows versions
- Fix #4957: Fix delayed cancellation of certain commands
- Fix #4958: Don't ignore metadata-setting errors during restore
- Fix #4969: Correctly restore timestamp for files with resource forks
on macOS
- Fix #4975: Prevent backup --stdin-from-command from panicking
- Fix #4980: Skip extended attribute processing on unsupported Windows
volumes
- Fix #5004: Fix spurious "A Required Privilege Is Not Held by the
Client" error
- Fix #5005: Fix rare failures to retry locking a repository
- Fix #5018: Improve HTTP/2 support for REST backend
- Chg #4953: Also back up files with incomplete metadata
- Enh #4795: Display progress bar for restore --verify
- Enh #4934: Automatically clear removed snapshots from cache
- Enh #4944: Print JSON-formatted errors during restore --json
- Enh #4959: Return exit code 12 for "bad password" errors
- Enh #4970: Make timeout for stuck requests customizable

- Update to version 0.17.0

- Fix #3600: Handle unreadable xattrs in folders above backup source
- Fix #4209: Fix slow SFTP upload performance
- Fix #4503: Correct hardlink handling in stats command
- Fix #4568: Prevent forget --keep-tags from deleting all
snapshots
- Fix #4615: Make find not sometimes ignore directories
- Fix #4656: Properly report ID of newly added keys
- Fix #4703: Shutdown cleanly when receiving SIGTERM
- Fix #4709: Correct --no-lock handling of ls and tag commands
- Fix #4760: Fix possible error on concurrent cache cleanup
- Fix #4850: Handle UTF-16 password files in key command correctly
- Fix #4902: Update snapshot summary on rewrite
- Chg #956: Return exit code 10 and 11 for non-existing and locked
repository
- Chg #4540: Require at least ARMv6 for ARM binaries
- Chg #4602: Deprecate legacy index format and s3legacy repository layout
- Chg #4627: Redesign backend error handling to improve reliability
- Chg #4707: Disable S3 anonymous authentication by default
- Chg #4744: Include full key ID in JSON output of key list
- Enh #662: Optionally skip snapshot creation if nothing changed
- Enh #693: Include snapshot size in snapshots output
- Enh #805: Add bitrot detection to diff command
- Enh #828: Improve features of the repair packs command
- Enh #1786: Support repositories with empty password
- Enh #2348: Add --delete option to restore command
- Enh #3067: Add extended options to configure Windows Shadow Copy
Service
- Enh #3406: Improve dump performance for large files
- Enh #3806: Optimize and make prune command resumable
- Enh #4006: (alpha) Store deviceID only for hardlinks
- Enh #4048: Add support for FUSE-T with mount on macOS
- Enh #4251: Support reading backup from a command's standard
output
- Enh #4287: Support connection to rest-server using unix socket
- Enh #4354: Significantly reduce prune memory usage
- Enh #4437: Make check command create non-existent cache directory
- Enh #4472: Support AWS Assume Role for S3 backend
- Enh #4547: Add --json option to version command
- Enh #4549: Add --ncdu option to ls command
- Enh #4573: Support rewriting host and time metadata in snapshots
- Enh #4583: Ignore s3.storage-class archive tiers for metadata
- Enh #4590: Speed up mount command's error detection
- Enh #4601: Add support for feature flags
- Enh #4611: Back up more file metadata on Windows
- Enh #4664: Make ls use message_type field in JSON output
- Enh #4676: Make key command's actions separate sub-commands
- Enh #4678: Add --target option to the dump command
- Enh #4708: Back up and restore SecurityDescriptors on Windows
- Enh #4733: Allow specifying --host via environment variable
- Enh #4737: Include snapshot ID in reason field of forget JSON
output
- Enh #4764: Support forgetting all snapshots
- Enh #4768: Allow specifying custom User-Agent for outgoing requests
- Enh #4781: Add restore options to read include/exclude patterns from
files
- Enh #4807: Support Extended Attributes on Windows NTFS
- Enh #4817: Make overwrite behavior of restore customizable
- Enh #4839: Add dry-run support to restore command for all the details
see https://github.com/restic/restic/releases/tag/v0.17.0
or /usr/share/doc/packages/restic/CHANGELOG.md

- Update to version 0.16.5
- Enh #4799: Add option to force use of Azure CLI credential
- Enh #4873: Update dependencies

- Update to version 0.16.4 This release works around and improves
detection of a bug in the compression library used by restic. The
resulting issue only happens when using restic 0.16.3 and the max
compression level (the default auto and off compression levels are not
affected), and when the source files being backed up have specific data
in them to trigger the bug. If you use max compression, you can use
restic check --read-data to make sure you're not affected.

- Update to version 0.16.3

- Fix #4560: Improve errors for irregular files on Windows
- Fix #4574: Support backup of deduplicated files on Windows again
- Fix #4612: Improve error handling for rclone backend
- Fix #4624: Correct restore progress information if an error
occurs
- Fix #4626: Improve reliability of restoring large files

- Update to version 0.16.2

- Fix #4540: Restore ARMv5 support for ARM binaries
- Fix #4545: Repair documentation build on Read the Docs

- Update to version 0.16.1

A very long list of improvements for all the details see
https://github.com/restic/restic/releases/tag/v0.16.1 It contains an
important bug fix which prevents data corruption when compression is set
to max.

Patch Instructions:

To install this openSUSE Security Update use the SUSE recommended installation methods
like YaST online_update or "zypper patch".

Alternatively you can run the command listed for your product:

- openSUSE Backports SLE-15-SP6:

zypper in -t patch openSUSE-2025-91=1

Package List:

- openSUSE Backports SLE-15-SP6 (aarch64 i586 ppc64le s390x x86_64):

restic-0.17.3-bp156.2.3.1

- openSUSE Backports SLE-15-SP6 (noarch):

restic-bash-completion-0.17.3-bp156.2.3.1
restic-zsh-completion-0.17.3-bp156.2.3.1

References:

https://www.suse.com/security/cve/CVE-2025-22868.html
https://bugzilla.suse.com/1239264