Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1593776 - (CVE-2018-10868) CVE-2018-10868 redhat-certification: billion laugh attack when getting the status of a host
CVE-2018-10868 redhat-certification: billion laugh attack when getting the st...
Status: NEW
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=20180621,repor...
: Security
Depends On: 1608786
Blocks: 1593614
  Show dependency treegraph
 
Reported: 2018-06-21 10:48 EDT by Riccardo Schirone
Modified: 2018-08-30 03:32 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
It has been discovered that redhat-certification does not properly limit the number of recursive definitions of entities in XML documents while parsing the status of a host. A remote attacker could use this vulnerability to consume all the memory of the server and cause a Denial of Service.
Story Points: ---
Clone Of:
Environment:
Last Closed:
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 Riccardo Schirone 2018-06-21 10:48:29 EDT
redhat-certification does not properly restrict the number of recursive definitions of entities in XML documents, allowing an unauthenticated user to run a "Billion Laugh Attack"[1] by replying to XMLRPC methods when getting the status of an host.

[1] https://en.wikipedia.org/wiki/Billion_laughs_attack
Comment 1 Riccardo Schirone 2018-06-21 10:48:38 EDT
Acknowledgments:

Name: Riccardo Schirone (Red Hat Product Security)
Comment 3 Riccardo Schirone 2018-06-25 09:12:26 EDT
getHostStatus in view.py connects to an XMLRPC server provided by the user, who could setup a fake server and reply with a small XML file which, when parsed, uses a big amount of memory.

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