|Description||Security constraints defined by annotations of Servlets in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 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 authorised to access them.|
|Source||CVE (at NVD; CERT, LWN, oss-sec, fulldisc, bugtraq, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, Mageia, GitHub code/issues, web search, more)|
|References||DLA-1301-1, DLA-1400-1, DLA-1450-1, DSA-4281-1|
Vulnerable and fixed packages
The table below lists information on source packages.
|tomcat9 (PTS)||buster, buster (security)||9.0.31-1~deb10u6||fixed|
|bullseye (security), bullseye||9.0.43-2~deb11u3||fixed|
The information below is based on the following data on fixed versions.
- tomcat9 <not-affected> (Fixed before initial upload to Debian)
tomcat8.0 builds only tomcat8.0-user and libtomcat8.0-java
Since 7.0.72-3, src:tomcat7 only builds the Servlet API