Relative Path Traversal in Babel 2.9.0 allows an attacker to load arbitrary locale files on disk and execute arbitrary code. Reference: https://www.tenable.com/security/research/tra-2021-14 Upstream patch: https://github.com/python-babel/babel/pull/782
Created babel tracking bugs for this issue: Affects: fedora-all [bug 1955725]
External References: https://www.tenable.com/security/research/tra-2021-14
An application that uses `babel.Locale` to create a new Locale object with an untrusted language argument might be vulnerable to this flaw. The babel library uses the language argument to retrieve a file on disk, however it does not perform any check to ensure that the language is a well formed name and that it does not contain special path characters (e.g. `..`). The locale files are essentially dumps of pickle, thus an attacker who can create a file on the system and trick an application to use that file as a babel Locale can easily execute arbitrary code on the vulnerable system.
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 7 Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS Via RHSA-2021:3252 https://access.redhat.com/errata/RHSA-2021:3252
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 7 Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS Via RHSA-2021:3254 https://access.redhat.com/errata/RHSA-2021:3254
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2021-20095
*** Bug 2016686 has been marked as a duplicate of this bug. ***
Note: this CVE ID was rejected by MITRE, and CVE-2021-42771 used instead to track this issue. Since Red Hat has already shipped errata referencing CVE-2021-20095, we continue to use this ID and instead mark CVE-2021-42771 as duplicate for our purposes. Both identifiers reference the same issue and carry the same analysis results, so the net result in terms of affected & fixed products is the same.
Adding the new CVE-2021-42771 here as well, while keeping the original CVE-2021-20095 listed here as well, as it was already used in released errata.
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2021:4151 https://access.redhat.com/errata/RHSA-2021:4151
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2021:4162 https://access.redhat.com/errata/RHSA-2021:4162
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2021:4201 https://access.redhat.com/errata/RHSA-2021:4201