SQ34403
Detected presence of active webhook service access keys.
priority | CI/CD status | severity | effort | RL level | RL assessment |
---|---|---|---|---|---|
fail | high | medium | 2 | secrets: fail Reason: active web service credentials |
About the issueโ
Software as a Service (SaaS) platforms expose programmable interfaces for action automation and secure exchange of information. Webhooks are web callback interfaces that enable real-time event notifications. Applications provide a public-facing interface that the web service calls when a specific event occurs. Authentication is done by the application that the web service accesses through a secret key. Since the key is encoded in the webhook callback, the service interface parameters should never be included in a software release package, even if they are obfuscated by encryption on the client-side. For supported web services, webhooks are automatically validated via the least privilege APIs the service exposes. Detected webhooks have been accepted as valid by the services they are associated with. This indicates they are currently active and may be abused if exposed to the public.
How to resolve the issueโ
- If webhook keys were published unintentionally and the software has been made public, you should revoke the exposed webhook secrets and file a security incident.
- Examples of webhook secrets that may have been detected include AWS, Slack, Office365 and others.
Incidence statisticsโ
Not relevant for this type of sensitive information.
Recommended readingโ
What is a webhook? (External resource - RedHat)
Introduction to Webhook security (External resource - webhooks.fyi)