cvelist/2020/7xxx/CVE-2020-7671.json

{
    "data_type": "CVE",
    "data_format": "MITRE",
    "data_version": "4.0",
    "CVE_data_meta": {
        "ID": "CVE-2020-7671",
        "ASSIGNER": "report@snyk.io",
        "STATE": "PUBLIC"
    },
    "affects": {
        "vendor": {
            "vendor_data": [
                {
                    "vendor_name": "n/a",
                    "product": {
                        "product_data": [
                            {
                                "product_name": "goliath",
                                "version": {
                                    "version_data": [
                                        {
                                            "version_value": "All versions including 1.0.6"
                                        }
                                    ]
                                }
                            }
                        ]
                    }
                }
            ]
        }
    },
    "problemtype": {
        "problemtype_data": [
            {
                "description": [
                    {
                        "lang": "eng",
                        "value": "HTTP Request Smuggling"
                    }
                ]
            }
        ]
    },
    "references": {
        "reference_data": [
            {
                "refsource": "MISC",
                "name": "https://github.com/postrank-labs/goliath/issues/351,",
                "url": "https://github.com/postrank-labs/goliath/issues/351,"
            },
            {
                "refsource": "MISC",
                "name": "https://snyk.io/vuln/SNYK-RUBY-GOLIATH-569136",
                "url": "https://snyk.io/vuln/SNYK-RUBY-GOLIATH-569136"
            }
        ]
    },
    "description": {
        "description_data": [
            {
                "lang": "eng",
                "value": "goliath through 1.0.6 allows request smuggling attacks where goliath 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."
            }
        ]
    }
}