Upstream information
Description
notion-go is a collection of libraries for supporting sign and verify OCI artifacts. Based on Notary Project specifications. The issue was identified during Quarkslab's security audit on the Certificate Revocation List (CRL) based revocation check feature.After retrieving the CRL, notation-go attempts to update the CRL cache using the os.Rename method. However, this operation may fail due to operating system-specific limitations, particularly when the source and destination paths are on different mount points. This failure could lead to an unexpected program termination. In method `crl.(*FileCache).Set`, a temporary file is created in the OS dedicated area (like /tmp for, usually, Linux/Unix). The file is written and then it is tried to move it to the dedicated `notation` cache directory thanks `os.Rename`. As specified in Go documentation, OS specific restriction may apply. When used with Linux OS, it is relying on rename syscall from the libc and as per the documentation, moving a file to a different mountpoint raises an EXDEV error, interpreted as Cross device link not permitted error. Some Linux distribution, like RedHat use a dedicated filesystem (tmpfs), mounted on a specific mountpoint (usually /tmp) for temporary files. When using such OS, revocation check based on CRL will repeatedly crash notation. As a result the signature verification process is aborted as process crashes. This issue has been addressed in version 1.3.0-rc.2 and all users are advised to upgrade. There are no known workarounds for this vulnerability.
SUSE information
Overall state of this security issue: Resolved
This issue is currently rated as having low severity.
| CNA (GitHub) | |
|---|---|
| Base Score | 3.3 |
| Vector | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L |
| Attack Vector | Local |
| Attack Complexity | Low |
| Privileges Required | None |
| User Interaction | Required |
| Scope | Unchanged |
| Confidentiality Impact | None |
| Integrity Impact | None |
| Availability Impact | Low |
| CVSSv3 Version | 3.1 |
SUSE Security Advisories:
- SUSE-SU-2025:0297-1, published 2025-01-30T14:03:41Z
- openSUSE-SU-2025:14653-1, published Fri Jan 17 18:50:11 2025
List of released packages
| Product(s) | Fixed package version(s) | References |
|---|---|---|
| SUSE Linux Enterprise Module for Package Hub 15 SP6 |
| Patchnames: SUSE-SLE-Module-Packagehub-Subpackages-15-SP6-2025-297 |
| openSUSE Leap 15.6 |
| Patchnames: openSUSE-SLE-15.6-2025-297 |
| openSUSE Tumbleweed |
| Patchnames: openSUSE-Tumbleweed-2025-14653 |
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.
| Product(s) | Source package | State |
|---|---|---|
| Products under general support and receiving all security fixes. | ||
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | govulncheck-vulndb | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | Released |
| openSUSE Leap 15.6 | govulncheck-vulndb | Released |
| Products past their end of life and not receiving proactive updates anymore. | ||
| openSUSE Leap 15.5 | govulncheck-vulndb | Affected |
SUSE Timeline for this CVE
CVE page created: Tue Jan 14 00:00:51 2025CVE page last modified: Thu Jan 30 20:02:07 2025