Bug 2347313

Summary: CVE-2025-0838 abseil-cpp: Heap Buffer overflow in Abseil [epel-9]
Product: [Fedora] Fedora EPEL Reporter: Michal Findra <mfindra>
Component: abseil-cppAssignee: Rich Mattes <richmattes>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: epel9CC: code, richmattes
Target Milestone: ---Keywords: Reopened, Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["84a57c2d-4c22-465f-9892-c00ecf404c54"]}
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-03-10 23:38:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2346987    

Description Michal Findra 2025-02-24 14:27:07 UTC 
More information about this security flaw is available in the following bug:

https://bugzilla.redhat.com/show_bug.cgi?id=2346987

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.
Comment 1 Ben Beasley 2025-02-24 15:52:50 UTC 
In my opinion, the fix for this CVE can’t be backported as a patch with high confidence and a reasonable amount of effort. The fix https://github.com/abseil/abseil-cpp/commit/5a0e2cb5e3958dd90bb8569a2766622cb74d90c1 is not especially self-contained, and the code to which it applies has changed quite a bit since the version 20211102.0 that is packaged in EPEL9.

Updating to a newer release would be an ABI-breaking update requireing https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/#process_for_incompatible_upgrades and could be disruptive to the packages that depend on abseil-cpp in EPEL9: bloaty, fastnetmon, grpc, ilbc, libarrow, and mozc.

It might be possible to do something about this if someone is determined enough, but I won’t be that person.