Spring Security
  1. Spring Security
  2. SEC-1750

AbstractSecurityInterceptor should replace the SecurityContext when doing RunAs replacement, rather than just the Authentication within the context

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0.6, 3.0.5, 3.1.0.RC2
    • Fix Version/s: 3.0.6, 3.1.0.RC3, 2.0.7
    • Component/s: Core
    • Labels:
      None

      Description

      Since the SecurityContext may be shared between different threads, there is a limited possibility of escalating permissions when a RunAsManager is used to modify the context.

        Activity

        Hide
        Luke Taylor added a comment -

        Default RunAsManager now creates an empty security context to hold the runas authentication token.

        Show
        Luke Taylor added a comment - Default RunAsManager now creates an empty security context to hold the runas authentication token.

          People

          • Assignee:
            Luke Taylor
            Reporter:
            Luke Taylor
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: