Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1564940 - (CVE-2018-1000164) CVE-2018-1000164 python-gunicorn: Improper neutralization of CRLF Sequences http/wsgi.py:process_headers() can allow an attacker to cause a server to return arbitrary HTTP headers
CVE-2018-1000164 python-gunicorn: Improper neutralization of CRLF Sequences h...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20160317,repor...
: Security
Depends On: 1567003 1564941
Blocks: 1564943
  Show dependency treegraph
 
Reported: 2018-04-08 21:33 EDT by Sam Fowler
Modified: 2018-04-16 10:03 EDT (History)
18 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Fowler 2018-04-08 21:33:28 EDT
python-gunicorn before version 19.5.0 has a HTTP response splitting vulnerability in the http/wsgi.py:process_headers() function caused by the improper neutralization of CRLF sequences. An attacker could exploit this to cause a server to return arbitrary HTTP headers.


External References:

https://epadillas.github.io/2018/04/02/http-header-splitting-in-gunicorn-19.4.5


Upstream Issue:

https://github.com/benoitc/gunicorn/issues/1227


Upstream Patch:

https://github.com/benoitc/gunicorn/commit/5263a4ef2a63c62216680876f3813959839608ff
Comment 1 Sam Fowler 2018-04-08 21:33:59 EDT
Created python-gunicorn tracking bugs for this issue:

Affects: epel-6 [bug 1564941]
Comment 2 Joshua Padman 2018-04-09 02:07:06 EDT
The version shipped with OpenStack 12 is 19.7.1 and contains the latest fixes.

Note You need to log in before you can comment on or make changes to this bug.