CVE-2024-4982 | Pagure: path traversal in view_issue_raw_file()

Exp

A directory traversal vulnerability was discovered in Pagure server. If a malicious user submits a specially cratfted git repository they could discover secrets on the server.

Published: 2025-05-12 Last update: 2025-08-07 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-4982 is rated High Exploit Risk (60.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.22%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-4982

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-4982

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-23 0.44% 0.22% -0.22%
2 2026-03-08 0.26% 0.44% +0.18%
3 2026-02-26 0.26%

Full EPSS history (15 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-4982

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.6 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
2.8 4.7 [email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 3.6 [email protected]

Weakness enumeration for CVE-2024-4982

OS Trackers for CVE-2024-4982

vendor priority summary link
debian not yet assigned CVE-2024-4982 not yet assigned priority: Debian including 1 source packages (pagure), 3 status rows across 3 suites (bullseye, sid, trixie): resolved 3. https://security-tracker.debian.org/tracker/CVE-2024-4982
ubuntu medium CVE-2024-4982 medium priority: Ubuntu including 1 source packages (pagure), 7 status rows across 7 suites (focal, jammy, noble, oracular, plucky, questing, upstream): released 4, ignored 2, not-affected 1. https://ubuntu.com/security/CVE-2024-4982

Affected software / configurations for CVE-2024-4982

Vendor Product Version Raw CPE
redhat pagure < 5.14.1 cpe:2.3:a:redhat:pagure:*:*:*:*:*:*:*:*

References for CVE-2024-4982

cvelogic Threat Intelligence