Missing authorization in Amazon amazon-connect-salesforce-lambda before 5.26 allows any IAM principal with lambda:InvokeFunction permission on the affected function to escalate privileges and perform AWS API operations that their own IAM identity is explicitly denied, via invocation of a Lambda function that dispatches caller-supplied parameters to privileged service APIs without authorization validation. To remediate this issue, we recommend upgrading to version 5.26 or later. After setup is complete, either delete or disable the sfExecuteAWSService function.
If you retain the function, restrict invocation to the intended IAM user only.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
Low
Partial data leak
Integrity
Low
Partial data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
References 3
https://aws.amazon.com/security/security-bulletins/2026-115-aws/
ff89ba41-3aa1-4d27-914a-91399e9639e5
https://github.com/amazon-connect/amazon-connect-salesforce-cti/security/adviso…
ff89ba41-3aa1-4d27-914a-91399e9639e5
https://github.com/amazon-connect/amazon-connect-salesforce-lambda/releases/tag…
ff89ba41-3aa1-4d27-914a-91399e9639e5