Scantide
  MITRE CWE, explained by Scantide

Software weaknesses, explained simply

CWE names recurring weakness types found in software and devices; it is not a list of individual vulnerabilities. Scantide keeps the MITRE terminology visible, then explains what each weakness means and shows familiar, non-operational examples of what it can look like in a real product.

Scantide does not hide the technical detail. The attention labels below are a presentation aid: headline signals deserve immediate attention, important signals deserve review, and technical detail remains available without being allowed to drown out the stronger signals. A specific CVE can still make a normally secondary CWE much more serious.
984CWE records in local generation
51headline signals
316important signals
617technical-detail signals
Headline signalImportantTechnical detailCWE generation 20261112T072920Z-b834b5ede09d

CWE-400 · Uncontrolled Resource Consumption

The product can consume or manage resources in a way that is not sufficiently bounded.

Technical detail

In plain English

The product can consume or manage resources in a way that is not sufficiently bounded.

What this can look like

Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.

A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.

The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.

MITRE description from the synchronized CWE record

The product does not properly control the allocation and maintenance of a limited resource.

Examples are intentionally conceptual. They explain the security consequence without providing exploit payloads or step-by-step attack instructions. MITRE remains the authoritative source for the CWE definition and mapping guidance.