Skip to content
Fencer Vulns
high 7.1

CVE-2020-14296 json

Red Hat CloudForms 4.7 and 5 was vulnerable to Server-Side Request Forgery (SSRF) flaw.

published 2020-08-11 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-6449

cvss
7.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 51%
public exploits
0
none known

Summary

Red Hat CloudForms 4.7 and 5 was vulnerable to Server-Side Request Forgery (SSRF) flaw. With the access to add Ansible Tower provider, an attacker could scan and attack systems from the internal network which are not normally accessible.

Patch / fix

  • cfme cloudforms managementengine 5.11 5.11.7.3-1.el8cf
  • cfme-gemset cloudforms managementengine 5.11 5.11.7.3-1.el8cf

red hat advisories RHSA-2020:3358

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-2020-14296 updated cvss 6.8

CloudForms: Server-Side Request Forgery (SSRF) in Ansible Tower Provider

  • Red Hat CloudForms Management Engine 5.11 cfme 5.11.7.3-1.el8cf
    fixed: vendor fix RHSA-2020:3358
  • Red Hat CloudForms Management Engine 5.11 cfme-gemset 5.11.7.3-1.el8cf, cfme-appliance 5.11.7.3-1.el8cf, v2v-conversion-host 1.16.2-3.el8ev, cfme-appliance-tools 5.11.7.3-1.el8cf, cfme-appliance-common 5.11.7.3-1.el8cf, cfme-amazon-smartstate 5.11.7.3-1.el8cf, +1 more
    not affected: vulnerable code not present

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

0.64% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
NVD 2.0 5.5 AV:N/AC:L/Au:S/C:P/I:P/A:N

Affected products

  • n/a CloudForms

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Vulns 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.