critical
9
Advisory Published
Updated

CVE-2021-22112

First published: Tue Feb 23 2021(Updated: )

Spring Security 5.4.x prior to 5.4.4, 5.3.x prior to 5.3.8.RELEASE, 5.2.x prior to 5.2.9.RELEASE, and older unsupported versions can fail to save the SecurityContext if it is changed more than once in a single request.A malicious user cannot cause the bug to happen (it must be programmed in). However, if the application's intent is to only allow the user to run with elevated privileges in a small portion of the application, the bug can be leveraged to extend those privileges to the rest of the application.

Credit: security@vmware.com

Affected SoftwareAffected VersionHow to fix
Pivotal Software Spring Security<5.2.9
Pivotal Software Spring Security>=5.3.0<5.3.8
Vmware Spring Security>=5.4.0<5.4.4
Oracle Communications Element Manager>=8.2.0<=8.2.4.0
Oracle Communications Interactive Session Recorder=6.3
Oracle Communications Interactive Session Recorder=6.4
Oracle Communications Unified Inventory Management=7.4.1
Oracle Hospitality Cruise Shipboard Property Management System=20.1.0
Oracle Insurance Policy Administration=11.2.0
Oracle Insurance Policy Administration=11.3.0
Oracle Mysql Enterprise Monitor<=8.0.25

Remedy

https://lists.apache.org/thread.html/r2cb05e499807900ba23e539643eead9c5f0652fd271f223f89da1804@%3Cpluto-scm.portals.apache.org%3E

Remedy

https://www.oracle.com/security-alerts/cpuApr2021.html

Remedy

https://www.oracle.com/security-alerts/cpuoct2021.html

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the vulnerability ID?

    The vulnerability ID is CVE-2021-22112.

  • What is the severity of CVE-2021-22112?

    The severity of CVE-2021-22112 is critical.

  • Which versions of Spring Security are affected by CVE-2021-22112?

    Spring Security 5.4.x prior to 5.4.4, 5.3.x prior to 5.3.8.RELEASE, and 5.2.x prior to 5.2.9.RELEASE are affected.

  • How can the SecurityContext be saved in Spring Security?

    The SecurityContext can be saved using the `SecurityContextHolder.setContext()` method.

  • How can I fix CVE-2021-22112 in Spring Security?

    To fix CVE-2021-22112, upgrade to Spring Security 5.4.4, 5.3.8.RELEASE, or 5.2.9.RELEASE.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203