Bug 2256953 (CVE-2023-7217)

Summary: CVE-2023-7217 libebml: integer overflow may lead to crash
Product: [Other] Security Response Reporter: Marian Rehak <mrehak>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: security-response-team
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
An integer overflow vulnerability was found in libebml. The function MemIOCallback::read at line 70 does not restrict the integer size, which could potentially lead to a crash.
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-02-16 12:56:07 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: 2258047, 2258048, 2263140, 2263141    
Bug Blocks:    

Description Marian Rehak 2024-01-05 15:09:30 UTC
Function MemIOCallback::read at line 70 has an integer overflow, which may lead to crash.

Comment 1 Marian Rehak 2024-02-07 07:19:46 UTC
Created libebml tracking bugs for this issue:

Affects: epel-all [bug 2263141]
Affects: fedora-all [bug 2263140]

Comment 2 Dominik 'Rathann' Mierzejewski 2024-02-07 09:16:41 UTC
Isn't this a duplicate of CVE-2023-52339 (bug 2258046) ?
It's difficult to say with certainty because there's little details, though.
If it's the same then it's already fixed, too.

Comment 3 Dominik 'Rathann' Mierzejewski 2024-02-07 09:20:35 UTC
CVE-2023-52339 is already publicized while this one isn't even visible over at NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-7217 .

Comment 4 Marian Rehak 2024-02-16 12:53:53 UTC
Hello Dominik, you are correct. This is a duplicate and I will close it as such. Thank you for letting me know!

Comment 5 Marian Rehak 2024-02-16 12:56:07 UTC

*** This bug has been marked as a duplicate of bug 2258046 ***