Bug 989755 - (CVE-2013-4180) CVE-2013-4180 Foreman: hosts_controller.rb power/ipmi_boot Symbol creation DoS
CVE-2013-4180 Foreman: hosts_controller.rb power/ipmi_boot Symbol creation DoS
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20130903,reported=2...
: Security
Depends On: 995307 994835 994836 995306
Blocks: 989761
  Show dependency treegraph
 
Reported: 2013-07-29 16:45 EDT by Kurt Seifried
Modified: 2016-04-26 18:10 EDT (History)
17 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-05-20 01:24:03 EDT
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 Kurt Seifried 2013-07-29 16:45:35 EDT
Marek Hulan (mhulan@redhat.com) reports:

I found a DoS bug in foreman. The problem is in converting a user input into a 
symbol. Since MRI garbage collector does not free any instantiated symbol any 
authenticated user can create inputs to consume all system memory. Memory 
consumption is linear (input size = consumed memory amount) and every input 
must be unique. Since the input comes from HTTP request via method PUT it's 
not hard to send large portion of data at a time. Basically an attacker is 
just limited by HTTP protocol and server configuration.
Comment 1 Marek Hulan 2013-07-31 09:00:24 EDT
http://projects.theforeman.org/issues/2860
Comment 5 Murray McAllister 2013-09-02 10:56:26 EDT
Acknowledgements:

This issue was discovered by Marek Hulán of the Red Hat Foreman team.
Comment 7 errata-xmlrpc 2013-09-03 16:26:10 EDT
This issue has been addressed in following products:

  OpenStack 3 for RHEL 6

Via RHSA-2013:1196 https://rhn.redhat.com/errata/RHSA-2013-1196.html

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