When using the CAS Proxy ticket authentication from Spring Security 3.1 to
3.2.4 a malicious CAS Service could trick another CAS Service into
authenticating a proxy ticket that was not associated. This is due to the
fact that the proxy ticket authentication uses the information from the
HttpServletRequest which is populated based upon untrusted information
within the HTTP request. This means if there are access control
restrictions on which CAS services can authenticate to one another, those
restrictions can be bypassed. If users are not using CAS Proxy tickets and
not basing access control decisions based upon the CAS Service, then there
is no impact to users.
 sbeattie> java-spring-security 3.x only?
Ubuntu 12.04 ESM (Precise Pangolin):DNE (precise was needs-triage)
Ubuntu 14.04 LTS (Trusty Tahr):needs-triage
Ubuntu 16.04 LTS (Xenial Xerus):DNE
Ubuntu 18.04 LTS (Bionic Beaver):DNE
Ubuntu 18.10 (Cosmic Cuttlefish):DNE
Ubuntu 19.04 (Disco Dingo):DNE
More Information

Updated: 2019-01-14 21:15:36 UTC (commit 51f9b73af244ba86b9321e46e526586c25a8e060)