CyberRota Analysis
AI-GeneratedThe vulnerability affects aiosend versions prior to 3.0.7, where the `WebhookHandler.feed_update()` method improperly deserializes the entire request body before HMAC signature verification. This flaw allows unauthenticated attackers to exploit the system by sending large JSON payloads, resulting in excessive CPU and memory consumption. Organizations using aiosend for Crypto Pay API integrations should prioritize upgrading to version 3.0.7 or implementing recommended workarounds to mitigate potential denial-of-service risks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
aiosend is a synchronous and asynchronous Crypto Pay API client. Pror to version 3.0.7, `WebhookHandler.feed_update()` deserializes the entire request body before verifying the HMAC signature. This allows an unauthenticated attacker to force expensive parsing of arbitrary JSON payloads that will ultimately be rejected, leading to unnecessary CPU and memory consumption. Version 3.0.7 fixes the issue. Some workarounds are available. Restrict request body size at the reverse proxy or web framework, rate-limit webhook endpoints, and/or reject oversized requests before JSON parsing.