More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2214463 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=2214463,2214466 # 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 version of grpc packaged in all Fedora releases is 1.48.4; based on version number, it is affected by this vulnerability. EPEL9 has 1.46.7, which should also be affected. In general, grpc cannot be updated in stable releases—except for patch releases, e.g. 1.48.3 to 1.48.4—without significant fallout and an exception to the Updates Policy, because it does not offer ABI or even full API stability across minor releases. For Fedora 39/Rawhide, updating to a version of grpc that is not affected by this vulnerability is desirable, but is blocked by the transition to protobuf 4 (date-based versions 22.x, 23.x, etc, vs. 3.x). A huge number of packages will be affected by the breaking changes that entails, and it is not yet clear when that update can happen or what the impact will be. To the best of my knowledge, the version of grpc in Rawhide is the last version that can be built with protobuf 3. Therefore, an immediate fix by updating grpc to the latest version is not possible in Rawhide or in stable releases. According to the CVE, this requires upstream pull request https://github.com/grpc/grpc/pull/32309—the same one that fixes bug 2214470—as well as https://github.com/grpc/grpc/pull/33005. I plan to investigate whether or not the changes from these PR’s can be confidently backported to 1.48.4 and/or 1.46.7.
The PR https://github.com/grpc/grpc/pull/33005 is another messy backport. I don’t think I’m going to attempt it. Like bug 2214474, that means this bug will only be fixed by an eventual new version of grpc in Rawhide. https://bugzilla.redhat.com/show_bug.cgi?id=2214474#c2 > Unfortunately, that means there doesn’t appear to be much that I can do to mitigate this in the short term. I am setting the status to ASSIGNED to indicate I am tracking the issue, but please expect this issue to languish until a coordinated update of protobuf and grpc can be prepared.