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-M99Q-R6R6-WXX3
Vulnerability from github – Published: 2024-08-08 12:30 – Updated: 2024-08-08 12:30An issue was discovered in GitLab CE/EE affecting all versions starting from 11.10 prior to 17.0.6, 17.1 prior to 17.1.4, and 17.2 prior to 17.2.2, with the processing logic for parsing invalid commits can lead to a regular expression DoS attack on the server.
{
"affected": [],
"aliases": [
"CVE-2024-3114"
],
"database_specific": {
"cwe_ids": [
"CWE-1333",
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-08-08T11:15:12Z",
"severity": "MODERATE"
},
"details": "An issue was discovered in GitLab CE/EE affecting all versions starting from 11.10 prior to 17.0.6, 17.1 prior to 17.1.4, and 17.2 prior to 17.2.2, with the processing logic for parsing invalid commits can lead to a regular expression DoS attack on the server.",
"id": "GHSA-m99q-r6r6-wxx3",
"modified": "2024-08-08T12:30:35Z",
"published": "2024-08-08T12:30:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-3114"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/2416630"
},
{
"type": "WEB",
"url": "https://gitlab.com/gitlab-org/gitlab/-/issues/452547"
}
],
"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:L",
"type": "CVSS_V3"
}
]
}
GHSA-M9FG-3Q8V-GM74
Vulnerability from github – Published: 2025-12-12 00:30 – Updated: 2025-12-12 00:30minaliC 2.0.0 contains a denial of service vulnerability that allows remote attackers to crash the web server by sending oversized GET requests. Attackers can send crafted HTTP requests with excessive data to overwhelm the server and cause service interruption.
{
"affected": [],
"aliases": [
"CVE-2024-58306"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-11T22:15:52Z",
"severity": "HIGH"
},
"details": "minaliC 2.0.0 contains a denial of service vulnerability that allows remote attackers to crash the web server by sending oversized GET requests. Attackers can send crafted HTTP requests with excessive data to overwhelm the server and cause service interruption.",
"id": "GHSA-m9fg-3q8v-gm74",
"modified": "2025-12-12T00:30:21Z",
"published": "2025-12-12T00:30:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-58306"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/51917"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/minalic-denial-of-service-vulnerability-via-large-get-request"
},
{
"type": "WEB",
"url": "http://minalic.sourceforge.net"
}
],
"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: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-M9HW-3QVV-6HXR
Vulnerability from github – Published: 2021-12-16 00:01 – Updated: 2022-05-24 00:00Windows Hyper-V Denial of Service Vulnerability
{
"affected": [],
"aliases": [
"CVE-2021-43246"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-12-15T15:15:00Z",
"severity": "MODERATE"
},
"details": "Windows Hyper-V Denial of Service Vulnerability",
"id": "GHSA-m9hw-3qvv-6hxr",
"modified": "2022-05-24T00:00:39Z",
"published": "2021-12-16T00:01:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-43246"
},
{
"type": "WEB",
"url": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-43246"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-M9J9-CMF2-WC4J
Vulnerability from github – Published: 2026-01-21 00:31 – Updated: 2026-01-21 00:31Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.0-8.0.44, 8.4.0-8.4.7 and 9.0.0-9.5.0. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. 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-21948"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-20T22:15:57Z",
"severity": "MODERATE"
},
"details": "Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.0-8.0.44, 8.4.0-8.4.7 and 9.0.0-9.5.0. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. 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-m9j9-cmf2-wc4j",
"modified": "2026-01-21T00:31:43Z",
"published": "2026-01-21T00:31:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-21948"
},
{
"type": "WEB",
"url": "https://www.oracle.com/security-alerts/cpujan2026.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"
}
]
}
GHSA-M9P8-WVPP-VMMM
Vulnerability from github – Published: 2026-01-28 18:30 – Updated: 2026-01-29 18:31A GPU device-ID validation flaw in the flow.cuda.get_device_capability() component of OneFlow v0.9.0 allows attackers to cause a Denial of Service (DoS) via a crafted device ID.
{
"affected": [],
"aliases": [
"CVE-2025-70999"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-28T18:16:51Z",
"severity": "HIGH"
},
"details": "A GPU device-ID validation flaw in the flow.cuda.get_device_capability() component of OneFlow v0.9.0 allows attackers to cause a Denial of Service (DoS) via a crafted device ID.",
"id": "GHSA-m9p8-wvpp-vmmm",
"modified": "2026-01-29T18:31:42Z",
"published": "2026-01-28T18:30:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-70999"
},
{
"type": "WEB",
"url": "https://github.com/Oneflow-Inc/oneflow/issues/10660"
},
{
"type": "WEB",
"url": "https://github.com/Daisy2ang"
},
{
"type": "WEB",
"url": "http://oneflow.com"
}
],
"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-M9P9-MH4F-QXMQ
Vulnerability from github – Published: 2022-05-14 02:18 – Updated: 2025-04-20 03:46An issue was discovered in Xen through 4.9.x allowing x86 PV guest OS users to cause a denial of service (unbounded recursion, stack consumption, and hypervisor crash) or possibly gain privileges via crafted page-table stacking.
{
"affected": [],
"aliases": [
"CVE-2017-15595"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-10-18T08:29:00Z",
"severity": "HIGH"
},
"details": "An issue was discovered in Xen through 4.9.x allowing x86 PV guest OS users to cause a denial of service (unbounded recursion, stack consumption, and hypervisor crash) or possibly gain privileges via crafted page-table stacking.",
"id": "GHSA-m9p9-mh4f-qxmq",
"modified": "2025-04-20T03:46:58Z",
"published": "2022-05-14T02:18:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-15595"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2017/11/msg00027.html"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2018/10/msg00021.html"
},
{
"type": "WEB",
"url": "https://security.gentoo.org/glsa/201801-14"
},
{
"type": "WEB",
"url": "https://support.citrix.com/article/CTX228867"
},
{
"type": "WEB",
"url": "https://www.debian.org/security/2017/dsa-4050"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/43014"
},
{
"type": "WEB",
"url": "https://xenbits.xen.org/xsa/advisory-240.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-M9PP-9784-85QG
Vulnerability from github – Published: 2026-04-24 15:32 – Updated: 2026-04-24 18:31An issue in Hostbill v.2025-11-24 and 2025-12-01 allows a remote attacker to cause a denial of service via the Client Balance component
{
"affected": [],
"aliases": [
"CVE-2026-31051"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-24T15:16:27Z",
"severity": "LOW"
},
"details": "An issue in Hostbill v.2025-11-24 and 2025-12-01 allows a remote attacker to cause a denial of service via the Client Balance component",
"id": "GHSA-m9pp-9784-85qg",
"modified": "2026-04-24T18:31:07Z",
"published": "2026-04-24T15:32:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-31051"
},
{
"type": "WEB",
"url": "https://blog.hostbillapp.com/2025/12/03/hostbill-security-advisory"
},
{
"type": "WEB",
"url": "https://github.com/Muhammad5235/HostBill-CVEs-2025/blob/main/Business%20Logic%20Vulnerability/Business%20Logic%20Vulnerability"
},
{
"type": "WEB",
"url": "https://hostbillapp.com/changelog"
},
{
"type": "WEB",
"url": "https://hostbillapp.com/release-notes/11-27-2025.html"
},
{
"type": "WEB",
"url": "https://hostbillapp.com/release-notes/12-01-2025.html"
},
{
"type": "WEB",
"url": "https://hostbillapp.com/responsible-disclosure"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-M9Q8-9M2H-84GH
Vulnerability from github – Published: 2022-05-14 01:20 – Updated: 2022-05-14 01:20Docker Engine before 18.09 allows attackers to cause a denial of service (dockerd memory consumption) via a large integer in a --cpuset-mems or --cpuset-cpus value, related to daemon/daemon_unix.go, pkg/parsers/parsers.go, and pkg/sysinfo/sysinfo.go.
{
"affected": [],
"aliases": [
"CVE-2018-20699"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-01-12T02:29:00Z",
"severity": "MODERATE"
},
"details": "Docker Engine before 18.09 allows attackers to cause a denial of service (dockerd memory consumption) via a large integer in a --cpuset-mems or --cpuset-cpus value, related to daemon/daemon_unix.go, pkg/parsers/parsers.go, and pkg/sysinfo/sysinfo.go.",
"id": "GHSA-m9q8-9m2h-84gh",
"modified": "2022-05-14T01:20:24Z",
"published": "2022-05-14T01:20:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-20699"
},
{
"type": "WEB",
"url": "https://github.com/docker/engine/pull/70"
},
{
"type": "WEB",
"url": "https://github.com/moby/moby/pull/37967"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2019:0487"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-M9WC-H684-M6RQ
Vulnerability from github – Published: 2022-05-24 17:40 – Updated: 2022-05-24 17:40A wrong check in Nextcloud Server 19 and prior allowed to perform a denial of service attack when resetting the password for a user.
{
"affected": [],
"aliases": [
"CVE-2020-8295"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-01-26T18:16:00Z",
"severity": "HIGH"
},
"details": "A wrong check in Nextcloud Server 19 and prior allowed to perform a denial of service attack when resetting the password for a user.",
"id": "GHSA-m9wc-h684-m6rq",
"modified": "2022-05-24T17:40:19Z",
"published": "2022-05-24T17:40:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-8295"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/812754"
},
{
"type": "WEB",
"url": "https://nextcloud.com/security/advisory/?id=NC-SA-2021-003"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-M9XH-6747-9R6F
Vulnerability from github – Published: 2026-10-08 19:41 – Updated: 2026-10-08 19:41Summary
Resolver::processReferences() collects <use> elements with the XPath predicate use[@href or @xlink:href], which is case sensitive. A <use> element written as xlink:HrEf is therefore never added to the reference graph, so the nesting-DoS nullification never marks it for removal. Sanitizer::cleanHrefAttributes() then runs later in the same pass and rewrites xlink:HrEf back to the canonical xlink:href. The sanitizer hands back a fully live nesting bomb that it would have stripped completely had the input used canonical casing.
This is the mirror image of CVE-2025-55166: that fix made href value checking case insensitive, but the <use> reference graph still selects nodes case sensitively.
Where it is
src/ElementReference/Resolver.php:97-118, the case-sensitive node selection:
$useNodeName = $this->xPath->createNodeName('use');
foreach ($this->subjects as $subject) {
$useElements = $this->xPath->query(
$useNodeName . '[@href or @xlink:href]',
$subject->getElement()
);
src/Sanitizer.php:479-504, the normalization that happens afterwards and makes the attribute live again:
// in case the attribute name is `HrEf`/`xlink:HrEf`, adjust it to `href`/`xlink:href`
if (!in_array($attribute->nodeName, $this->allowedAttrs, true)
&& in_array(strtolower($attribute->nodeName), $this->allowedAttrs, true)
) {
$element->removeAttribute($attribute->nodeName);
$element->setAttribute(strtolower($attribute->nodeName), $attribute->value);
}
Ordering is the whole bug. Sanitizer::sanitize() builds the resolver graph first and normalizes attribute casing second, so the graph is built against names the sanitizer is about to change.
Impact
Anyone who can submit an SVG to an application that sanitizes it with this library and then serves it. No privileges beyond being able to upload or paste an SVG. The output is the project's own tests/data/useDosTest.svg nesting structure, intact, with canonical xlink:href attributes, which is exactly the input the useNestingLimit machinery exists to defuse.
Proof of concept
Against a clean clone of tag 0.22.0. The only change to the input is rewriting xlink:href to xlink:HrEf in the project's own DoS fixture.
<?php
spl_autoload_register(function ($class) {
$p = 'enshrined\\svgSanitize\\';
if (strpos($class, $p) !== 0) return;
$rel = str_replace('\\', '/', substr($class, strlen($p)));
$f = __DIR__ . '/svgsan/src/' . $rel . '.php';
if (file_exists($f)) require $f;
});
$orig = file_get_contents(__DIR__ . '/svgsan/tests/data/useDosTest.svg');
$mut = str_replace('xlink:href', 'xlink:HrEf', $orig);
function run($label, $input) {
$s = new \enshrined\svgSanitize\Sanitizer();
$s->removeRemoteReferences(true);
$out = $s->sanitize($input);
echo "[$label]\n";
echo " output <use count : ", substr_count($out, '<use '), "\n";
echo " output xlink:href : ", (strpos($out,'xlink:href')!==false?'YES':'NO'), "\n";
echo " output xlink:HrEf : ", (strpos($out,'xlink:HrEf')!==false?'YES':'NO'), "\n";
}
run('canonical xlink:href (control)', $orig);
run('mixed-case xlink:HrEf (attack)', $mut);
Observed on PHP 8.5.9:
orig use count: 201
mutated input has xlink:HrEf: YES
[canonical xlink:href (control)]
output <use count : 0
output xlink:href : NO
output xlink:HrEf : NO
[mixed-case xlink:HrEf (attack)]
output <use count : 201
output xlink:href : YES
output xlink:HrEf : NO
201 to 0 on canonical input, 201 to 201 on mixed-case input, and the output attribute name comes back canonical either way. To be precise about what I measured: I measured the nullification being skipped and the attribute being re-canonicalized. I did not measure renderer memory or CPU on the resulting file, so the downstream cost is whatever you already assign to useDosTest.svg.
Suggested fix
Stop matching attribute names case sensitively when the reference graph is built. Either select every descendant use and resolve the href in PHP with a case-insensitive local-name lookup (an extension of Helper::getElementHref() at Helper.php:10-19 is the smallest change), or move the cleanHrefAttributes() canonicalization so it runs before $this->elementReferenceResolver->collect() rather than after, so the resolver only ever sees href and xlink:href. The second option also removes the general class of bug where the graph and the cleaner disagree about a node's identity.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.22.0"
},
"package": {
"ecosystem": "Packagist",
"name": "enshrined/svg-sanitize"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-107381"
],
"database_specific": {
"cwe_ids": [
"CWE-178",
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-08T19:41:10Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "## Summary\n\n`Resolver::processReferences()` collects `\u003cuse\u003e` elements with the XPath predicate `use[@href or @xlink:href]`, which is case sensitive. A `\u003cuse\u003e` element written as `xlink:HrEf` is therefore never added to the reference graph, so the nesting-DoS nullification never marks it for removal. `Sanitizer::cleanHrefAttributes()` then runs later in the same pass and rewrites `xlink:HrEf` back to the canonical `xlink:href`. The sanitizer hands back a fully live nesting bomb that it would have stripped completely had the input used canonical casing.\n\nThis is the mirror image of CVE-2025-55166: that fix made href *value* checking case insensitive, but the `\u003cuse\u003e` reference graph still selects nodes case sensitively.\n\n## Where it is\n\n`src/ElementReference/Resolver.php:97-118`, the case-sensitive node selection:\n\n```php\n$useNodeName = $this-\u003exPath-\u003ecreateNodeName(\u0027use\u0027);\nforeach ($this-\u003esubjects as $subject) {\n $useElements = $this-\u003exPath-\u003equery(\n $useNodeName . \u0027[@href or @xlink:href]\u0027,\n $subject-\u003egetElement()\n );\n```\n\n`src/Sanitizer.php:479-504`, the normalization that happens afterwards and makes the attribute live again:\n\n```php\n// in case the attribute name is `HrEf`/`xlink:HrEf`, adjust it to `href`/`xlink:href`\nif (!in_array($attribute-\u003enodeName, $this-\u003eallowedAttrs, true)\n \u0026\u0026 in_array(strtolower($attribute-\u003enodeName), $this-\u003eallowedAttrs, true)\n) {\n $element-\u003eremoveAttribute($attribute-\u003enodeName);\n $element-\u003esetAttribute(strtolower($attribute-\u003enodeName), $attribute-\u003evalue);\n}\n```\n\nOrdering is the whole bug. `Sanitizer::sanitize()` builds the resolver graph first and normalizes attribute casing second, so the graph is built against names the sanitizer is about to change.\n\n## Impact\n\nAnyone who can submit an SVG to an application that sanitizes it with this library and then serves it. No privileges beyond being able to upload or paste an SVG. The output is the project\u0027s own `tests/data/useDosTest.svg` nesting structure, intact, with canonical `xlink:href` attributes, which is exactly the input the `useNestingLimit` machinery exists to defuse.\n\n## Proof of concept\n\nAgainst a clean clone of tag `0.22.0`. The only change to the input is rewriting `xlink:href` to `xlink:HrEf` in the project\u0027s own DoS fixture.\n\n```php\n\u003c?php\nspl_autoload_register(function ($class) {\n $p = \u0027enshrined\\\\svgSanitize\\\\\u0027;\n if (strpos($class, $p) !== 0) return;\n $rel = str_replace(\u0027\\\\\u0027, \u0027/\u0027, substr($class, strlen($p)));\n $f = __DIR__ . \u0027/svgsan/src/\u0027 . $rel . \u0027.php\u0027;\n if (file_exists($f)) require $f;\n});\n$orig = file_get_contents(__DIR__ . \u0027/svgsan/tests/data/useDosTest.svg\u0027);\n$mut = str_replace(\u0027xlink:href\u0027, \u0027xlink:HrEf\u0027, $orig);\n\nfunction run($label, $input) {\n $s = new \\enshrined\\svgSanitize\\Sanitizer();\n $s-\u003eremoveRemoteReferences(true);\n $out = $s-\u003esanitize($input);\n echo \"[$label]\\n\";\n echo \" output \u003cuse count : \", substr_count($out, \u0027\u003cuse \u0027), \"\\n\";\n echo \" output xlink:href : \", (strpos($out,\u0027xlink:href\u0027)!==false?\u0027YES\u0027:\u0027NO\u0027), \"\\n\";\n echo \" output xlink:HrEf : \", (strpos($out,\u0027xlink:HrEf\u0027)!==false?\u0027YES\u0027:\u0027NO\u0027), \"\\n\";\n}\nrun(\u0027canonical xlink:href (control)\u0027, $orig);\nrun(\u0027mixed-case xlink:HrEf (attack)\u0027, $mut);\n```\n\nObserved on PHP 8.5.9:\n\n```text\norig use count: 201\nmutated input has xlink:HrEf: YES\n\n[canonical xlink:href (control)]\n output \u003cuse count : 0\n output xlink:href : NO\n output xlink:HrEf : NO\n[mixed-case xlink:HrEf (attack)]\n output \u003cuse count : 201\n output xlink:href : YES\n output xlink:HrEf : NO\n```\n\n201 to 0 on canonical input, 201 to 201 on mixed-case input, and the output attribute name comes back canonical either way. To be precise about what I measured: I measured the nullification being skipped and the attribute being re-canonicalized. I did not measure renderer memory or CPU on the resulting file, so the downstream cost is whatever you already assign to `useDosTest.svg`.\n\n## Suggested fix\n\nStop matching attribute names case sensitively when the reference graph is built. Either select every descendant `use` and resolve the href in PHP with a case-insensitive local-name lookup (an extension of `Helper::getElementHref()` at `Helper.php:10-19` is the smallest change), or move the `cleanHrefAttributes()` canonicalization so it runs before `$this-\u003eelementReferenceResolver-\u003ecollect()` rather than after, so the resolver only ever sees `href` and `xlink:href`. The second option also removes the general class of bug where the graph and the cleaner disagree about a node\u0027s identity.",
"id": "GHSA-m9xh-6747-9r6f",
"modified": "2026-10-08T19:41:10Z",
"published": "2026-10-08T19:41:10Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/darylldoyle/svg-sanitizer/security/advisories/GHSA-m9xh-6747-9r6f"
},
{
"type": "WEB",
"url": "https://github.com/darylldoyle/svg-sanitizer/commit/2dff6628314de8519155b7feb218bbe132785757"
},
{
"type": "PACKAGE",
"url": "https://github.com/darylldoyle/svg-sanitizer"
},
{
"type": "WEB",
"url": "https://github.com/darylldoyle/svg-sanitizer/releases/tag/1.0.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "svg-sanitizer: Mixed-case xlink:HrEf skips the `\u003cuse\u003e` nesting-DoS check in Resolver::processReferences"
}
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.