GSD-2020-7659

Vulnerability from gsd - Updated: 2021-05-24 00:00
Details
reel through 0.6.1 allows Request Smuggling attacks due to incorrect Content-Length and Transfer encoding header parsing. 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 TECL smuggling attacks. Note, This project is deprecated, and is not maintained any more.
Aliases

{
  "GSD": {
    "alias": "CVE-2020-7659",
    "description": "reel through 0.6.1 allows Request Smuggling attacks due to incorrect Content-Length and Transfer encoding header parsing. 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. Note: This project is deprecated, and is not maintained any more.",
    "id": "GSD-2020-7659"
  },
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "affected": [
        {
          "package": {
            "ecosystem": "RubyGems",
            "name": "reel",
            "purl": "pkg:gem/reel"
          }
        }
      ],
      "aliases": [
        "CVE-2020-7659",
        "GHSA-x3v4-pxvm-63j8"
      ],
      "details": "reel through 0.6.1 allows Request Smuggling attacks due to incorrect\nContent-Length and Transfer encoding header parsing. It is possible to conduct HTTP\nrequest 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 TECL smuggling attacks. Note, This project is deprecated, and is not\nmaintained any more.\n",
      "id": "GSD-2020-7659",
      "modified": "2021-05-24T00:00:00.000Z",
      "published": "2021-05-24T00:00:00.000Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/advisories/GHSA-x3v4-pxvm-63j8"
        }
      ],
      "schema_version": "1.4.0",
      "severity": [
        {
          "score": 7.5,
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTP Request Smuggling in reel"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "report@snyk.io",
        "ID": "CVE-2020-7659",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "reel",
                    "version": {
                      "version_data": [
                        {
                          "version_value": "All versions including 0.6.1"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "n/a"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "reel through 0.6.1 allows Request Smuggling attacks due to incorrect Content-Length and Transfer encoding header parsing. 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. Note: This project is deprecated, and is not maintained any more."
          }
        ]
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "lang": "eng",
                "value": "HTTP Request Smuggling"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://snyk.io/vuln/SNYK-RUBY-REEL-569135",
            "refsource": "MISC",
            "url": "https://snyk.io/vuln/SNYK-RUBY-REEL-569135"
          }
        ]
      }
    },
    "github.com/rubysec/ruby-advisory-db": {
      "cve": "2020-7659",
      "cvss_v3": 7.5,
      "date": "2021-05-24",
      "description": "reel through 0.6.1 allows Request Smuggling attacks due to incorrect\nContent-Length and Transfer encoding header parsing. It is possible to conduct HTTP\nrequest 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 TECL smuggling attacks. Note, This project is deprecated, and is not\nmaintained any more.\n",
      "gem": "reel",
      "ghsa": "x3v4-pxvm-63j8",
      "title": "HTTP Request Smuggling in reel",
      "url": "https://github.com/advisories/GHSA-x3v4-pxvm-63j8"
    },
    "gitlab.com": {
      "advisories": [
        {
          "affected_range": "\u003c=0.6.1",
          "affected_versions": "All versions up to 0.6.1",
          "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-06-02",
          "description": "reel allows Request Smuggling attacks due to incorrect `Content-Length` and `Transfer-Encoding` header parsing. 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": [],
          "identifier": "CVE-2020-7659",
          "identifiers": [
            "CVE-2020-7659"
          ],
          "not_impacted": "",
          "package_slug": "gem/reel",
          "pubdate": "2020-06-01",
          "solution": "Unfortunately, there is no solution available as this project has been deprecated.",
          "title": "Inconsistent Interpretation of HTTP Requests (HTTP Request Smuggling)",
          "urls": [
            "https://nvd.nist.gov/vuln/detail/CVE-2020-7659"
          ],
          "uuid": "8ac3757d-acd2-4bd3-9d44-4e3d5562bdc4"
        }
      ]
    },
    "nvd.nist.gov": {
      "configurations": {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "children": [],
            "cpe_match": [
              {
                "cpe23Uri": "cpe:2.3:a:celluloid:reel:*:*:*:*:*:*:*:*",
                "cpe_name": [],
                "versionEndIncluding": "0.6.1",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      },
      "cve": {
        "CVE_data_meta": {
          "ASSIGNER": "report@snyk.io",
          "ID": "CVE-2020-7659"
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "en",
              "value": "reel through 0.6.1 allows Request Smuggling attacks due to incorrect Content-Length and Transfer encoding header parsing. 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. Note: This project is deprecated, and is not maintained any more."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "en",
                  "value": "CWE-444"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://snyk.io/vuln/SNYK-RUBY-REEL-569135",
              "refsource": "MISC",
              "tags": [
                "Third Party Advisory"
              ],
              "url": "https://snyk.io/vuln/SNYK-RUBY-REEL-569135"
            }
          ]
        }
      },
      "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-06-02T17:01Z",
      "publishedDate": "2020-06-01T13:15Z"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…