Bug 1517316 (CVE-2017-16932) - CVE-2017-16932 libxml2: Infinite recursion in parameter entities
Summary: CVE-2017-16932 libxml2: Infinite recursion in parameter entities
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2017-16932
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1517317 1517318 1517319 1517320 1517321 1517322 1517342 1517343 1517352 1517353 1517354 1517355
Blocks: 1517325
TreeView+ depends on / blocked
 
Reported: 2017-11-24 15:31 UTC by Adam Mariš
Modified: 2021-12-14 18:47 UTC (History)
43 users (show)

Fixed In Version: libxml2 2.9.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-21 11:58:03 UTC
Embargoed:


Attachments (Terms of Use)

Description Adam Mariš 2017-11-24 15:31:58 UTC
parser.c in libxml2 before 2.9.5 does not prevent infinite recursion in parameter entities.

Upstream patch:

https://github.com/GNOME/libxml2/commit/899a5d9f0ed13b8e32449a08a361e0de127dd961

Comment 1 Adam Mariš 2017-11-24 15:32:51 UTC
Created libxml2 tracking bugs for this issue:

Affects: fedora-all [bug 1517320]


Created mingw-libxml2 tracking bugs for this issue:

Affects: epel-7 [bug 1517318]
Affects: fedora-all [bug 1517321]


Created ruby193-rubygem-nokogiri tracking bugs for this issue:

Affects: openshift-1 [bug 1517322]


Created rubygem-nokogiri tracking bugs for this issue:

Affects: epel-all [bug 1517317]
Affects: fedora-all [bug 1517319]

Comment 11 Kurt Seifried 2018-03-22 20:13:25 UTC
Statement:

This issue affects the versions of rubygem-nokogiri as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

This issue affects the versions of libxml2 as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

This issue affects the versions of rubygem-nokogiri on CloudForms 5 as it uses the Red Hat Enterprise copy of libxml2 as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

This issue affects the versions of rubygem-nokogiri on Satellite 6.0, 6.1 and 6.2  as it uses the Red Hat Enterprise copy of libxml2 as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Please note that Satellite version 6.3 no longer ships rubygem-nokogir, but instead uses a version of rubygem-nokogiri from another software channel.

Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.

Red Hat Enterprise Linux 6 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.


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