RHSA-2020:3329

Vulnerability from csaf_redhat - Published: 2020-08-05 14:47 - Updated: 2026-06-26 22:26
Summary
Red Hat Security Advisory: Red Hat Ansible Tower 3.6.5-1 - RHEL7 Container
Severity
Moderate
Notes
Topic: Red Hat Ansible Tower 3.6.5-1 - RHEL7 Container
Details: * Removed reports option for Satellite inventory script * Fixed Tower Server Side Request Forgery on Credentials (CVE-2020-14327) * Fixed the ``Job Type`` field to render properly when editing a Job Template * Fixed a notable delay running large project update clones * Fixed Tower to properly sync host facts for Red Hat Satellite 6.7 inventories * Fixed installations on Red Hat OpenShift 4.3 to no longer fail * Fixed the usage of certain SSH keys on RHEL8 when FIPS is enabled to work properly * Fixed upgrades from 3.5 to 3.6 on RHEL8 in order for PostgreSQL client libraries to be upgraded on Tower nodes, which fixes the backup/restore function * Fixed credential lookups from CyberArk AIM to no longer fail unexpectedly * Fixed the ability to add a user to an organization when they already had roles in the organization * Fixed manually added host variables to no longer be removed on VMWare vCenter inventory syncs * Fixed a number of issues related to Tower’s reporting of metrics to Red Hat Automation Analytics
Terms of Use: This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Red Hat Inc. and provide a link to the original.

A Server-side request forgery (SSRF) flaw was found in Tower. Functionality on the Tower server is abused by supplying a URL that could lead to the server processing it. This flaw leads to the connection to internal services or the exposure of additional internal services by abusing the test feature of lookup credentials to forge HTTP/HTTPS requests from the server and retrieving the results of the response.

CWE-918 - Server-Side Request Forgery (SSRF)
Affected products
Product Identifier Version Remediation
Unresolved product id: 7Server-Ansible-Tower-3.6:ansible-tower-36/ansible-tower@sha256:d014f851f25ea1fea8ca4f0a7ee0f5cca0334856d1ecd96e0ad49c7ab6510fd6_amd64 —
Vendor Fix fix
Threats
Impact Moderate

