austintoddj/canvas is vulnerable to Server-Side Request Forgery (SSRF)
30
CVE Score
Low
Server-Side Request Forgery (SSRF)
Canvas validates a webhook URL's hostname by resolving it once and checking that every A and AAAA address is public, then delivers the webhook through a separate HTTP client call that resolves the same hostname again independently. A hostname under externally controlled DNS can resolve to a public address during validation and to a private or internal address during delivery, letting the outbound webhook request reach internal network targets. The fix resolves both A and AAAA records up front, rejects any private or mixed resolution, and pins the delivery connection to the validated address with CURLOPT_RESOLVE while enforcing HTTPS and failing closed when curl pinning is unavailable.
Upgrade the austintoddj/canvas library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you use Canvas's webhook delivery feature.
7.0.0 - 7.1.0
Fixed in 7.1.1austintoddj/canvas is vulnerable to Server-Side Request Forgery (SSRF) in versions 7.0.0 - 7.1.0.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.