Skip to content

CWE-405: Asymmetric Resource Consumption (Amplification)

Class

The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric."

This can lead to poor performance due to "amplification" of resource consumption, typically in a non-linear fashion. This situation is worsened if the product allows malicious users or attackers to consume more resources than their access level permits.

Consequences

  • Availability: DoS: Amplification, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other)

How to prevent it

  • Architecture and Design: An application must make resources available to a client commensurate with the client's access level.
  • Architecture and Design: An application must, at all times, keep track of allocated resources and meter their usage appropriately.
  • System Configuration: Consider disabling resource-intensive algorithms on the server side, such as Diffie-Hellman key exchange.

Recent advisories

  • GHSA-4vqv-7265-gm2w — pypdf has possible large memory usage for exceptions in strict mode
  • GHSA-g3hv-75wg-m249 — minimatch has potential denial of service via globparts amplification
  • GHSA-9fm3-97px-rjf6 — undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering
  • GHSA-7hqp-7c5m-4vq6 — Microsoft Security Advisory CVE-2026-96960 - .NET and Visual Studio Denial of Service Vulnerability
  • GO-2026-6607 — Reject malformed ECH outer extension references in crypto/tls
  • GO-2026-6611 — Excessive CPU consumption from repeated initial window changes in net/http
  • GO-2026-6603 — HTTP/2 server memory exhaustion due to Trailer headers in net/http
  • GHSA-3g9q-v48f-hh9w — Open WebUI: Unauthenticated requests can stall the server via uncached OIDC fetches in back-channel logout
  • GHSA-23w6-3w8w-8484 — pypdf: Possible long runtimes/large memory usage when retrieving outlines
  • GHSA-w6m8-cqvj-pg5v — OpenClaw has incomplete Fix for CVE-2026-32011: Feishu Webhook Pre-Auth Body Parsing DoS (Slow-Body / Slowloris Variant)
  • GHSA-rm59-992w-x2mv — OpenClaw is vulnerable to unauthenticated resource exhaustion through its voice call webhook handling
  • GHSA-g2pg-6438-jwpf — devalue vulnerable to denial of service due to memory/CPU exhaustion in devalue.parse
  • GHSA-vw5p-8cq8-m7mv — Devalue is vulnerable to denial of service due to memory exhaustion in devalue.parse
  • GHSA-j3g3-5qv5-52mj — net-imap rubygem vulnerable to possible DoS by memory exhaustion
  • GHSA-mh63-6h87-95cp — jwt-go allows excessive memory allocation during header parsing

All advisories for CWE-405

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor