[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[SECURITY] [DLA 1400-1] tomcat7 security update



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Package        : tomcat7
Version        : 7.0.56-3+really7.0.88-1
CVE ID         : CVE-2017-7674 CVE-2017-12616 CVE-2018-1304
                 CVE-2018-1305 CVE-2018-8014
Debian Bug     : 802312 898935

Several security vulnerabilities have been discovered in the Tomcat
servlet and JSP engine.

CVE-2017-7674
    The CORS Filter in Apache Tomcat did not add an HTTP Vary header
    indicating that the response varies depending on Origin. This
    permitted client and server side cache poisoning in some
    circumstances.

CVE-2017-12616
    When using a VirtualDirContext with Apache Tomcat it was possible to
    bypass security constraints and/or view the source code of JSPs for
    resources served by the VirtualDirContext using a specially crafted
    request.

CVE-2018-1304
    The URL pattern of "" (the empty string) which exactly maps to the
    context root was not correctly handled in Apache Tomcat when used as
    part of a security constraint definition. This caused the constraint
    to be ignored. It was, therefore, possible for unauthorized users to
    gain access to web application resources that should have been
    protected. Only security constraints with a URL pattern of the empty
    string were affected.

CVE-2018-1305
    Security constraints defined by annotations of Servlets in Apache
    Tomcat were only applied once a Servlet had been loaded. Because
    security constraints defined in this way apply to the URL pattern
    and any URLs below that point, it was possible - depending on the
    order Servlets were loaded - for some security constraints not to be
    applied. This could have exposed resources to users who were not
    authorized to access them.

CVE-2018-8014
    The defaults settings for the CORS filter provided in Apache Tomcat
    are insecure and enable 'supportsCredentials' for all origins. It is
    expected that users of the CORS filter will have configured it
    appropriately for their environment rather than using it in the
    default configuration. Therefore, it is expected that most users
    will not be impacted by this issue.

For Debian 8 "Jessie", these problems have been fixed in version
7.0.56-3+really7.0.88-1.

We recommend that you upgrade your tomcat7 packages.

Further information about Debian LTS security advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://wiki.debian.org/LTS
-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlsz+fVfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQACgkQ2a0UuVE7
UeT6jxAAsF5TiQnsgH/TnHogViax1TVv2VNKPFnyr2Qfsf+jJPMHiS0QjRd7Tq36
gOelP+5glunm5YkWrawp7SDBZxD6g9sGWn6CMBx5Z8CdGeB1acA2YeJShJkf8meW
vXFXbFqI8d64lXR6WIv3LmltbJPH6NRfVYdgY3+/pFBoz1AIYPY9kIQS7WWWetFj
NWXjg8S9PpqI/12yNDW4JgY/2/95bz15iaFq6LHnpVxg7dZOynJ9+gW6lvuv5OUk
nemqiCodn8okr6xpHencbcIpdYOqcMEPm9ZqAAQNRnHJvHexAM6Mb4XUjXy+//8S
xYFBPdRYAlJorB2/+U35Rf0AmEzKcill1ncFvmMV2wDs0ffGDC8HYwc0N8lsxOLG
egp16Epggtju8hCIkF6HRTHWXfDc/b2KbAKbYkJ/AU1MDlwDgTRLobTiDtLzsyS8
dFO5FTXwFlIUOM2+XFc7mcXzMAJBL/WDOs0QvE9kXFnKYweIx9GvA5Thdh2qH4wq
FB+3ok58Qwl5/13ObTjGnfNsVjtI4k6x7/QvX9s+zBlKK/BwkeCTN1bNHO8J1lBn
CuRpOQdbQM/DJEjQb/7M569Hvb/LVg38zE8Ze+C2C2R4O1sWpi6Tz9oATdofogws
60EakU+vnAagdvDAuySrZRv4fwMBrKhF9asTg/t6l9yAb6NAa0k=
=Fyo9
-----END PGP SIGNATURE-----


Reply to: