A flaw was found in librepo in versions before 1.12.1.
A flaw was found in librepo in versions before 1.12.1. A directory traversal vulnerability was found where it failed to sanitize paths in remote repository metadata. An attacker controlling a remote repository may be able to copy files outside of the destination directory on the targeted system via path traversal. This flaw could potentially result in system compromise via the overwriting of critical system files. The highest threat from this flaw is to users that make use of untrusted third-party repositories.
- Published
- Aug 30, 2020
- Updated
- Jun 16, 2026
- EPSS
- 2.5% · 84th percentile
- CWE
- CWE-22
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.5%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| redhat | librepo | cpe:2.3:a:redhat:librepo |
| opensuse | backports sle | cpe:2.3:a:opensuse:backports_sle |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora31
- fedoraproject fedora32
- fedoraproject fedora33
- opensuse backports sle15.0
- opensuse leap15.2
- redhat librepobefore 1.12.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a librepo
- librepo versions before 1.12.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.2 | librepo | before 1.12.1-lp152.2.6.1 | 1.12.1-lp152.2.6.1 |
| openSUSE:Leap 15.2 | librepo | before 1.11.2-lp152.2.3.1 | 1.11.2-lp152.2.3.1 |
| Red Hat:enterprise_linux:7::client | librepo | before 0:1.8.1-8.el7_9 | 0:1.8.1-8.el7_9 |
| Red Hat:enterprise_linux:7::client | librepo-debuginfo | before 0:1.8.1-8.el7_9 | 0:1.8.1-8.el7_9 |
| Red Hat:enterprise_linux:7::client | librepo-devel | before 0:1.8.1-8.el7_9 | 0:1.8.1-8.el7_9 |
| Red Hat:enterprise_linux:7::client | python-librepo | before 0:1.8.1-8.el7_9 | 0:1.8.1-8.el7_9 |
| Red Hat:enterprise_linux:8::baseos | librepo | before 0:1.11.0-3.el8_2 | 0:1.11.0-3.el8_2 |
| Red Hat:enterprise_linux:8::baseos | librepo-debuginfo | before 0:1.11.0-3.el8_2 | 0:1.11.0-3.el8_2 |
| Red Hat:enterprise_linux:8::baseos | librepo-debugsource | before 0:1.11.0-3.el8_2 | 0:1.11.0-3.el8_2 |
| Red Hat:enterprise_linux:8::baseos | python3-librepo | before 0:1.11.0-3.el8_2 | 0:1.11.0-3.el8_2 |
| Red Hat:enterprise_linux:8::baseos | python3-librepo-debuginfo | before 0:1.11.0-3.el8_2 | 0:1.11.0-3.el8_2 |
| Red Hat:rhel_e4s:8.0::baseos | librepo | before 0:1.9.2-2.el8_0 | 0:1.9.2-2.el8_0 |
| Red Hat:rhel_e4s:8.0::baseos | librepo-debuginfo | before 0:1.9.2-2.el8_0 | 0:1.9.2-2.el8_0 |
| Red Hat:rhel_e4s:8.0::baseos | librepo-debugsource | before 0:1.9.2-2.el8_0 | 0:1.9.2-2.el8_0 |
| Red Hat:rhel_e4s:8.0::baseos | python3-librepo | before 0:1.9.2-2.el8_0 | 0:1.9.2-2.el8_0 |
| Red Hat:rhel_e4s:8.0::baseos | python3-librepo-debuginfo | before 0:1.9.2-2.el8_0 | 0:1.9.2-2.el8_0 |
| Red Hat:rhel_eus:8.1::baseos | librepo | before 0:1.10.3-4.el8_1 | 0:1.10.3-4.el8_1 |
| Red Hat:rhel_eus:8.1::baseos | librepo-debuginfo | before 0:1.10.3-4.el8_1 | 0:1.10.3-4.el8_1 |
| Red Hat:rhel_eus:8.1::baseos | librepo-debugsource | before 0:1.10.3-4.el8_1 | 0:1.10.3-4.el8_1 |
| Red Hat:rhel_eus:8.1::baseos | python3-librepo | before 0:1.10.3-4.el8_1 | 0:1.10.3-4.el8_1 |
| Red Hat:rhel_eus:8.1::baseos | python3-librepo-debuginfo | before 0:1.10.3-4.el8_1 | 0:1.10.3-4.el8_1 |
| SUSE:Package Hub 15 SP2 | librepo | before 1.11.2-bp152.2.3.1 | 1.11.2-bp152.2.3.1 |
| SUSE:Package Hub 15 SP2 | librepo | before 1.12.1-bp152.2.6.1 | 1.12.1-bp152.2.6.1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:librepo | 1.11.2-lp152.2.3.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| red hat:librepo | 0:1.11.0-3.el8_2 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:librepo-debuginfo | 0:1.11.0-3.el8_2 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:librepo-debugsource | 0:1.11.0-3.el8_2 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:librepo-devel | 0:1.8.1-8.el7_9 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:python-librepo | 0:1.8.1-8.el7_9 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:python3-librepo | 0:1.11.0-3.el8_2 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:python3-librepo-debuginfo | 0:1.11.0-3.el8_2 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| suse:librepo | 1.11.2-bp152.2.3.1 · SUSE:Package Hub 15 SP2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) { return res.sendStatus(400);}res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- lists.opensuse.org/opensuse-security-announce/2020-08/msg00072.html
- lists.opensuse.org/opensuse-security-announce/2020-09/msg00055.html
- bugzilla.redhat.com/show_bug.cgi?id=1866498
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/33RX4P5R5YL4NZSFSE4NOX37X6YCXAS4/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OOMDEQBRJ7SO2QWL7H23G3VV2VSCUYOY/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XDMHVY7OMIJNSPVZ2GJWHT77Z5V3YJ55/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.