Bug 2512101 - CVE-2026-58102 perl-Crypt-OpenSSL-X509: Crypt::OpenSSL::X509: Information disclosure due to heap out-of-bounds read. [fedora-all]
Summary: CVE-2026-58102 perl-Crypt-OpenSSL-X509: Crypt::OpenSSL::X509: Information dis...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Crypt-OpenSSL-X509
Version: 45
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Xavier Bachelot
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["cd96b651-8c70-4b43-93ea-9...
Depends On:
Blocks: CVE-2026-58102
TreeView+ depends on / blocked
 
Reported: 2026-08-06 15:09 UTC by Vladimir Vasilev
Modified: 2026-08-20 11:18 UTC (History)
3 users (show)

Fixed In Version: perl-Crypt-OpenSSL-X509-2.1.3-1.fc43
Clone Of:
Environment:
Last Closed: 2026-08-20 11:18:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vladimir Vasilev 2026-08-06 15:09:32 UTC
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.

Crypt::OpenSSL::X509 versions before 2.1.3 for Perl allow a heap out-of-bounds read via a long certificate extension OID in hv_exts.

When building the extension hash (via extensions(), extensions_by_long_name(), extensions_by_oid(), or has_extension_oid()), the code passes OBJ_obj2txt()'s return value as the hash-key length; because that value is the OID's full text length rather than the bytes written to the fixed-size buffer (129 bytes), an OID whose text is longer than the 129-byte buffer causes a read past the allocation, exposing adjacent heap memory as the returned hash key. extensions_by_name() uses the static shortname path and is not affected.

Comment 1 Aoife Moloney 2026-08-17 15:48:37 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle.
Changing version to 45.


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