Bug 1923211 - libgcrypt: Heap buffer overflow in in the block buffer management code [fedora-all]
Summary: libgcrypt: Heap buffer overflow in in the block buffer management code [fedor...
Keywords:
Status: CLOSED DUPLICATE of bug 1923267
Alias: None
Product: Fedora
Classification: Fedora
Component: libgcrypt
Version: 33
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
Assignee: Jakub Jelen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-01 15:09 UTC by Pedro Sampaio
Modified: 2021-02-08 12:11 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-02-02 16:13:03 UTC
Type: ---
Embargoed:
fedora-admin-xmlrpc: mirror+


Attachments (Terms of Use)

Description Pedro Sampaio 2021-02-01 15:09:11 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

Comment 1 Jakub Jelen 2021-02-02 16:13:03 UTC
I already closed the bug #1923267 which was filled from the tracking bug #1923210. Did your tool go wild or whats up?

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

Comment 2 Pedro Sampaio 2021-02-08 12:11:01 UTC
(In reply to Jakub Jelen from comment #1)
> I already closed the bug #1923267 which was filled from the tracking bug
> #1923210. Did your tool go wild or whats up?
> 
> *** This bug has been marked as a duplicate of bug 1923267 ***

Might have been some connection issue between the tools and their backends. Sometimes happen. Sorry about that.


Note You need to log in before you can comment on or make changes to this bug.