Skip to content
OpenAdvisories

Weakness (CWE)

CWE-400: Uncontrolled Resource Consumption

Class Draft Mapping discouraged

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

How to prevent it (4 mitigations)

  1. Architecture and Design

    Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.

  2. Architecture and Design

    Mitigation of resource exhaustion attacks requires that the target system either:

    - recognizes the attack and denies that user further access for a given amount of time, or

    - uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.

    The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.

    The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.

  3. Architecture and Design

    Ensure that protocols have specific limits of scale placed on them.

  4. Implementation

    Ensure that all failures in resource allocation place the system into a safe posture.

Source: MITRE CWE-400

All Critical High Medium Low Exploited only Public exploit

1,732 results · Clear filters · Feed

  • Medium —
    CVE-2009-0033 EPSS 10%

    Apache Tomcat Denial of Service via Malformed Request Headers

    Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when the Java AJP connector and mod_jk load balancing are used, allows remote attackers to cause a denial of service (application outage) via a crafted request with invalid he…

    org.apache.tomcat:tomcat Maven
  • Medium 5.9
    CVE-2007-5712

    Django vulnerable to Denial of Service via i18n middleware component

    The internationalization (i18n) framework in Django 0.91, 0.95, 0.95.1, and 0.96, and as used in other products such as PyLucid, when the USE_I18N option and the i18n component are enabled, allows remote attackers to cause a denial of service (memory consumpt…

    python-django django Debian PyPI
  • Medium 5.5
    CVE-2006-5649

    Unspecified vulnerability in the "alignment check exception handling" in Ubuntu 5.10, 6.06 LTS, and 6.10 for the PowerP…

  • Medium 5.5
    CVE-2006-5648

    Ubuntu Linux 6.10 for the PowerPC (PPC) allows local users to cause a denial of service (resource consumption) by using…

  • Medium 6.5
    CVE-2006-6017

    WordPress before 2.0.5 does not properly store a profile containing a string representation of a serialized object, whi…

    wordpress Debian
  • Medium —
    CVE-2004-2650

    Apache James Denial of Service

    Spooler in Apache Foundation James 2.2.0 allows local users to cause a denial of service (memory consumption) by triggering various error conditions in the retrieve function, which prevents a lock from being released and causes a memory leak.

    org.apache.james:james-server Maven
  • Medium —
    CVE-2004-2381

    Jetty HTTP Server Denial of Service vulnerability

    HttpRequest.java in Jetty HTTP Server before 4.2.19 allows remote attackers to cause denial of service (memory usage and application crash) via HTTP requests with a large Content-Length.

    org.mortbay.jetty:jetty Maven
  • Medium 5.9
    CVE-2004-1464 Exploited

    Cisco IOS 12.2(15) and earlier allows remote attackers to cause a denial of service (refused VTY (virtual terminal) con…

    KEV May 19, 2023
  • Medium —
    CVE-2003-0045

    Jakarta Tomcat Denial of Service vulnerability

    Jakarta Tomcat before 3.3.1a on certain Windows systems may allow remote attackers to cause a denial of service (thread hang and resource consumption) via a request for a JSP page containing an MS-DOS device name, such as aux.jsp.

    org.apache.tomcat:tomcat Maven
  • Medium —
    CVE-2003-0866 Public exploit EPSS 35%

    Apache Tomcat Denial of Service vulnerability in the Catalina package

    The Catalina org.apache.catalina.connector.http package in Tomcat 4.0.x up to 4.0.3 allows remote attackers to cause a denial of service via several requests that do not follow the HTTP protocol, which causes Tomcat to reject later requests.

    org.apache.tomcat:tomcat Maven
  • Medium —
    CVE-2002-0935

    Apache Tomcat DoS Via Requests Including Null Characters

    Apache Tomcat 4.0.3, and possibly other versions before 4.1.3 beta, allows remote attackers to cause a denial of service (resource exhaustion) via a large number of requests to the server with null characters, which causes the working threads to hang.

    org.apache.tomcat:tomcat Maven
  • Medium —
    CVE-2002-0687

    Zope Server vulnerable to DoS via header injection

    The "through the web code" capability for Zope 2.0 through 2.5.1 b1 allows untrusted users to shut down the Zope server via certain headers.

    zope PyPI