{
  "document": {
    "aggregate_severity": {
      "namespace": "https://access.redhat.com/security/updates/classification/",
      "text": "Moderate"
    },
    "category": "csaf_security_advisory",
    "csaf_version": "2.0",
    "distribution": {
      "text": "Copyright \u00a9 Red Hat, Inc. All rights reserved.",
      "tlp": {
        "label": "WHITE",
        "url": "https://www.first.org/tlp/"
      }
    },
    "lang": "en",
    "notes": [
      {
        "category": "summary",
        "text": "Red Hat Ansible Tower 3.6.5-1 - RHEL7 Container",
        "title": "Topic"
      },
      {
        "category": "general",
        "text": "* Removed reports option for Satellite inventory script\n* Fixed Tower Server Side Request Forgery on Credentials (CVE-2020-14327)\n* Fixed the ``Job Type`` field to render properly when editing a Job Template\n* Fixed a notable delay running large project update clones\n* Fixed Tower to properly sync host facts for Red Hat Satellite 6.7 inventories\n* Fixed installations on Red Hat OpenShift 4.3 to no longer fail\n* Fixed the usage of certain SSH keys on RHEL8 when FIPS is enabled to work properly\n* Fixed upgrades from 3.5 to 3.6 on RHEL8 in order for PostgreSQL client libraries to be upgraded on Tower nodes, which fixes the backup/restore function\n* Fixed credential lookups from CyberArk AIM to no longer fail unexpectedly\n* Fixed the ability to add a user to an organization when they already had roles in the organization\n* Fixed manually added host variables to no longer be removed on VMWare vCenter inventory syncs\n* Fixed a number of issues related to Tower\u2019s reporting of metrics to Red Hat Automation Analytics",
        "title": "Details"
      },
      {
        "category": "legal_disclaimer",
        "text": "This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Red Hat Inc. and provide a link to the original.",
        "title": "Terms of Use"
      }
    ],
    "publisher": {
      "category": "vendor",
      "contact_details": "https://access.redhat.com/security/team/contact/",
      "issuing_authority": "Red Hat Product Security is responsible for vulnerability handling across all Red Hat products and services.",
      "name": "Red Hat Product Security",
      "namespace": "https://www.redhat.com"
    },
    "references": [
      {
        "category": "self",
        "summary": "https://access.redhat.com/errata/RHSA-2020:3329",
        "url": "https://access.redhat.com/errata/RHSA-2020:3329"
      },
      {
        "category": "external",
        "summary": "https://access.redhat.com/security/updates/classification/#moderate",
        "url": "https://access.redhat.com/security/updates/classification/#moderate"
      },
      {
        "category": "external",
        "summary": "1856785",
        "url": "https://bugzilla.redhat.com/show_bug.cgi?id=1856785"
      },
      {
        "category": "self",
        "summary": "Canonical URL",
        "url": "https://security.access.redhat.com/data/csaf/v2/advisories/2020/rhsa-2020_3329.json"
      }
    ],
    "title": "Red Hat Security Advisory: Red Hat Ansible Tower 3.6.5-1 - RHEL7 Container",
    "tracking": {
      "current_release_date": "2026-06-26T22:26:26+00:00",
      "generator": {
        "date": "2026-06-26T22:26:26+00:00",
        "engine": {
          "name": "Red Hat SDEngine",
          "version": "5.2.6"
        }
      },
      "id": "RHSA-2020:3329",
      "initial_release_date": "2020-08-05T14:47:44+00:00",
      "revision_history": [
        {
          "date": "2020-08-05T14:47:44+00:00",
          "number": "1",
          "summary": "Initial version"
        },
        {
          "date": "2020-08-05T14:47:44+00:00",
          "number": "2",
          "summary": "Last updated version"
        },
        {
          "date": "2026-06-26T22:26:26+00:00",
          "number": "3",
          "summary": "Last generated version"
        }
      ],
      "status": "final",
      "version": "3"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_name",
                "name": "Red Hat Ansible Tower 3.6 for RHEL 7",
                "product": {
                  "name": "Red Hat Ansible Tower 3.6 for RHEL 7",
                  "product_id": "7Server-Ansible-Tower-3.6",
                  "product_identification_helper": {
                    "cpe": "cpe:/a:redhat:ansible_tower:3.6::el7"
                  }
                }
              }
            ],
            "category": "product_family",
            "name": "Red Hat Ansible Tower"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "ansible-tower-36/ansible-tower@sha256:d014f851f25ea1fea8ca4f0a7ee0f5cca0334856d1ecd96e0ad49c7ab6510fd6_amd64",
                "product": {
                  "name": "ansible-tower-36/ansible-tower@sha256:d014f851f25ea1fea8ca4f0a7ee0f5cca0334856d1ecd96e0ad49c7ab6510fd6_amd64",
                  "product_id": "ansible-tower-36/ansible-tower@sha256:d014f851f25ea1fea8ca4f0a7ee0f5cca0334856d1ecd96e0ad49c7ab6510fd6_amd64",
                  "product_identification_helper": {
                    "purl": "pkg:oci/ansible-tower@sha256:d014f851f25ea1fea8ca4f0a7ee0f5cca0334856d1ecd96e0ad49c7ab6510fd6?arch=amd64\u0026repository_url=registry.redhat.io/ansible-tower-36/ansible-tower\u0026tag=3.6.5-1"
                  }
                }
              }
            ],
            "category": "architecture",
            "name": "amd64"
          }
        ],
        "category": "vendor",
        "name": "Red Hat"
      }
    ],
    "relationships": [
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "ansible-tower-36/ansible-tower@sha256:d014f851f25ea1fea8ca4f0a7ee0f5cca0334856d1ecd96e0ad49c7ab6510fd6_amd64 as a component of Red Hat Ansible Tower 3.6 for RHEL 7",
          "product_id": "7Server-Ansible-Tower-3.6:ansible-tower-36/ansible-tower@sha256:d014f851f25ea1fea8ca4f0a7ee0f5cca0334856d1ecd96e0ad49c7ab6510fd6_amd64"
        },
        "product_reference": "ansible-tower-36/ansible-tower@sha256:d014f851f25ea1fea8ca4f0a7ee0f5cca0334856d1ecd96e0ad49c7ab6510fd6_amd64",
        "relates_to_product_reference": "7Server-Ansible-Tower-3.6"
      }
    ]
  },
  "vulnerabilities": [
    {
      "acknowledgments": [
        {
          "names": [
            "Maxime ESCOURBIAC"
          ],
          "organization": "Michelin CERT team"
        }
      ],
      "cve": "CVE-2020-14327",
      "cwe": {
        "id": "CWE-918",
        "name": "Server-Side Request Forgery (SSRF)"
      },
      "discovery_date": "2020-07-06T00:00:00+00:00",
      "ids": [
        {
          "system_name": "Red Hat Bugzilla ID",
          "text": "1856785"
        }
      ],
      "notes": [
        {
          "category": "description",
          "text": "A Server-side request forgery (SSRF) flaw was found in Tower. Functionality on the Tower server is abused by supplying a URL that could lead to the server processing it. This flaw leads to the connection to internal services or the exposure of additional internal services by abusing the test feature of lookup credentials to forge HTTP/HTTPS requests from the server and retrieving the results of the response.",
          "title": "Vulnerability description"
        },
        {
          "category": "summary",
          "text": "Tower: SSRF: Server Side Request Forgery on Credential",
          "title": "Vulnerability summary"
        },
        {
          "category": "other",
          "text": "Ansible Tower 3.7.1 and 3.6.4 as well as previous versions are affected.",
          "title": "Statement"
        },
        {
          "category": "general",
          "text": "The CVSS score(s) listed for this vulnerability do not reflect the associated product\u0027s status, and are included for informational purposes to better understand the severity of this vulnerability.",
          "title": "CVSS score applicability"
        }
      ],
      "product_status": {
        "fixed": [
          "7Server-Ansible-Tower-3.6:ansible-tower-36/ansible-tower@sha256:d014f851f25ea1fea8ca4f0a7ee0f5cca0334856d1ecd96e0ad49c7ab6510fd6_amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://access.redhat.com/security/cve/CVE-2020-14327"
        },
        {
          "category": "external",
          "summary": "RHBZ#1856785",
          "url": "https://bugzilla.redhat.com/show_bug.cgi?id=1856785"
        },
        {
          "category": "external",
          "summary": "https://www.cve.org/CVERecord?id=CVE-2020-14327",
          "url": "https://www.cve.org/CVERecord?id=CVE-2020-14327"
        },
        {
          "category": "external",
          "summary": "https://nvd.nist.gov/vuln/detail/CVE-2020-14327",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2020-14327"
        }
      ],
      "release_date": "2020-07-14T00:00:00+00:00",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2020-08-05T14:47:44+00:00",
          "details": "For information on upgrading Ansible Tower, reference the Ansible Tower Upgrade and Migration Guide: https://docs.ansible.com/ansible-tower/latest/html/upgrade-migration-guide/index.html",
          "product_ids": [
            "7Server-Ansible-Tower-3.6:ansible-tower-36/ansible-tower@sha256:d014f851f25ea1fea8ca4f0a7ee0f5cca0334856d1ecd96e0ad49c7ab6510fd6_amd64"
          ],
          "restart_required": {
            "category": "none"
          },
          "url": "https://access.redhat.com/errata/RHSA-2020:3329"
        }
      ],
      "scores": [
        {
          "cvss_v3": {
            "attackComplexity": "LOW",
            "attackVector": "LOCAL",
            "availabilityImpact": "NONE",
            "baseScore": 5.5,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "NONE",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
            "version": "3.1"
          },
          "products": [
            "7Server-Ansible-Tower-3.6:ansible-tower-36/ansible-tower@sha256:d014f851f25ea1fea8ca4f0a7ee0f5cca0334856d1ecd96e0ad49c7ab6510fd6_amd64"
          ]
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Moderate"
        }
      ],
      "title": "Tower: SSRF: Server Side Request Forgery on Credential"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.