Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1397731 - (CVE-2015-8978) CVE-2015-8978 perl-SOAP-Lite: XML exponential entity expansion denial-of-service
CVE-2015-8978 perl-SOAP-Lite: XML exponential entity expansion denial-of-service
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20150721,repor...
: Security
Depends On: 1397732
Blocks: 1397735
  Show dependency treegraph
 
Reported: 2016-11-23 04:40 EST by Andrej Nemec
Modified: 2016-12-14 02:15 EST (History)
13 users (show)

See Also:
Fixed In Version: perl-SOAP-Lite 1.15
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-12-14 02:15:19 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrej Nemec 2016-11-23 04:40:57 EST
In Soap Lite (aka the SOAP::Lite extension for Perl) 1.14 and earlier,
an example attack consists of defining 10 or more XML entities, each
defined as consisting of 10 of the previous entity, with the document
consisting of a single instance of the largest entity, which expands to
one billion copies of the first entity. The amount of computer memory
used for handling an external SOAP call would likely exceed that
available to the process parsing the XML.

References:

http://cpansearch.perl.org/src/PHRED/SOAP-Lite-1.20/Changes
Comment 1 Andrej Nemec 2016-11-23 04:42:29 EST
Created perl-SOAP-Lite tracking bugs for this issue:

Affects: epel-all [bug 1397732]
Comment 3 Doran Moppert 2016-12-14 02:09:16 EST
Statement:

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/.

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