Elevation of privilege results from giving an attacker authorization permissions beyond those initially granted. For example, an attacker with a privilege set of "read only" permissions somehow elevates the set to include "read and write."
Trusted STS Should Sign SAML Token Claims
A Security Assertions Markup Language (SAML) token is a generic XML token that is the default type for issued tokens. A SAML token can be constructed by a Security Token Service (STS) that the end Web service trusts in a typical exchange. SAML tokens contain claims in statements. An attacker may copy the claims from a valid token, create a new SAML token, and sign it with a different issuer. The intent is to determine whether the server is validating issuers and, if not, utilize the weakness to construct SAML tokens that allow privileges beyond those intended by a trusted STS.
The SamlAssertion class verifies the digital signature contained within a SAML token, and the default SamlSecurityTokenAuthenticator requires that SAML tokens be signed by an X.509 certificate that is valid when the CertificateValidationMode of the IssuedTokenServiceCredential class is set to ChainTrust.
ChainTrust mode alone is insufficient to determine whether the issuer of the SAML token is trusted. Services that require a more granular trust model can either use authorization and enforcement policies to check the issuer of the claim sets produced by issued token authentication or use the X.509 validation settings on IssuedTokenServiceCredential to restrict the set of allowed signing certificates. For more information, see Managing Claims and Authorization with the Identity Model and Federation and Issued Tokens.
Switching Identity Without a Security Context
The following applies only to WinFX.
When a connection is established between a client and server, the identity of the client does not change, except in one situation: after the WCF client is opened, if all of the following conditions are true:
The procedures to establish a security context (using a transport security session or message security session) is switched off (EstablishSecurityContext property is set to
falsein case of message security or transport not capable of establishing security sessions is used in transport security case. HTTPS is one example of such transport).
You are using Windows authentication.
You do not explicitly set the credential.
You are calling the service under the impersonated security context.
If these conditions are true, the identity used to authenticate the client to the service might change (it might not be the impersonated identity but the process identity instead) after the WCF client is opened. This occurs because the Windows credential used to authenticate the client to the service is transmitted with every message, and the credential used for authentication is obtained from the current thread's Windows identity. If the Windows identity of the current thread changes (for example, by impersonating a different caller), the credential that is attached to the message and used to authenticate the client to the service might also change.
If you want to have deterministic behavior when using Windows authentication together with impersonation you need to explicitly set the Windows credential or you need to establish a security context with the service. To do this, use a message security session or a transport security session. For example, the net.tcp transport can provide a transport security session. Additionally, you must use only a synchronous version of client operations when calling the service. If you establish a message security context, you should not keep the connection to the service open longer than the configured session renewal period, because the identity can also change during the session renewal process.
The following applies to .NET Framework version 3.5, and subsequent versions.
Credentials used by the client or the service are based on the current context thread. The credentials are obtained when the
Open method (or
BeginOpen, for asynchronous calls) of the client or service is called. For both the ServiceHost and ClientBase<TChannel> classes, the
BeginOpen methods inherit from the Open and BeginOpen methods of the CommunicationObject class.
When using the
BeginOpen method, the credentials captured cannot be guaranteed to be the credentials of the process that calls the method.
Token Caches Allow Replay Using Obsolete Data
WCF uses the local security authority (LSA)
LogonUser function to authenticate users by user name and password. Because the logon function is a costly operation, WCF allows you to cache tokens that represent authenticated users to increase performance. The caching mechanism saves the results from
LogonUser for subsequent uses. This mechanism is disabled by default; to enable it, set the CacheLogonTokens property to
true, or use the
cacheLogonTokens attribute of the <userNameAuthentication>.
You can set a Time to Live (TTL) for the cached tokens by setting the CachedLogonTokenLifetime property to a TimeSpan, or use the
cachedLogonTokenLifetime attribute of the
userNameAuthentication element; the default is 15 minutes. Note that while a token is cached, any client that presents the same user name and password can use the token, even if the user account is deleted from Windows or if its password has been changed. Until the TTL expires and the token is removed from the cache, WCF allows the (possibly malicious) user to authenticate.
To mitigate this: Decrease the attack window by setting the
cachedLogonTokenLifetime value to the shortest time span your users need.
Issued Token Authorization: Expiration Reset to Large Value
This occurs when using the WSFederationHttpBinding and any of the system-provided bindings that have an issued token as the client credential type.
This also occurs when you create custom bindings by using one of the following methods:
To mitigate this, the authorization policy must check the action and the expiration time of each authorization policy.
The Service Uses a Different Certificate Than the Client Intended
Under certain conditions, a client can digitally sign a message with an X.509 certificate and have the service retrieve a different certificate than the intended one.
This can occur under the following circumstances:
The client digitally signs a message using an X.509 certificate and does not attach the X.509 certificate to the message, but rather just references the certificate using its subject key identifier.
The service's computer contains two or more certificates with the same public key, but they contain different information.
The service retrieves a certificate that matches the subject key identifier, but it is not the one the client intended to use. When WCF receives the message and verifies the signature, WCF maps the information in the unintended X.509 certificate to a set of claims that are different and potentially elevated from what the client expected.
To mitigate this, reference the X.509 certificate another way, such as using IssuerSerial.