Lucene search

[email protected]CVE-2019-16786

HistoryDec 20, 2019 - 11:15 p.m.

CVE-2019-16786

2019-12-2023:15:11

CWE-444

[email protected]

web.nvd.nist.gov

243

waitress

http

security

vulnerability

nvd

cve-2019-16786

5 Medium

CVSS2

Attack Vector

NETWORK

Attack Complexity

LOW

Authentication

NONE

Confidentiality Impact

NONE

Integrity Impact

PARTIAL

Availability Impact

NONE

AV:N/AC:L/Au:N/C:N/I:P/A:N

7.5 High

CVSS3

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

NONE

Integrity Impact

HIGH

Availability Impact

NONE

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

7.2 High

AI Score

Confidence

High

0.003 Low

EPSS

Percentile

68.2%

JSON

Waitress through version 1.3.1 would parse the Transfer-Encoding header and only look for a single string value, if that value was not chunked it would fall through and use the Content-Length header instead. According to the HTTP standard Transfer-Encoding should be a comma separated list, with the inner-most encoding first, followed by any further transfer codings, ending with chunked. Requests sent with: “Transfer-Encoding: gzip, chunked” would incorrectly get ignored, and the request would use a Content-Length header instead to determine the body size of the HTTP message. This could allow for Waitress to treat a single request as multiple requests in the case of HTTP pipelining. This issue is fixed in Waitress 1.4.0.

Affected configurations

Vulners

NVD

Node

pylonswaitressRange≤1.3.1

CPENameOperatorVersion
agendaless:waitressagendaless waitresslt1.3.1

CPE	Name	Operator	Version
agendaless:waitress	agendaless waitress	lt	1.3.1

CNA Affected

[
  {
    "product": "Waitress",
    "vendor": "Pylons",
    "versions": [
      {
        "lessThanOrEqual": "1.3.1",
        "status": "affected",
        "version": "<= 1.3.1",
        "versionType": "custom"
      }
    ]
  }
]