More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2282114 Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # low, medium, high, urgent (required) severity=medium # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2282114,2282160 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
We don't call the requests library in our code directly. Also, we don't ship any Python code in the RPMs, Python is only used to build the artifacts, so Python code is only present in SRPMs. No HTTP connections are established during the build process. The request library is just looked for by CMake because it's a dependency of the compliance-trestle (https://github.com/oscal-compass/compliance-trestle). The compliance-trestle is a optional dependency of our code and isn't used when building Fedora artifacts. Therefore, I conclude that there is no action that we could do on our side.