CVE-2020-14352

Public on

Last Modified: UTC

Important Important Impact What does this mean?
8 CVSS v3 Base Score

Description

A flaw was found in librepo. 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.

Statement

This issue is rated as having Moderate impact on Red Hat Enterprise Linux 7 because DNF is not installed by default. The DNF package is available through the Extras channel as an enhancement to YUM 3. Both Fedora and Red Hat Enterprise Linux leverage transport security and package signatures to ship software to their users in a safe way.

Fedora provides a centralized, non-mirrored Fedora-run metalink service which provides a list if active mirrors and the expected cryptographic digest of the repomd.xml files. yum uses this information to select a mirror and verify that it serves the up-to-date, untampered repomd.xml. The chain of cryptographic digests is verified from there, eventually leading to verification of the .rpm file contents.

Red Hat uses a different option to distribute Red Hat Enterprise Linux and its RPM-based products: a content-distribution network, managed by a trusted third party. Furthermore, the repositories provided by Red Hat use a separate public key infrastructure which is managed by Red Hat. For further information, refer to the following articles.

[1] This content is not included.https://access.redhat.com/blogs/766093/posts/1976693

[2] https://access.redhat.com/articles/1373143

Mitigation

Avoid downloading software from untrusted third-party mirrors. Note that under normal circumstances, this flaw does not pose any threat to Red Hat users, as repositories are fully trusted and controlled by Red Hat.

Additional Information

External References

Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2020-14352

Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2020-14352

Affected Packages and Issued Red Hat Security Errata

Products / Services Components State Errata
Red Hat Enterprise Linux 7 librepo Fixed RHSA-2020:5012
Red Hat Enterprise Linux 8 librepo Fixed RHSA-2020:3658
Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions librepo Fixed RHSA-2020:3756
Red Hat Enterprise Linux 8.1 Extended Update Support librepo Fixed RHSA-2020:3749
Unless explicitly stated as not affected, all previous versions of packages in any minor update stream of a product listed here should be assumed vulnerable, although may not have been subject to full analysis.

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).

CVSS v3 Score Breakdown Red Hat NVD
CVSS v3 Base Score 8 8
Attack Vector Network Network
Attack Complexity Low Low
Privileges Required Low Low
User Interaction Required Required
Scope Unchanged Unchanged
Confidentiality Impact High High
Integrity Impact High High
Availability Impact High High

CVSS v3 Vector

Red Hat CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

NVD CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Acknowledgements

Red Hat would like to thank Sergei Iudin <siudin@fb.com> for reporting this issue.

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

 For open source software shipped by multiple vendors, the CVSS base scores may vary for each vendor's version depending on the version they ship, how they ship it, the platform, and even how the software is compiled. This makes scoring of vulnerabilities difficult for third-party vulnerability databases such as NVD that only provide a single CVSS base score for each vulnerability. Red Hat scores reflect how a vulnerability affects our products specifically.

For more information, see https://access.redhat.com/solutions/762393.

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
  • "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
  • "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.

What can I do if my product is listed as "Will not fix"?

 A "will not fix" status means that a fix for an affected product version is not planned or not possible due to complexity, which may create additional risk.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.

What can I do if my product is listed as "Fix deferred"?

 A deferred status means that a fix for an affected product version is not guaranteed due to higher-priority development work.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
  • Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.

What is a mitigation?

 A mitigation is an action that can be taken to reduce the impact of a security vulnerability, without deploying any fixes.

I have a Red Hat product but it is not in the above list, is it affected?

 The listed products were found to include one or more of the components that this vulnerability affects. These products underwent a thorough evaluation to determine their affectedness by this vulnerability. Note that layered products (such as container-based offerings) that consume affected components from any of the products listed in this table may be affected and are not represented.

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

 In order to maintain code stability and compatibility, Red Hat usually does not rebase packages to entirely new versions. Instead, we backport fixes and new features to an older version of the package we distribute. This can result in some security scanners that only consider the package version to report the package as vulnerable. To avoid this, we suggest that you use an approved vulnerability scanner from our This content is not included.Red Hat Vulnerability Scanner Certification program.