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

{
    "data_type": "CVE",
    "data_format": "MITRE",
    "data_version": "4.0",
    "CVE_data_meta": {
        "ASSIGNER": "report@snyk.io",
        "DATE_PUBLIC": "2020-07-27T11:23:53.870794Z",
        "ID": "CVE-2020-7695",
        "STATE": "PUBLIC",
        "TITLE": "HTTP Response Splitting"
    },
    "affects": {
        "vendor": {
            "vendor_data": [
                {
                    "product": {
                        "product_data": [
                            {
                                "product_name": "uvicorn",
                                "version": {
                                    "version_data": [
                                        {
                                            "version_affected": ">=",
                                            "version_value": "0"
                                        }
                                    ]
                                }
                            }
                        ]
                    },
                    "vendor_name": "n/a"
                }
            ]
        }
    },
    "problemtype": {
        "problemtype_data": [
            {
                "description": [
                    {
                        "lang": "eng",
                        "value": "HTTP Response Splitting"
                    }
                ]
            }
        ]
    },
    "references": {
        "reference_data": [
            {
                "refsource": "CONFIRM",
                "url": "https://snyk.io/vuln/SNYK-PYTHON-UVICORN-570471"
            },
            {
                "refsource": "CONFIRM",
                "url": "https://github.com/encode/uvicorn"
            }
        ]
    },
    "description": {
        "description_data": [
            {
                "lang": "eng",
                "value": "This affects all versions of package uvicorn.\n Uvicorn's implementation of the HTTP protocol for the httptools parser is vulnerable to HTTP response splitting. CRLF sequences are not escaped in the value of HTTP headers. Attackers can exploit this to add arbitrary headers to HTTP responses, or even return an arbitrary response body, whenever crafted input is used to construct HTTP headers.\r\n\r\n"
            }
        ]
    },
    "impact": {
        "cvss": {
            "version": "3.1",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:P/RL:U/RC:C",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "attackVector": "NETWORK",
            "attackComplexity": "LOW",
            "privilegesRequired": "NONE",
            "userInteraction": "NONE",
            "scope": "UNCHANGED",
            "confidentialityImpact": "NONE",
            "integrityImpact": "LOW",
            "availabilityImpact": "NONE"
        }
    },
    "credit": [
        {
            "lang": "eng",
            "value": "Everardo Padilla Saca"
        }
    ]
}