Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1397484 - (CVE-2016-6816) CVE-2016-6816 tomcat: HTTP Request smuggling vulnerability due to permitting invalid character in HTTP requests
CVE-2016-6816 tomcat: HTTP Request smuggling vulnerability due to permitting ...
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=20161122,repor...
: Security
Depends On: 1397493 1397495 1397496 1398253 1398254 1399014 1399016 1402662 1402663 1402664 1402665
Blocks: 1397488 1397645 1428325 1482229
  Show dependency tree / graph
 
Reported: 2016-11-22 10:56 EST by Adam Mariš
Modified: 2018-10-19 17:38 EDT (History)
71 users (show)

See Also:
Fixed In Version: tomcat 6.0.48, tomcat 7.0.73, tomcat 8.0.39, tomcat 8.5.8
Doc Type: If docs needed, set a value
Doc Text:
It was discovered that the code that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other then their own.
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)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:0244 normal SHIPPED_LIVE Important: Red Hat JBoss Enterprise Application Platform security update 2017-02-02 20:39:38 EST
Red Hat Product Errata RHSA-2017:0245 normal SHIPPED_LIVE Important: Red Hat JBoss Enterprise Application Platform security update 2017-02-02 20:36:51 EST
Red Hat Product Errata RHSA-2017:0246 normal SHIPPED_LIVE Important: Red Hat JBoss Enterprise Application Platform security update 2017-02-02 20:33:58 EST
Red Hat Product Errata RHSA-2017:0247 normal SHIPPED_LIVE Moderate: Red Hat JBoss Enterprise Application Platform security update 2017-05-02 21:58:19 EDT
Red Hat Product Errata RHSA-2017:0250 normal SHIPPED_LIVE Important: jboss-ec2-eap security, bug fix, and enhancement update 2017-02-02 21:03:53 EST
Red Hat Product Errata RHSA-2017:0455 normal SHIPPED_LIVE Important: Red Hat JBoss Web Server 3.1.0 security and enhancement update 2017-03-07 19:06:40 EST
Red Hat Product Errata RHSA-2017:0456 normal SHIPPED_LIVE Important: Red Hat JBoss Web Server 3.1.0 security and enhancement update 2017-03-07 19:06:06 EST
Red Hat Product Errata RHSA-2017:0457 normal SHIPPED_LIVE Important: Red Hat JBoss Web Server security and enhancement update 2017-03-07 19:05:59 EST
Red Hat Product Errata RHSA-2017:0527 normal SHIPPED_LIVE Moderate: tomcat6 security update 2017-03-15 13:01:42 EDT
Red Hat Product Errata RHSA-2017:0935 normal SHIPPED_LIVE Moderate: tomcat security update 2017-04-12 15:02:18 EDT

  None (edit)
Description Adam Mariš 2016-11-22 10:56:38 EST 
The code that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack and/or obtain sensitive information from requests other then their own.

Affects: 6.0.0 to 6.0.47, 7.0.0 to 7.0.72, 8.0.0.RC1 to 8.0.38, 8.5.0 to 8.5.6

Upstream patches:

Tomcat 6.0.48: https://svn.apache.org/viewvc?view=rev&rev=1767683
Tomcat 7.0.73: http://svn.apache.org/viewvc?view=rev&rev=1767675
Tomcat 8.0.39: http://svn.apache.org/viewvc?view=rev&rev=1767653
Tomcat 8.5.8: http://svn.apache.org/viewvc?view=rev&rev=1767645

External References:

https://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.48
https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.73
https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.39
https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.8
https://access.redhat.com/solutions/2891171
https://access.redhat.com/articles/2991951
Comment 2 Adam Mariš 2016-11-22 11:09:57 EST 
Created tomcat tracking bugs for this issue:

Affects: fedora-all [bug 1397493]
Affects: epel-6 [bug 1397495]
Comment 10 Coty Sutherland 2017-01-24 15:30:07 EST 
For the record, this fix has been getting some negative responses in the community from users because of the amount of clients that use curly braces ({ and }) and the pipe symbol (|) in their requests without encoding them. Doing so will result in a 400 response after this patch is applied. Additionally, there is no workaround to change the behavior back; see https://bz.apache.org/bugzilla/show_bug.cgi?id=60594 for information on an RFE to add an optional setting.
Comment 11 errata-xmlrpc 2017-02-02 15:24:07 EST 
This issue has been addressed in the following products:

   Red Hat JBoss Enterprise Application Platform 6

Via RHSA-2017:0247 https://rhn.redhat.com/errata/RHSA-2017-0247.html
Comment 12 errata-xmlrpc 2017-02-02 15:44:51 EST 
This issue has been addressed in the following products:

  Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 5

Via RHSA-2017:0246 https://rhn.redhat.com/errata/RHSA-2017-0246.html
Comment 13 errata-xmlrpc 2017-02-02 15:46:03 EST 
This issue has been addressed in the following products:

  Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 7

Via RHSA-2017:0245 https://rhn.redhat.com/errata/RHSA-2017-0245.html
Comment 14 errata-xmlrpc 2017-02-02 15:47:10 EST 
This issue has been addressed in the following products:

  Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6

Via RHSA-2017:0244 https://rhn.redhat.com/errata/RHSA-2017-0244.html
Comment 15 errata-xmlrpc 2017-02-02 16:04:42 EST 
This issue has been addressed in the following products:

  Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6

Via RHSA-2017:0250 https://rhn.redhat.com/errata/RHSA-2017-0250.html
Comment 16 Timothy Walsh 2017-02-12 23:09:56 EST 
Statement:

Applying the fix provided to mitigate this issue may cause Tomcat to return 400 status after updating. For more information, refer to https://access.redhat.com/solutions/2891171
Comment 18 errata-xmlrpc 2017-03-07 14:10:22 EST 
This issue has been addressed in the following products:

  Red Hat JBoss Web Server 3.1.0

Via RHSA-2017:0457 https://rhn.redhat.com/errata/RHSA-2017-0457.html
Comment 19 errata-xmlrpc 2017-03-07 14:14:57 EST 
This issue has been addressed in the following products:

  Red Hat JBoss Web Server 3 for RHEL 7

Via RHSA-2017:0456 https://access.redhat.com/errata/RHSA-2017:0456
Comment 20 errata-xmlrpc 2017-03-07 14:19:27 EST 
This issue has been addressed in the following products:

  Red Hat JBoss Web Server 3 for RHEL 6

Via RHSA-2017:0455 https://access.redhat.com/errata/RHSA-2017:0455
Comment 21 errata-xmlrpc 2017-03-15 09:02:11 EDT 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6

Via RHSA-2017:0527 https://rhn.redhat.com/errata/RHSA-2017-0527.html
Comment 24 errata-xmlrpc 2017-04-12 11:04:06 EDT 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2017:0935 https://access.redhat.com/errata/RHSA-2017:0935
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.