More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2269723 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=2269723,2269725 # 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
It looks like there is still disagreement about whether the Rust OpenSSL bindings are doing something wrong here, or if this is just an issue with OpenSSL itself. There's also no known "fix" (if there is something that *can* be fixed in the Rust bindings), so I'm going to close this as NOTABUG.
There is a workaround: use of openssl with support for implicit rejection. Since the OpenSSL in Fedora includes it, when rust-openssl is used with the default provider, rust-openssl will not be vulnerable. When it's used with other providers or ENGINEs, it still likely will.