CWE-400
DiscouragedUncontrolled Resource Consumption
Abstraction: Class · Status: Draft
The product does not properly control the allocation and maintenance of a limited resource.
6465 vulnerabilities reference this CWE, most recent first.
GHSA-53QW-Q765-4FWW
Vulnerability from github – Published: 2022-01-12 19:20 – Updated: 2024-09-20 16:04An issue was discovered in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1. UserAttributeSimilarityValidator incurred significant overhead in evaluating a submitted password that was artificially large in relation to the comparison values. In a situation where access to user registration was unrestricted, this provided a potential vector for a denial-of-service attack.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "Django"
},
"ranges": [
{
"events": [
{
"introduced": "2.2a1"
},
{
"fixed": "2.2.26"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "PyPI",
"name": "Django"
},
"ranges": [
{
"events": [
{
"introduced": "3.2a1"
},
{
"fixed": "3.2.11"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "PyPI",
"name": "Django"
},
"ranges": [
{
"events": [
{
"introduced": "4.0a1"
},
{
"fixed": "4.0.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-45115"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2022-01-12T19:18:33Z",
"nvd_published_at": "2022-01-05T00:15:00Z",
"severity": "HIGH"
},
"details": "An issue was discovered in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1. `UserAttributeSimilarityValidator` incurred significant overhead in evaluating a submitted password that was artificially large in relation to the comparison values. In a situation where access to user registration was unrestricted, this provided a potential vector for a denial-of-service attack.",
"id": "GHSA-53qw-q765-4fww",
"modified": "2024-09-20T16:04:22Z",
"published": "2022-01-12T19:20:53Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-45115"
},
{
"type": "WEB",
"url": "https://github.com/django/django/commit/2135637fdd5ce994de110affef9e67dffdf77277"
},
{
"type": "WEB",
"url": "https://github.com/django/django/commit/a8b32fe13bcaed1c0b772fdc53de84abc224fb20"
},
{
"type": "WEB",
"url": "https://github.com/django/django/commit/df79ef03ac867c93caaa6be56bc69e66abfeef8f"
},
{
"type": "WEB",
"url": "https://docs.djangoproject.com/en/4.0/releases/security"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-53qw-q765-4fww"
},
{
"type": "PACKAGE",
"url": "https://github.com/django/django"
},
{
"type": "WEB",
"url": "https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2022-1.yaml"
},
{
"type": "WEB",
"url": "https://groups.google.com/forum/#!forum/django-announce"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/B4SQG2EAF4WCI2SLRL6XRDJ3RPK3ZRDV"
},
{
"type": "WEB",
"url": "https://security.netapp.com/advisory/ntap-20220121-0005"
},
{
"type": "WEB",
"url": "https://www.djangoproject.com/weblog/2022/jan/04/security-releases"
}
],
"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",
"type": "CVSS_V4"
}
],
"summary": "Denial-of-service in Django"
}
GHSA-53RP-33P8-4HM8
Vulnerability from github – Published: 2025-02-06 06:31 – Updated: 2025-02-06 15:32A prototype pollution in the lib.merge function of xe-utils v3.5.31 allows attackers to cause a Denial of Service (DoS) via supplying a crafted payload.
{
"affected": [],
"aliases": [
"CVE-2024-57074"
],
"database_specific": {
"cwe_ids": [
"CWE-1321",
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-02-05T22:15:31Z",
"severity": "HIGH"
},
"details": "A prototype pollution in the lib.merge function of xe-utils v3.5.31 allows attackers to cause a Denial of Service (DoS) via supplying a crafted payload.",
"id": "GHSA-53rp-33p8-4hm8",
"modified": "2025-02-06T15:32:52Z",
"published": "2025-02-06T06:31:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-57074"
},
{
"type": "WEB",
"url": "https://gist.github.com/tariqhawis/82e3eb472d03273a74e40242e8356297"
}
],
"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-53VQ-MHJH-RC84
Vulnerability from github – Published: 2022-05-13 01:43 – Updated: 2022-05-13 01:43libgedit.a in GNOME gedit through 3.22.1 allows remote attackers to cause a denial of service (CPU consumption) via a file that begins with many '\0' characters.
{
"affected": [],
"aliases": [
"CVE-2017-14108"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-09-05T06:29:00Z",
"severity": "HIGH"
},
"details": "libgedit.a in GNOME gedit through 3.22.1 allows remote attackers to cause a denial of service (CPU consumption) via a file that begins with many \u0027\\0\u0027 characters.",
"id": "GHSA-53vq-mhjh-rc84",
"modified": "2022-05-13T01:43:19Z",
"published": "2022-05-13T01:43:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-14108"
},
{
"type": "WEB",
"url": "https://bugzilla.gnome.org/show_bug.cgi?id=791037"
},
{
"type": "WEB",
"url": "https://cxsecurity.com/issue/WLB-2017090008"
},
{
"type": "WEB",
"url": "https://packetstormsecurity.com/files/143983/libgedit.a-3.22.1-Denial-Of-Service.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-5426-92W4-WVHV
Vulnerability from github – Published: 2026-09-23 21:48 – Updated: 2026-09-23 21:48Impact
When creating content with a very large title or description field, Plone can become unresponsive. Even if the content loads, it can be hard to edit or delete, because the UI is unwieldy.
Patches
The problem has been patched in plone.app.dexterity.
- On Plone 6.2, upgrade to
plone.app.dexterity5.0.1. - On Plone 6.1, upgrade to
plone.app.dexterity4.1.3. - On Plone 6.0, upgrade to
plone.app.dexterity3.2.3.
Another part of this problem has been patched in plone.app.contenttypes. See this advisory.
Workarounds
There are no known workarounds.
This problem was responsibly reported by Aldin Visnjic to the Plone/Zope Security Team. Thank you!
Note: The Plone/Zope Security team felt that the kind of fixes that were needed could be disruptive in corner cases if they were not careful. So they decided to develop the fixes publicly, giving the whole community the chance the review, and giving them the benefit from early feedback.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "plone.app.dexterity"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0"
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 4.1.2"
},
"package": {
"ecosystem": "PyPI",
"name": "plone.app.dexterity"
},
"ranges": [
{
"events": [
{
"introduced": "4.0.0"
},
{
"fixed": "4.1.3"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 3.2.2"
},
"package": {
"ecosystem": "PyPI",
"name": "plone.app.dexterity"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.2.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-57576"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2026-09-23T21:48:22Z",
"nvd_published_at": "2026-09-22T23:17:07Z",
"severity": "MODERATE"
},
"details": "### Impact\nWhen creating content with a very large title or description field, Plone can become unresponsive. Even if the content loads, it can be hard to edit or delete, because the UI is unwieldy.\n\n### Patches\nThe problem has been patched in `plone.app.dexterity`.\n\n* On Plone 6.2, upgrade to `plone.app.dexterity` 5.0.1.\n* On Plone 6.1, upgrade to `plone.app.dexterity` 4.1.3.\n* On Plone 6.0, upgrade to `plone.app.dexterity` 3.2.3.\n\nAnother part of this problem has been patched in `plone.app.contenttypes`. See [this advisory](https://github.com/plone/plone.app.contenttypes/security/advisories/GHSA-8pcw-h6w9-h46g).\n\n### Workarounds\nThere are no known workarounds.\n\nThis problem was responsibly reported by Aldin Visnjic to the [Plone/Zope Security Team](mailto:security@plone.org). Thank you!\n\nNote: The Plone/Zope Security team felt that the kind of fixes that were needed could be disruptive in corner cases if they were not careful. So they decided to develop the fixes publicly, giving the whole community the chance the review, and giving them the benefit from early feedback.",
"id": "GHSA-5426-92w4-wvhv",
"modified": "2026-09-23T21:48:22Z",
"published": "2026-09-23T21:48:22Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/plone/plone.app.dexterity/security/advisories/GHSA-5426-92w4-wvhv"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-57576"
},
{
"type": "WEB",
"url": "https://github.com/plone/plone.app.dexterity/pull/433"
},
{
"type": "WEB",
"url": "https://github.com/plone/plone.app.dexterity/commit/0d317df663823445200d0569a66a95b7e4a9c50d"
},
{
"type": "WEB",
"url": "https://github.com/plone/plone.app.dexterity/commit/2fdceb120ca86682a408f3a14753cfcf5126d9d9"
},
{
"type": "WEB",
"url": "https://github.com/plone/plone.app.dexterity/commit/411689047f9a3521899ae6992a9b0efbd0592a8f"
},
{
"type": "WEB",
"url": "https://github.com/plone/plone.app.dexterity/commit/cbcef731c0882146b9bf30688cdc639d879878fb"
},
{
"type": "WEB",
"url": "https://github.com/plone/plone.app.dexterity/commit/f3596538cf7670bb8bc27b0dfa0b1da41c8b8a3a"
},
{
"type": "WEB",
"url": "https://github.com/plone/plone.app.dexterity/commit/fb45bfdb18f1dfb3ed55e477947a3df9a6ee9e20"
},
{
"type": "PACKAGE",
"url": "https://github.com/plone/plone.app.dexterity"
},
{
"type": "WEB",
"url": "https://github.com/plone/plone.app.dexterity/releases/tag/3.2.3"
},
{
"type": "WEB",
"url": "https://github.com/plone/plone.app.dexterity/releases/tag/4.1.3"
},
{
"type": "WEB",
"url": "https://github.com/plone/plone.app.dexterity/releases/tag/5.0.1"
}
],
"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"
}
],
"summary": "plone.app.dexterity has a Denial of Service due to excessive title or description length"
}
GHSA-542G-H47M-68V8
Vulnerability from github – Published: 2026-09-30 15:01 – Updated: 2026-09-30 15:01Summary
Axios versions with Node.js HTTP/2 support can terminate the caller’s process when a ClientHttp2Session emits an error event that is not handled by axios.
This affects applications that use the Node HTTP adapter with httpVersion: 2. A malicious, unavailable, or non-HTTP/2 endpoint can cause an uncaught exception instead of a normal rejected axios request.
Impact
The impact is denial of service. In affected applications, an attacker who can influence the request destination, or operate the destination server, may be able to crash the Node.js process.
This does not affect default HTTP/1.1 usage, browser XHR/fetch adapters, or applications that do not enable axios HTTP/2 support.
Affected Functionality
Affected path:
- Node.js HTTP adapter
- httpVersion: 2
- HTTP/2 session creation/reuse through Http2Sessions
- Network/session failures emitted as ClientHttp2Session error events
Caller-controlled http2Options can make the issue easier to trigger, but passing arbitrary attacker input into axios config is caller-controlled behavior and should not be the primary advisory framing.
Technical Details
Http2Sessions.getSession() creates a session with http2.connect(authority, options) but only registers a close handler. It does not register an error handler on the returned ClientHttp2Session.
When the session emits error, Node treats it as an unhandled EventEmitter error and throws. This can bypass the normal axios Promise rejection path and terminate the process.
Proof of Concept of Attack
import axios from './index.js';
await axios.get('http://127.0.0.1:1/', {
httpVersion: 2,
timeout: 1000
});
Expected vulnerable behavior: the process exits with an uncaught ECONNREFUSED session error instead of only rejecting the axios request.
Workarounds
Disable axios HTTP/2 for untrusted or user-influenced destinations and use the default HTTP/1.1 adapter until a fixed release is available. Also avoid passing attacker-controlled values into http2Options; axios config is trusted application input.
Original report
Hi, i'm RelunSec a security researcher working with **InsiteTech.jp** i want let you known, i finded a DoS in axios, to reproduce that, that is the example of a serverconst http = require('http');
// Import the local axios version to ensure the patch is active
const axios = require('../../lib/axios.js').default;
const url = require('url');
// A public HTTP/2 server to make internal requests to.
// This simulates an external service your application might interact with over HTTP/2.
const TARGET_URL = 'https://nghttp2.org/';
const PORT = 3000;
const server = http.createServer(async (req, res) => {
const parsedUrl = url.parse(req.url, true);
const http2optionId = parsedUrl.query.http2optionId;
if (!http2optionId) {
console.warn(`[SERVER] Rejected request: Missing http2optionId parameter`);
res.writeHead(400, { 'Content-Type': 'text/plain' });
res.end('Error: Missing http2optionId query parameter. Usage: ?http2optionId=value\n');
return;
}
console.log(`[SERVER] Received request with http2optionId: ${http2optionId}`);
// Create an Axios instance configured for HTTP/2
// The 'id' in http2Options makes each session configuration unique.
const axiosInstance = axios.create({
baseURL: TARGET_URL,
httpVersion: 2,
http2Options: {
// rejectUnauthorized: false, // Uncomment if targeting a local HTTP/2 server with self-signed cert
id: http2optionId, // This is the attacker-controlled unique part
},
// Adding a short timeout to prevent attacker from waiting too long if target is slow
timeout: 5000
});
try {
const response = await axiosInstance.get('/');
res.writeHead(200, { 'Content-Type': 'text/plain' });
res.end(`Internal HTTP/2 request successful for ID: ${http2optionId}\nStatus: ${response.status}`);
} catch (error) {
// Check for the specific error indicating session limit reached
if (error.isAxiosError && error.code === axios.AxiosError.ERR_BAD_OPTION_VALUE) {
console.error(`[SERVER] Internal HTTP/2 request failed for ID: ${http2optionId}: ${error.message}`);
res.writeHead(500, { 'Content-Type': 'text/plain' });
res.end(`Internal HTTP/2 request failed for ID: ${http2optionId}: ${error.message}`);
} else {
console.error(`[SERVER] Internal HTTP/2 request failed for ID: ${http2optionId}:`, error.message);
res.writeHead(500, { 'Content-Type': 'text/plain' });
res.end(`Internal HTTP/2 request failed for ID: ${http2optionId}: Generic error - ${error.message}`);
}
}
});
server.listen(PORT, () => {
console.log(`PoC Server listening on http://localhost:${PORT}`);
console.log(`Targeting internal HTTP/2 requests to: ${TARGET_URL}`);
console.log(`Send requests to http://localhost:${PORT}?http2optionId=...`);
console.log(`Expected behavior with current patch: After ~100 unique http2optionIds, subsequent requests will receive ERR_BAD_OPTION_VALUE.`);
});
relunsec@relunsec:~/software/axios-1/poc/poc$ curl http://127.0.0.1:3000/?http2optionId=hi
curl: (52) Empty reply from server
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "axios"
},
"ranges": [
{
"events": [
{
"introduced": "1.13.0"
},
{
"fixed": "1.20.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-101901"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2026-09-30T15:01:07Z",
"nvd_published_at": "2026-09-28T18:17:18Z",
"severity": "HIGH"
},
"details": "## Summary\n\nAxios versions with Node.js HTTP/2 support can terminate the caller\u2019s process when a ClientHttp2Session emits an error event that is not handled by axios.\n\nThis affects applications that use the Node HTTP adapter with httpVersion: 2. A malicious, unavailable, or non-HTTP/2 endpoint can cause an uncaught exception instead of a normal rejected axios request.\n\n## Impact\n\nThe impact is denial of service. In affected applications, an attacker who can influence the request destination, or operate the destination server, may be able to crash the Node.js process.\n\nThis does not affect default HTTP/1.1 usage, browser XHR/fetch adapters, or applications that do not enable axios HTTP/2 support.\n\n## Affected Functionality\n\nAffected path:\n\n- Node.js HTTP adapter\n- httpVersion: 2\n- HTTP/2 session creation/reuse through Http2Sessions\n- Network/session failures emitted as ClientHttp2Session error events\n\nCaller-controlled http2Options can make the issue easier to trigger, but passing arbitrary attacker input into axios config is caller-controlled behavior and should not be the primary advisory framing.\n\n## Technical Details\n\nHttp2Sessions.getSession() creates a session with http2.connect(authority, options) but only registers a close handler. It does not register an error handler on the returned ClientHttp2Session.\n\nWhen the session emits error, Node treats it as an unhandled EventEmitter error and throws. This can bypass the normal axios Promise rejection path and terminate the process.\n\n## Proof of Concept of Attack\n```js\nimport axios from \u0027./index.js\u0027;\n\nawait axios.get(\u0027http://127.0.0.1:1/\u0027, {\n httpVersion: 2,\n timeout: 1000\n});\n```\n\nExpected vulnerable behavior: the process exits with an uncaught ECONNREFUSED session error instead of only rejecting the axios request.\n\n## Workarounds\n\nDisable axios HTTP/2 for untrusted or user-influenced destinations and use the default HTTP/1.1 adapter until a fixed release is available. Also avoid passing attacker-controlled values into http2Options; axios config is trusted application input.\n\n\u003cdetails\u003e\n \u003csummary\u003e\u003ch3\u003eOriginal report\u003c/h3\u003e\u003c/summary\u003e\n \nHi, i\u0027m RelunSec a security researcher working with **InsiteTech.jp**\n\ni want let you known, i finded a DoS in axios, to reproduce that, that is the example of a server\n\n```js\nconst http = require(\u0027http\u0027);\n// Import the local axios version to ensure the patch is active\nconst axios = require(\u0027../../lib/axios.js\u0027).default; \nconst url = require(\u0027url\u0027);\n\n// A public HTTP/2 server to make internal requests to.\n// This simulates an external service your application might interact with over HTTP/2.\nconst TARGET_URL = \u0027https://nghttp2.org/\u0027; \nconst PORT = 3000;\n\nconst server = http.createServer(async (req, res) =\u003e {\n const parsedUrl = url.parse(req.url, true);\n const http2optionId = parsedUrl.query.http2optionId;\n\n if (!http2optionId) {\n console.warn(`[SERVER] Rejected request: Missing http2optionId parameter`);\n res.writeHead(400, { \u0027Content-Type\u0027: \u0027text/plain\u0027 });\n res.end(\u0027Error: Missing http2optionId query parameter. Usage: ?http2optionId=value\\n\u0027);\n return; \n}\n\n console.log(`[SERVER] Received request with http2optionId: ${http2optionId}`);\n\n // Create an Axios instance configured for HTTP/2\n // The \u0027id\u0027 in http2Options makes each session configuration unique.\n const axiosInstance = axios.create({\n baseURL: TARGET_URL,\n httpVersion: 2,\n http2Options: {\n // rejectUnauthorized: false, // Uncomment if targeting a local HTTP/2 server with self-signed cert\n id: http2optionId, // This is the attacker-controlled unique part\n },\n // Adding a short timeout to prevent attacker from waiting too long if target is slow\n timeout: 5000 \n });\n\n try {\n const response = await axiosInstance.get(\u0027/\u0027);\n res.writeHead(200, { \u0027Content-Type\u0027: \u0027text/plain\u0027 });\n res.end(`Internal HTTP/2 request successful for ID: ${http2optionId}\\nStatus: ${response.status}`);\n } catch (error) {\n // Check for the specific error indicating session limit reached\n if (error.isAxiosError \u0026\u0026 error.code === axios.AxiosError.ERR_BAD_OPTION_VALUE) {\n console.error(`[SERVER] Internal HTTP/2 request failed for ID: ${http2optionId}: ${error.message}`);\n res.writeHead(500, { \u0027Content-Type\u0027: \u0027text/plain\u0027 });\n res.end(`Internal HTTP/2 request failed for ID: ${http2optionId}: ${error.message}`);\n } else {\n console.error(`[SERVER] Internal HTTP/2 request failed for ID: ${http2optionId}:`, error.message);\n res.writeHead(500, { \u0027Content-Type\u0027: \u0027text/plain\u0027 });\n res.end(`Internal HTTP/2 request failed for ID: ${http2optionId}: Generic error - ${error.message}`);\n }\n }\n});\n\nserver.listen(PORT, () =\u003e {\n console.log(`PoC Server listening on http://localhost:${PORT}`);\n console.log(`Targeting internal HTTP/2 requests to: ${TARGET_URL}`);\n console.log(`Send requests to http://localhost:${PORT}?http2optionId=...`);\n console.log(`Expected behavior with current patch: After ~100 unique http2optionIds, subsequent requests will receive ERR_BAD_OPTION_VALUE.`);\n});\n```\n\ni tested all that in latest git version, after starting the server.cjs, to trigger that you just need do\n\n```rust\nrelunsec@relunsec:~/software/axios-1/poc/poc$ curl http://127.0.0.1:3000/?http2optionId=hi\ncurl: (52) Empty reply from server\n```\n\nthat is extremly simple to trigger\n\nit confirms a DoS in the HTTP/2 session cache, that needs be patched, the impact is will lead the server crashes and shutdown by an attacker, the server is written properly and no flaws in it and try catch blocks and errors handled however because that is an axios internal error will crash\n\u003c/details\u003e\n\n---",
"id": "GHSA-542g-h47m-68v8",
"modified": "2026-09-30T15:01:07Z",
"published": "2026-09-30T15:01:07Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/axios/axios/security/advisories/GHSA-542g-h47m-68v8"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-101901"
},
{
"type": "WEB",
"url": "https://github.com/axios/axios/pull/11141"
},
{
"type": "WEB",
"url": "https://github.com/axios/axios/commit/d19040bda7a8be2f82c3c6e1a5bc03917daee39a"
},
{
"type": "PACKAGE",
"url": "https://github.com/axios/axios"
},
{
"type": "WEB",
"url": "https://github.com/axios/axios/releases/tag/v1.20.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"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",
"type": "CVSS_V4"
}
],
"summary": "Axios: Denial of Service via Unhandled \u0027error\u0027 Event in HTTP/2 ClientHttp2Session Initialization"
}
GHSA-543H-6VP9-2F5C
Vulnerability from github – Published: 2023-04-17 21:30 – Updated: 2024-04-04 03:31Vulnerability discovered is related to the peer-to-peer (p2p) communications, attackers can craft consensus messages, send it to individual nodes and take them offline. An attacker can crawl the network peers using getaddr message and attack the unpatched nodes.
{
"affected": [],
"aliases": [
"CVE-2023-30769"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-04-17T20:15:07Z",
"severity": "CRITICAL"
},
"details": "Vulnerability discovered is related to the peer-to-peer (p2p) communications, attackers can craft consensus messages, send it to individual nodes and take them offline. An attacker can crawl the network peers using getaddr message and attack the unpatched nodes.",
"id": "GHSA-543h-6vp9-2f5c",
"modified": "2024-04-04T03:31:02Z",
"published": "2023-04-17T21:30:18Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-30769"
},
{
"type": "WEB",
"url": "https://www.halborn.com/blog/post/halborn-discovers-zero-day-impacting-dogecoin-and-280-networks"
},
{
"type": "WEB",
"url": "https://www.halborn.com/disclosures"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-545Q-3FG6-48M7
Vulnerability from github – Published: 2021-03-18 19:39 – Updated: 2023-09-12 20:51This affects the package html-parse-stringify before 2.0.1; all versions of package html-parse-stringify2. Sending certain input could cause one of the regular expressions that is used for parsing to backtrack, freezing the process.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "html-parse-stringify"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.0.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "html-parse-stringify2"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "2.0.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-23346"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2021-03-12T23:03:51Z",
"nvd_published_at": "2021-03-04T17:15:00Z",
"severity": "MODERATE"
},
"details": "This affects the package html-parse-stringify before 2.0.1; all versions of package html-parse-stringify2. Sending certain input could cause one of the regular expressions that is used for parsing to backtrack, freezing the process.",
"id": "GHSA-545q-3fg6-48m7",
"modified": "2023-09-12T20:51:14Z",
"published": "2021-03-18T19:39:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-23346"
},
{
"type": "WEB",
"url": "https://github.com/HenrikJoreteg/html-parse-stringify/commit/c7274a48e59c92b2b7e906fedf9065159e73fe12"
},
{
"type": "WEB",
"url": "https://github.com/HenrikJoreteg/html-parse-stringify/blob/master/lib/parse.js%23L2"
},
{
"type": "WEB",
"url": "https://github.com/HenrikJoreteg/html-parse-stringify/releases/tag/v2.0.1"
},
{
"type": "WEB",
"url": "https://github.com/rayd/html-parse-stringify2/blob/master/lib/parse.js%23L2"
},
{
"type": "WEB",
"url": "https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1080633"
},
{
"type": "WEB",
"url": "https://snyk.io/vuln/SNYK-JS-HTMLPARSESTRINGIFY-1079306"
},
{
"type": "WEB",
"url": "https://snyk.io/vuln/SNYK-JS-HTMLPARSESTRINGIFY2-1079307"
}
],
"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"
}
],
"summary": "html-parse-stringify and html-parse-stringify2 vulnerable to Regular expression denial of service (ReDoS)"
}
GHSA-54C4-M6WJ-XG9P
Vulnerability from github – Published: 2024-08-13 18:31 – Updated: 2024-08-13 18:31A denial-of-service vulnerability exists via the CIP/Modbus port in the Rockwell Automation Micro850/870 (2080 -L50E/2080 -L70E). If exploited, the CIP/Modbus communication may be disrupted for short duration.
{
"affected": [],
"aliases": [
"CVE-2024-7567"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-08-13T18:15:32Z",
"severity": "MODERATE"
},
"details": "A denial-of-service vulnerability exists via the CIP/Modbus port in the Rockwell Automation Micro850/870 (2080 -L50E/2080 -L70E). If exploited, the CIP/Modbus communication may be disrupted for short duration.",
"id": "GHSA-54c4-m6wj-xg9p",
"modified": "2024-08-13T18:31:17Z",
"published": "2024-08-13T18:31:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-7567"
},
{
"type": "WEB",
"url": "https://https://www.rockwellautomation.com/en-us/trust-center/security-advisories/advisory.SD1684.html"
}
],
"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/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-54CR-FX8F-GPC5
Vulnerability from github – Published: 2026-08-04 15:32 – Updated: 2026-08-05 21:31In Eclipse Milo versions 1.0.0 through 1.1.4, monitored-item quota accounting is not exception-safe: if item creation fails with an unchecked error, the server-global reservation is not restored. Deeply nested PubSub ExtensionObjects in a CreateMonitoredItems event filter can trigger a StackOverflowError during decoding, allowing an unauthenticated remote client to exhaust a finite global monitored-item quota and prevent all clients from creating new monitored items until restart. Existing monitored items and other server functions remain unaffected.
{
"affected": [],
"aliases": [
"CVE-2026-61387"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-04T13:18:55Z",
"severity": "MODERATE"
},
"details": "In Eclipse Milo versions 1.0.0 through 1.1.4, monitored-item quota accounting is not exception-safe: if item creation fails with an unchecked error, the server-global reservation is not restored. Deeply nested PubSub ExtensionObjects in a `CreateMonitoredItems` event filter can trigger a `StackOverflowError` during decoding, allowing an unauthenticated remote client to exhaust a finite global monitored-item quota and prevent all clients from creating new monitored items until restart. Existing monitored items and other server functions remain unaffected.",
"id": "GHSA-54cr-fx8f-gpc5",
"modified": "2026-08-05T21:31:34Z",
"published": "2026-08-04T15:32:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-61387"
},
{
"type": "WEB",
"url": "https://github.com/eclipse-milo/milo/commit/587e35669f519b2d7f6d850a5f86ee5a76c3a2c5"
},
{
"type": "WEB",
"url": "https://github.com/eclipse-milo/milo/commit/5f3f6da2a5ea80682e1da7c58f7a1870b09d2b43"
},
{
"type": "WEB",
"url": "https://gitlab.eclipse.org/security/cve-assignment/-/work_items/182"
},
{
"type": "WEB",
"url": "https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/598"
}
],
"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:L/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-54F7-P954-GXW6
Vulnerability from github – Published: 2026-07-22 00:31 – Updated: 2026-07-22 00:31Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: InnoDB). Supported versions that are affected are MySQL Server: 9.7.0-9.7.1; MySQL Cluster: 9.7.0-9.7.1. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server, MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
{
"affected": [],
"aliases": [
"CVE-2026-47008"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-21T22:17:06Z",
"severity": "MODERATE"
},
"details": "Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: InnoDB). Supported versions that are affected are MySQL Server: 9.7.0-9.7.1; MySQL Cluster: 9.7.0-9.7.1. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server, MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).",
"id": "GHSA-54f7-p954-gxw6",
"modified": "2026-07-22T00:31:14Z",
"published": "2026-07-22T00:31:14Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-47008"
},
{
"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:H/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
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:
- 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.
- 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.
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.