CyberSecBulletin
CVE-2024-4981NVD status: Analyzed

Pagure: Files or Directories Accessible to External Parties

Published Updated By the CyberSecBulletin desk

CVE-2024-4981 is a high-severity files or directories accessible to external parties vulnerability in Pagure from Red Hat, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 5.14.1 as the first without the flaw, so updating Pagure to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.43% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Pagure to 5.14.1 or a later version.
  2. Read the advisory on access.redhat.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Red HatPagurebefore 5.14.15.14.1

Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
LowLimited modification of data is possible.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.6HighCNA (puiterwijk.org)
CVSS 3.17.1HighNVD

Official description

A vulnerability was discovered in Pagure server. If a malicious user were to submit a git repository with symbolic links, the server could unintentionally show incorporate and make visible content from outside the git repo.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Files or Directories Accessible to External Parties

The product makes files or directories accessible to unauthorized actors, even though they should not be.

How developers prevent this class of flaw

  • When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.

More Files or Directories Accessible to External Parties vulnerabilities (CWE-552)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Technical write-ups (may include proof of concept)

Other references

Recent Files or Directories Accessible to External Parties vulnerabilities

Spotted an error? Tell us.