CVE-2024-47516: Pagure: argument injection in pagurerepo.log()
First published: Tue Oct 01 2024(Updated: )
A vulnerability was found in Pagure. An argument injection in Git during retrieval of the repository history leads to remote code execution on the Pagure instance.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Pagure |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-47516?
CVE-2024-47516 is considered a critical vulnerability due to its potential for remote code execution.
How do I fix CVE-2024-47516?
To fix CVE-2024-47516, update the Pagure software to the latest version that addresses this vulnerability.
What type of vulnerability is CVE-2024-47516?
CVE-2024-47516 is an argument injection vulnerability that results in remote code execution.
Who is affected by CVE-2024-47516?
CVE-2024-47516 affects Pagure instances that utilize Git for repository history retrieval.
What can happen if CVE-2024-47516 is exploited?
If exploited, CVE-2024-47516 can allow an attacker to execute arbitrary code on the affected Pagure instance.
- collector/mitre-cve
- source/MITRE
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2024-47516
- agent/title
- agent/references
- agent/weakness
- agent/type
- agent/first-publish-date
- agent/description
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/severity
- agent/author
- agent/source
- agent/event
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- vendor/pagure
- canonical/pagure