Ecosyste.ms: Advisories
An open API service providing security vulnerability metadata for many open source software ecosystems.
Security Advisories: GSA_kwCzR0hTQS1xamgzLTRqM2gtdm13cM4ABDOr
notation-go has an OS error when setting CRL cache leads to denial of signature verification
Summary
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.
Details
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
.
PoC
- Ensure that the temporary file storage area (e.g., /tmp) is mounted on a different mount point than the user's 'notation' cache directory.
- Either disable the Online Certificate Status Protocol (OCSP) revocation check, or utilize certificates that exclusively support Certificate Revocation Lists (CRLs) for revocation check.
- Try to verify a previously generated signature using the 'notation' tool.
Impact
The signature verification process is aborted as process crashes.
Remediation
The cache file should be created, written, then copied to the wanted final location, and finally removed. Additionally, this error shouldn't lead to a crash as it is not fatal and shouldn't prevent the rest of the program to properly continue
Permalink: https://github.com/advisories/GHSA-qjh3-4j3h-vmwpJSON: https://advisories.ecosyste.ms/api/v1/advisories/GSA_kwCzR0hTQS1xamgzLTRqM2gtdm13cM4ABDOr
Source: GitHub Advisory Database
Origin: Unspecified
Severity: Low
Classification: General
Published: 4 days ago
Updated: 3 days ago
CVSS Score: 3.3
CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
EPSS Percentage: 0.00045
EPSS Percentile: 0.17569
Identifiers: GHSA-qjh3-4j3h-vmwp, CVE-2024-51491
References:
- https://github.com/notaryproject/notation-go/security/advisories/GHSA-qjh3-4j3h-vmwp
- https://github.com/notaryproject/notation-go/commit/3c3302258ad510fbca2f8a73731569d91f07d196
- https://nvd.nist.gov/vuln/detail/CVE-2024-51491
- https://man7.org/linux/man-pages/man2/rename.2.html
- https://pkg.go.dev/vuln/GO-2025-3382
- https://github.com/advisories/GHSA-qjh3-4j3h-vmwp
Blast Radius: 4.7
Affected Packages
go:github.com/notaryproject/notation-go
Dependent packages: 29Dependent repositories: 26
Downloads:
Affected Version Ranges: = 1.3.0-rc.1
Fixed in: 1.3.0-rc.2
All affected versions:
All unaffected versions: 1.0.0, 1.0.1, 1.1.0, 1.1.1, 1.1.2, 1.2.0, 1.2.1