Sap Cloud Security Services Integration Library
Monthly
Token trust-source confusion in SAP's cloud-security-services-integration-library lets the HybridTokenAuthenticator component accept identity tokens minted by an IAS/XSUAA service binding that was never intended as the application's trust source, resulting in unauthorized access at limited confidentiality and integrity impact (CVSS 3.1 base 4.2, CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N, no availability impact). Only deployments bound to multiple IAS/XSUAA service instances are exposed: an 'ambient' binding must exist for the flaw to trigger, and remote attackers must already hold a valid token issued by that ambient binding before they can authenticate, so single-binding SAP BTP Cloud Foundry applications are not affected. There is no public exploit identified at time of analysis, and all available signals point to a genuinely low-priority issue rather than an urgent one.
Token trust-source confusion in SAP's cloud-security-services-integration-library lets the HybridTokenAuthenticator component accept identity tokens minted by an IAS/XSUAA service binding that was never intended as the application's trust source, resulting in unauthorized access at limited confidentiality and integrity impact (CVSS 3.1 base 4.2, CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N, no availability impact). Only deployments bound to multiple IAS/XSUAA service instances are exposed: an 'ambient' binding must exist for the flaw to trigger, and remote attackers must already hold a valid token issued by that ambient binding before they can authenticate, so single-binding SAP BTP Cloud Foundry applications are not affected. There is no public exploit identified at time of analysis, and all available signals point to a genuinely low-priority issue rather than an urgent one.