More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2278918 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=2278918,2278920 # 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
The release notes at https://github.com/protocolbuffers/protobuf/releases/tag/v25.0 report that the bug was introduced in 4.22.0 and was fixed with https://github.com/protocolbuffers/protobuf/commit/b955165ebdcc5a8ba9c267230d6305f4e3d9c118 in 4.25.0 and up. Since the protobuf package in Fedora is (unfortunately) still at 3.6.1 due to the large effort required to bring all of its dependent packages along, it should be unaffected by this *particular* issue. Any future update, e.g. https://src.fedoraproject.org/rpms/protobuf/pull-request/28, will be to a version recent enough that it is also unaffected.