More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2248982 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=low # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2248982,2248983 # 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
Upstream says: "Some of our earliest chips like ESP32 revision < ECO3 had support for secure boot and flash encryption schemes based on AES ECB modes. Recently we have migrated to more standard algorithms like RSA-3072, ECDSA for secure boot (v2) and AES-XTS for flash encryption. In summary, the code you pointed is specific to some of our older chip revisions and their security features. We plan to continue supporting them in our tools.", hence closing.