Authenticated forged webhook acceptance via untrusted certificates
Published May 26, 2023 · Updated Jan 14, 2025
Improper signature verification in django-ses before 3.5.0 allows remote authenticated users to submit forged SES/SNS webhook events. EventMessageVerifier accepts a SigningCertURL under any amazonaws.com subdomain, downloads that attacker-chosen certificate, and trusts it to verify the request signature. The default trusted-domain setting is exposed when SESEventWebhookView is routed; accepted events can reach application handlers or trigger blind SSRF.
Summary
What happened
Improper signature verification in django-ses before 3.5.0 allows remote authenticated users to submit forged SES/SNS webhook events. EventMessageVerifier accepts a SigningCertURL under any amazonaws.com subdomain, downloads that attacker-chosen certificate, and trusts it to verify the request signature. The default trusted-domain setting is exposed when SESEventWebhookView is routed; accepted events can reach application handlers or trigger blind SSRF.
The record
- CVE
- CVE-2023-33185
- Published
- May 26, 2023
- Updated
- Jan 14, 2025
- Vendor
- django-ses
- Product
- django-ses
- Classifications
- CWE-347, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2023CVE publishedPublication date reported by the CVE source.
- Jan 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Certificate URL signature verification proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo