Arbitrary file write via followed repository symlinks
Published May 12, 2025 · Updated May 12, 2025
Path traversal in Red Hat Pagure before 5.14.1 allows remote authenticated users to write outside a repository via symbolic links. The _update_file_in_git() web-editor path joins an attacker-controlled filename, then opens it without resolving and confining symbolic-link targets to the temporary clone. Repository write access is required; writable targets under the Pagure git service account can be replaced, enabling code execution in demonstrated configurations.
Summary
What happened
Path traversal in Red Hat Pagure before 5.14.1 allows remote authenticated users to write outside a repository via symbolic links. The _update_file_in_git() web-editor path joins an attacker-controlled filename, then opens it without resolving and confining symbolic-link targets to the temporary clone. Repository write access is required; writable targets under the Pagure git service account can be replaced, enabling code execution in demonstrated configurations.
The record
- CVE
- CVE-2024-4981
- Published
- May 12, 2025
- Updated
- May 12, 2025
- Vendor
- 389 Directory Server
- Product
- Pagure
- Classifications
- CWE-552, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 12, 2025CVE publishedPublication date reported by the CVE source.
- May 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <5.14.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Pagure symbolic-link arbitrary-write reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Demonstrated code execution on Pagure stagingreported exploitation
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo