Skip to content
Fencer Intel
medium 5.0

CVE-2014-0180 json

The wait_for_task function in app/controllers/application_controller.rb in Red Hat CloudForms 3.0 Management Engine (CFME) before 5.2.4.2 a…

published 2014-07-07 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-0232

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

The wait_for_task function in app/controllers/application_controller.rb in Red Hat CloudForms 3.0 Management Engine (CFME) before 5.2.4.2 allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via unspecified vectors.

Patch / fix

  • cfme cloudforms managementengine 5 5.2.4.2-1.el6cf
  • cfme-lib cloudforms managementengine 5 5.2.4.2-1.el6cf
  • cfme-appliance cloudforms managementengine 5 5.2.4.2-1.el6cf
  • mingw32-cfme-host cloudforms managementengine 5 5.2.4.2-1.el6cf
  • ruby193-rubygem-actionpack cloudforms managementengine 5 1:3.2.13-8.el6cf

red hat advisories RHSA-2014:0816

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-0180 updated cvss 5.0

CFME: app/controllers/application_controller.rb wait_for_task DoS

  • Red Hat Management Engine cfme 5.2.4.2-1.el6cf, cfme-lib 5.2.4.2-1.el6cf, cfme-appliance 5.2.4.2-1.el6cf, mingw32-cfme-host 5.2.4.2-1.el6cf, ruby193-rubygem-actionpack 3.2.13-8.el6cf
    fixed: vendor fix RHSA-2014:0816

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.83% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-399 Resource Management Errors

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.