GSD-2020-7670

Vulnerability from gsd - Updated: 2020-10-20 00:00
Details
agoo through 2.12.3 allows request smuggling attacks where agoo is used as a backend and a frontend proxy also being vulnerable. It is possible to conduct HTTP request smuggling attacks by sending the Content-Length header twice. Furthermore, invalid Transfer Encoding headers were found to be parsed as valid which could be leveraged for TE:CL smuggling attacks.
Aliases
Aliases
CVE-2020-7670
To clipboard 

{
  "GSD": {
    "alias": "CVE-2020-7670",
    "description": "agoo prior to 2.14.0 allows request smuggling attacks where agoo is used as a backend and a frontend proxy also being vulnerable. HTTP pipelining issues and request smuggling attacks might be possible due to incorrect Content-Length and Transfer encoding header parsing. It is possible to conduct HTTP request smuggling attacks where `agoo` is used as part of a chain of backend servers due to insufficient `Content-Length` and `Transfer Encoding` parsing.",
    "id": "GSD-2020-7670"
  },
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "affected": [
        {
          "package": {
            "ecosystem": "RubyGems",
            "name": "agoo",
            "purl": "pkg:gem/agoo"
          }
        }
      ],
      "aliases": [
        "CVE-2020-7670",
        "GHSA-h385-52j6-9984"
      ],
      "details": "agoo through 2.12.3 allows request smuggling attacks where agoo is used\nas a backend and a frontend proxy also being vulnerable. It is possible to conduct\nHTTP request smuggling attacks by sending the Content-Length header twice. Furthermore,\ninvalid Transfer Encoding headers were found to be parsed as valid which could be\nleveraged for TE:CL smuggling attacks.\n",
      "id": "GSD-2020-7670",
      "modified": "2020-10-20T00:00:00.000Z",
      "published": "2020-10-20T00:00:00.000Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/ohler55/agoo/issues/88"
        },
        {
          "type": "WEB",
          "url": "https://github.com/ohler55/agoo/commit/23d03535cf7b50d679a60a953a0cae9519a4a130"
        }
      ],
      "schema_version": "1.4.0",
      "severity": [
        {
          "score": 7.5,
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTP Request Smuggling in Agoo"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "report@snyk.io",
        "ID": "CVE-2020-7670",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "agoo",
                    "version": {
                      "version_data": [
                        {
                          "version_value": "versions prior to 2.14.0"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "n/a"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "agoo prior to 2.14.0 allows request smuggling attacks where agoo is used as a backend and a frontend proxy also being vulnerable. HTTP pipelining issues and request smuggling attacks might be possible due to incorrect Content-Length and Transfer encoding header parsing. It is possible to conduct HTTP request smuggling attacks where `agoo` is used as part of a chain of backend servers due to insufficient `Content-Length` and `Transfer Encoding` parsing."
          }
        ]
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "lang": "eng",
                "value": "HTTP Request Smuggling"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://snyk.io/vuln/SNYK-RUBY-AGOO-569137",
            "refsource": "MISC",
            "url": "https://snyk.io/vuln/SNYK-RUBY-AGOO-569137"
          },
          {
            "name": "https://github.com/ohler55/agoo/issues/88",
            "refsource": "MISC",
            "url": "https://github.com/ohler55/agoo/issues/88"
          },
          {
            "name": "https://github.com/ohler55/agoo/commit/23d03535cf7b50d679a60a953a0cae9519a4a130",
            "refsource": "MISC",
            "url": "https://github.com/ohler55/agoo/commit/23d03535cf7b50d679a60a953a0cae9519a4a130"
          }
        ]
      }
    },
    "github.com/rubysec/ruby-advisory-db": {
      "cve": "2020-7670",
      "cvss_v3": 7.5,
      "date": "2020-10-20",
      "description": "agoo through 2.12.3 allows request smuggling attacks where agoo is used\nas a backend and a frontend proxy also being vulnerable. It is possible to conduct\nHTTP request smuggling attacks by sending the Content-Length header twice. Furthermore,\ninvalid Transfer Encoding headers were found to be parsed as valid which could be\nleveraged for TE:CL smuggling attacks.\n",
      "gem": "agoo",
      "ghsa": "h385-52j6-9984",
      "patched_versions": [
        "\u003e= 2.13.0"
      ],
      "related": {
        "url": [
          "https://github.com/ohler55/agoo/commit/23d03535cf7b50d679a60a953a0cae9519a4a130"
        ]
      },
      "title": "HTTP Request Smuggling in Agoo",
      "url": "https://github.com/ohler55/agoo/issues/88"
    },
    "gitlab.com": {
      "advisories": [
        {
          "affected_range": "\u003c=2.12.3",
          "affected_versions": "All versions up to 2.12.3",
          "cvss_v2": "AV:N/AC:L/Au:N/C:N/I:P/A:N",
          "cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
          "cwe_ids": [
            "CWE-1035",
            "CWE-444",
            "CWE-937"
          ],
          "date": "2020-11-17",
          "description": "agoo allows request smuggling attacks where agoo is used as a backend with a frontend proxy that is also vulnerable. It is possible to conduct HTTP request smuggling attacks by sending the `Content-Length` header twice. Furthermore, invalid `Transfer-Encoding` headers were found to be parsed as valid which could be leveraged for TE:CL smuggling attacks.",
          "fixed_versions": [
            "2.13.0"
          ],
          "identifier": "CVE-2020-7670",
          "identifiers": [
            "CVE-2020-7670"
          ],
          "not_impacted": "All versions after 2.12.3",
          "package_slug": "gem/agoo",
          "pubdate": "2020-06-10",
          "solution": "Upgrade to version 2.13.0 or above.",
          "title": "Inconsistent Interpretation of HTTP Requests (HTTP Request Smuggling)",
          "urls": [
            "https://nvd.nist.gov/vuln/detail/CVE-2020-7670"
          ],
          "uuid": "f8dff70f-1a15-4d6d-95dc-c53ee2b89c11"
        }
      ]
    },
    "nvd.nist.gov": {
      "configurations": {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "children": [],
            "cpe_match": [
              {
                "cpe23Uri": "cpe:2.3:a:ohler:agoo:*:*:*:*:*:ruby:*:*",
                "cpe_name": [],
                "versionEndIncluding": "2.12.3",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      },
      "cve": {
        "CVE_data_meta": {
          "ASSIGNER": "report@snyk.io",
          "ID": "CVE-2020-7670"
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "en",
              "value": "agoo prior to 2.14.0 allows request smuggling attacks where agoo is used as a backend and a frontend proxy also being vulnerable. HTTP pipelining issues and request smuggling attacks might be possible due to incorrect Content-Length and Transfer encoding header parsing. It is possible to conduct HTTP request smuggling attacks where `agoo` is used as part of a chain of backend servers due to insufficient `Content-Length` and `Transfer Encoding` parsing."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "en",
                  "value": "CWE-444"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://snyk.io/vuln/SNYK-RUBY-AGOO-569137",
              "refsource": "MISC",
              "tags": [
                "Third Party Advisory"
              ],
              "url": "https://snyk.io/vuln/SNYK-RUBY-AGOO-569137"
            },
            {
              "name": "https://github.com/ohler55/agoo/issues/88",
              "refsource": "MISC",
              "tags": [],
              "url": "https://github.com/ohler55/agoo/issues/88"
            },
            {
              "name": "https://github.com/ohler55/agoo/commit/23d03535cf7b50d679a60a953a0cae9519a4a130",
              "refsource": "MISC",
              "tags": [],
              "url": "https://github.com/ohler55/agoo/commit/23d03535cf7b50d679a60a953a0cae9519a4a130"
            }
          ]
        }
      },
      "impact": {
        "baseMetricV2": {
          "acInsufInfo": false,
          "cvssV2": {
            "accessComplexity": "LOW",
            "accessVector": "NETWORK",
            "authentication": "NONE",
            "availabilityImpact": "NONE",
            "baseScore": 5.0,
            "confidentialityImpact": "NONE",
            "integrityImpact": "PARTIAL",
            "vectorString": "AV:N/AC:L/Au:N/C:N/I:P/A:N",
            "version": "2.0"
          },
          "exploitabilityScore": 10.0,
          "impactScore": 2.9,
          "obtainAllPrivilege": false,
          "obtainOtherPrivilege": false,
          "obtainUserPrivilege": false,
          "severity": "MEDIUM",
          "userInteractionRequired": false
        },
        "baseMetricV3": {
          "cvssV3": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "NONE",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
            "version": "3.1"
          },
          "exploitabilityScore": 3.9,
          "impactScore": 3.6
        }
      },
      "lastModifiedDate": "2020-11-17T00:15Z",
      "publishedDate": "2020-06-10T16:15Z"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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

Loading timeline…




    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.