Common Weakness Enumeration
CWE-400
DiscouragedUncontrolled Resource Consumption
Abstraction: Class · Status: Draft
The product does not properly control the allocation and maintenance of a limited resource.
5567 vulnerabilities reference this CWE, most recent first.
GHSA-F9CM-P3W6-XVR3
Vulnerability from github – Published: 2018-10-09 00:38 – Updated: 2020-08-31 18:08
VLAI
Summary
Denial-of-Service Extended Event Loop Blocking in qs
Details
Versions prior to 1.0.0 of qs are affected by a denial of service vulnerability that results from excessive recursion in parsing a deeply nested JSON string.
Recommendation
Update to version 1.0.0 or later
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "qs"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2014-10064"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2020-06-16T21:34:11Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "Versions prior to 1.0.0 of `qs` are affected by a denial of service vulnerability that results from excessive recursion in parsing a deeply nested JSON string.\n\n\n\n\n## Recommendation\n\nUpdate to version 1.0.0 or later",
"id": "GHSA-f9cm-p3w6-xvr3",
"modified": "2020-08-31T18:08:25Z",
"published": "2018-10-09T00:38:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2014-10064"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-f9cm-p3w6-xvr3"
},
{
"type": "WEB",
"url": "https://www.npmjs.com/advisories/28"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "Denial-of-Service Extended Event Loop Blocking in qs"
}
GHSA-F9CM-QMX5-M98H
Vulnerability from github – Published: 2018-11-01 14:45 – Updated: 2023-09-07 20:34
VLAI
Summary
Prototype Pollution in merge
Details
Versions of merge before 1.2.1 are vulnerable to prototype pollution. The merge.recursive function can be tricked into adding or modifying properties of the Object prototype.
Recommendation
Update to version 1.2.1 or later.
Severity
7.5 (High)
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "merge"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.2.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2018-16469"
],
"database_specific": {
"cwe_ids": [
"CWE-1321",
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2020-06-16T21:34:14Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "Versions of `merge` before 1.2.1 are vulnerable to prototype pollution. The `merge.recursive` function can be tricked into adding or modifying properties of the Object prototype.\n\n\n## Recommendation\n\nUpdate to version 1.2.1 or later.",
"id": "GHSA-f9cm-qmx5-m98h",
"modified": "2023-09-07T20:34:10Z",
"published": "2018-11-01T14:45:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-16469"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/381194"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-f9cm-qmx5-m98h"
},
{
"type": "WEB",
"url": "https://www.npmjs.com/advisories/722"
}
],
"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": "Prototype Pollution in merge"
}
GHSA-F9XV-M3HP-2JQ7
Vulnerability from github – Published: 2022-05-13 01:36 – Updated: 2022-05-13 01:36
VLAI
Details
A Resource Consumption issue was discovered in Trihedral VTScada Versions prior to 11.2.26. The client does not properly validate the input or limit the amount of resources that are utilized by an attacker, which can be used to consume more resources than are available.
Severity
7.5 (High)
{
"affected": [],
"aliases": [
"CVE-2017-6043"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-06-21T19:29:00Z",
"severity": "HIGH"
},
"details": "A Resource Consumption issue was discovered in Trihedral VTScada Versions prior to 11.2.26. The client does not properly validate the input or limit the amount of resources that are utilized by an attacker, which can be used to consume more resources than are available.",
"id": "GHSA-f9xv-m3hp-2jq7",
"modified": "2022-05-13T01:36:34Z",
"published": "2022-05-13T01:36:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-6043"
},
{
"type": "WEB",
"url": "https://ics-cert.us-cert.gov/advisories/ICSA-17-164-01"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/99066"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-FC5R-PJ7X-F9M3
Vulnerability from github – Published: 2025-05-29 18:31 – Updated: 2025-05-29 21:31
VLAI
Details
An issue in Open Network Foundation ONOS v2.7.0 allows attackers to cause a Denial of Service (DoS) via supplying crafted packets.
Severity
5.6 (Medium)
{
"affected": [],
"aliases": [
"CVE-2024-53423"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-05-29T18:15:23Z",
"severity": "MODERATE"
},
"details": "An issue in Open Network Foundation ONOS v2.7.0 allows attackers to cause a Denial of Service (DoS) via supplying crafted packets.",
"id": "GHSA-fc5r-pj7x-f9m3",
"modified": "2025-05-29T21:31:37Z",
"published": "2025-05-29T18:31:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53423"
},
{
"type": "WEB",
"url": "https://gist.github.com/kjw6855/abeecc798d138b49537393e1fd3a5e96"
},
{
"type": "WEB",
"url": "https://wiki.onosproject.org/pages/viewpage.action?pageId=16122675"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-FC6J-W9HX-R5XV
Vulnerability from github – Published: 2023-12-07 09:30 – Updated: 2023-12-09 06:30
VLAI
Details
A lack of rate limiting in pjActionAJaxSend in Availability Booking Calendar 5.0 allows attackers to cause resource exhaustion.
Severity
7.5 (High)
{
"affected": [],
"aliases": [
"CVE-2023-48831"
],
"database_specific": {
"cwe_ids": [
"CWE-400",
"CWE-770"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-12-07T07:15:11Z",
"severity": "HIGH"
},
"details": "A lack of rate limiting in pjActionAJaxSend in Availability Booking Calendar 5.0 allows attackers to cause resource exhaustion.",
"id": "GHSA-fc6j-w9hx-r5xv",
"modified": "2023-12-09T06:30:20Z",
"published": "2023-12-07T09:30:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-48831"
},
{
"type": "WEB",
"url": "https://www.phpjabbers.com/availability-booking-calendar/#sectionDemo"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/176039"
}
],
"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-FCG8-MG9G-6HC4
Vulnerability from github – Published: 2022-08-30 19:35 – Updated: 2026-06-08 23:41
VLAI
Summary
.NET Denial of Service Vulnerability
Details
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 6.0, .NET 5.0 and .NET Core 3.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A vulnerability exists in .NET 6.0, .NET 5.0 and .NET core 3.1 where a malicious client can can cause a denial of service when HTML forms are parsed.
Affected software
- Any .NET 6.0 application running on .NET 6.0.4 or earlier.
- Any .NET 5.0 application running .NET 5.0.16 or earlier.
- Any .NET Core 3.1 application running on .NET Core 3.1.24 or earlier.
Affected packages
.NET Core 3.1
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.AspNetCore.App.Runtime.win-x64 | >=3.0.0,3.1.24 | 3.1.25 |
| Microsoft.AspNetCore.App.Runtime.linux-x64 | >=3.0.0,3.1.24 | 3.1.25 |
| Microsoft.AspNetCore.App.Runtime.win-x86 | >=3.0.0,3.1.24 | 3.1.25 |
| Microsoft.AspNetCore.App.Runtime.osx-x64 | >=3.0.0,3.1.24 | 3.1.25 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | >=3.0.0,3.1.24 | 3.1.25 |
| Microsoft.AspNetCore.App.Runtime.linux-arm64 | >=3.0.0,3.1.24 | 3.1.25 |
| Microsoft.AspNetCore.App.Runtime.linux-arm | >=3.0.0,3.1.24 | 3.1.25 |
| Microsoft.AspNetCore.App.Runtime.win-arm64 | >=3.0.0,3.1.24 | 3.1.25 |
| Microsoft.AspNetCore.App.Runtime.win-arm | >=3.0.0,3.1.24 | 3.1.25 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | >=3.0.0,3.1.24 | 3.1.25 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-arm | >=3.0.0,3.1.24 | 3.1.25 |
.NET 5.0
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.AspNetCore.App.Runtime.win-x64 | >=5.0.0,5.0.16 | 5.0.17 |
| Microsoft.AspNetCore.App.Runtime.linux-x64 | >=5.0.0,5.0.16 | 5.0.17 |
| Microsoft.AspNetCore.App.Runtime.win-x86 | >=5.0.0,5.0.16 | 5.0.17 |
| Microsoft.AspNetCore.App.Runtime.osx-x64 | >=5.0.0,5.0.16 | 5.0.17 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | >=5.0.0,5.0.16 | 5.0.17 |
| Microsoft.AspNetCore.App.Runtime.linux-arm64 | >=5.0.0,5.0.16 | 5.0.17 |
| Microsoft.AspNetCore.App.Runtime.linux-arm | >=5.0.0,5.0.16 | 5.0.17 |
| Microsoft.AspNetCore.App.Runtime.win-arm64 | >=5.0.0,5.0.16 | 5.0.17 |
| Microsoft.AspNetCore.App.Runtime.win-arm | >=5.0.0,5.0.16 | 5.0.17 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | >=5.0.0,5.0.16 | 5.0.17 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-arm | >=5.0.0,5.0.16 | 5.0.17 |
.NET 6.0
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.AspNetCore.App.Runtime.win-x64 | >=6.0.0,6.0.4 | 6.0.5 |
| Microsoft.AspNetCore.App.Runtime.linux-x64 | >=6.0.0,6.0.4 | 6.0.5 |
| Microsoft.AspNetCore.App.Runtime.win-x86 | >=6.0.0,6.0.4 | 6.0.5 |
| Microsoft.AspNetCore.App.Runtime.osx-x64 | >=6.0.0,6.0.4 | 6.0.5 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | >=6.0.0,6.0.4 | 6.0.5 |
| Microsoft.AspNetCore.App.Runtime.linux-arm64 | >=6.0.0,6.0.4 | 6.0.5 |
| Microsoft.AspNetCore.App.Runtime.linux-arm | >=6.0.0,6.0.4 | 6.0.5 |
| Microsoft.AspNetCore.App.Runtime.win-arm64 | >=6.0.0,6.0.4 | 6.0.5 |
| Microsoft.AspNetCore.App.Runtime.win-arm | >=6.0.0,6.0.4 | 6.0.5 |
| Microsoft.AspNetCore.App.Runtime.osx-arm64 | >=6.0.0,6.0.4 | 6.0.5 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | >=6.0.0,6.0.4 | 6.0.5 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-arm | >=6.0.0,6.0.4 | 6.0.5 |
Patches
-
If you're using .NET Core 6.0, you should download and install Runtime 6.0.5 or SDK 6.0.105 (for Visual Studio 2022 v17.0) or SDK 6.0.203 (for Visual Studio 2022 v17.1) from https://dotnet.microsoft.com/download/dotnet-core/6.0.
-
If you're using .NET 5.0, you should download and install Runtime 5.0.17 or SDK 5.0.214 (for Visual Studio 2019 v16.9) or SDK 5.0.408 (for Visual Studio 2011 v16.11) from https://dotnet.microsoft.com/download/dotnet-core/5.0.
-
If you're using .NET Core 3.1, you should download and install Runtime 3.1.25 or SDK 3.1.419 (for Visual Studio 2019 v16.9 or Visual Studio 2011 16.11 or Visual Studio 2022 17.0 or Visual Studio 2022 17.1 ) from https://dotnet.microsoft.com/download/dotnet-core/3.1.
.NET 6.0, .NET 5.0 and .NET Core 3.1 updates are also available from Microsoft Update. To access this either type "Check for updates" in your Windows search, or open Settings, choose Update & Security and then click Check for Updates.
Other
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/222 An Issue for this can be found at https://github.com/dotnet/aspnetcore/issues/41609 MSRC details for this can be found at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-29145
Severity
7.5 (High)
{
"affected": [
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.win-x64"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.1.25"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.win-x64"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.17"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.win-x64"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.0.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-x64"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.1.25"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-x64"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.17"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-x64"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.0.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.win-x86"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.1.25"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.win-x86"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.17"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.win-x86"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.0.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.osx-x64"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.1.25"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.osx-x64"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.17"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.osx-x64"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.0.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-musl-x64"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.1.25"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-musl-x64"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.17"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-musl-x64"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.0.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-arm64"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.1.25"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-arm64"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.17"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-arm64"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.0.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-arm"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.1.25"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-arm"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.17"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-arm"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.0.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.win-arm64"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.1.25"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.win-arm64"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.17"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.win-arm64"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.0.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.win-arm"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.1.25"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.win-arm"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.17"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.win-arm"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.0.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-musl-arm64"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.1.25"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-musl-arm64"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.17"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-musl-arm64"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.0.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-musl-arm"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.1.25"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-musl-arm"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.17"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Microsoft.AspNetCore.App.Runtime.linux-musl-arm"
},
"ranges": [
{
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.0.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-29145"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2022-08-30T19:35:52Z",
"nvd_published_at": "2022-05-10T21:15:00Z",
"severity": "HIGH"
},
"details": "Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 6.0, .NET 5.0 and .NET Core 3.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.\n\nA vulnerability exists in .NET 6.0, .NET 5.0 and .NET core 3.1 where a malicious client can can cause a denial of service when HTML forms are parsed.\n\n### Affected software\n\n* Any .NET 6.0 application running on .NET 6.0.4 or earlier.\n* Any .NET 5.0 application running .NET 5.0.16 or earlier.\n* Any .NET Core 3.1 application running on .NET Core 3.1.24 or earlier.\n\n#### Affected packages\n\n**.NET Core 3.1**\n\n| Package name | Affected version | Patched version |\n|---------------------------------------------------|---------------------|---------------|\n| Microsoft.AspNetCore.App.Runtime.win-x64 | \u003e=3.0.0,3.1.24 | 3.1.25 |\n| Microsoft.AspNetCore.App.Runtime.linux-x64 | \u003e=3.0.0,3.1.24 | 3.1.25 |\n| Microsoft.AspNetCore.App.Runtime.win-x86 | \u003e=3.0.0,3.1.24 | 3.1.25 |\n| Microsoft.AspNetCore.App.Runtime.osx-x64 | \u003e=3.0.0,3.1.24 | 3.1.25 |\n| Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | \u003e=3.0.0,3.1.24 | 3.1.25 |\n| Microsoft.AspNetCore.App.Runtime.linux-arm64 | \u003e=3.0.0,3.1.24 | 3.1.25 |\n| Microsoft.AspNetCore.App.Runtime.linux-arm | \u003e=3.0.0,3.1.24 | 3.1.25 |\n| Microsoft.AspNetCore.App.Runtime.win-arm64 | \u003e=3.0.0,3.1.24 | 3.1.25 |\n| Microsoft.AspNetCore.App.Runtime.win-arm | \u003e=3.0.0,3.1.24 | 3.1.25 |\n| Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | \u003e=3.0.0,3.1.24 | 3.1.25 |\n| Microsoft.AspNetCore.App.Runtime.linux-musl-arm | \u003e=3.0.0,3.1.24 | 3.1.25 |\n\n**.NET 5.0**\n\n| Package name | Affected version | Patched version |\n|---------------------------------------------------|---------------------|---------------|\n| Microsoft.AspNetCore.App.Runtime.win-x64 | \u003e=5.0.0,5.0.16 | 5.0.17 |\n| Microsoft.AspNetCore.App.Runtime.linux-x64 | \u003e=5.0.0,5.0.16 | 5.0.17 |\n| Microsoft.AspNetCore.App.Runtime.win-x86 | \u003e=5.0.0,5.0.16 | 5.0.17 |\n| Microsoft.AspNetCore.App.Runtime.osx-x64 | \u003e=5.0.0,5.0.16 | 5.0.17 |\n| Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | \u003e=5.0.0,5.0.16 | 5.0.17 |\n| Microsoft.AspNetCore.App.Runtime.linux-arm64 | \u003e=5.0.0,5.0.16 | 5.0.17 |\n| Microsoft.AspNetCore.App.Runtime.linux-arm | \u003e=5.0.0,5.0.16 | 5.0.17 |\n| Microsoft.AspNetCore.App.Runtime.win-arm64 | \u003e=5.0.0,5.0.16 | 5.0.17 |\n| Microsoft.AspNetCore.App.Runtime.win-arm | \u003e=5.0.0,5.0.16 | 5.0.17 |\n| Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | \u003e=5.0.0,5.0.16 | 5.0.17 |\n| Microsoft.AspNetCore.App.Runtime.linux-musl-arm | \u003e=5.0.0,5.0.16 | 5.0.17 |\n\n**.NET 6.0**\n\n| Package name | Affected version | Patched version |\n|---------------------------------------------------|---------------------|---------------|\n| Microsoft.AspNetCore.App.Runtime.win-x64 | \u003e=6.0.0,6.0.4 | 6.0.5 |\n| Microsoft.AspNetCore.App.Runtime.linux-x64 | \u003e=6.0.0,6.0.4 | 6.0.5 |\n| Microsoft.AspNetCore.App.Runtime.win-x86 | \u003e=6.0.0,6.0.4 | 6.0.5 |\n| Microsoft.AspNetCore.App.Runtime.osx-x64 | \u003e=6.0.0,6.0.4 | 6.0.5 |\n| Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | \u003e=6.0.0,6.0.4 | 6.0.5 |\n| Microsoft.AspNetCore.App.Runtime.linux-arm64 | \u003e=6.0.0,6.0.4 | 6.0.5 |\n| Microsoft.AspNetCore.App.Runtime.linux-arm | \u003e=6.0.0,6.0.4 | 6.0.5 |\n| Microsoft.AspNetCore.App.Runtime.win-arm64 | \u003e=6.0.0,6.0.4 | 6.0.5 |\n| Microsoft.AspNetCore.App.Runtime.win-arm | \u003e=6.0.0,6.0.4 | 6.0.5 |\n| Microsoft.AspNetCore.App.Runtime.osx-arm64 | \u003e=6.0.0,6.0.4 | 6.0.5 |\n| Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | \u003e=6.0.0,6.0.4 | 6.0.5 |\n| Microsoft.AspNetCore.App.Runtime.linux-musl-arm | \u003e=6.0.0,6.0.4 | 6.0.5 |\n\n\n### Patches\n* If you\u0027re using .NET Core 6.0, you should download and install Runtime 6.0.5 or SDK 6.0.105 (for Visual Studio 2022 v17.0) or SDK 6.0.203 (for Visual Studio 2022 v17.1) from https://dotnet.microsoft.com/download/dotnet-core/6.0.\n\n* If you\u0027re using .NET 5.0, you should download and install Runtime 5.0.17 or SDK 5.0.214 (for Visual Studio 2019 v16.9) or SDK 5.0.408 (for Visual Studio 2011 v16.11) from https://dotnet.microsoft.com/download/dotnet-core/5.0.\n\n* If you\u0027re using .NET Core 3.1, you should download and install Runtime 3.1.25 or SDK 3.1.419 (for Visual Studio 2019 v16.9 or Visual Studio 2011 16.11 or Visual Studio 2022 17.0 or Visual Studio 2022 17.1 ) from https://dotnet.microsoft.com/download/dotnet-core/3.1.\n\n.NET 6.0, .NET 5.0 and .NET Core 3.1 updates are also available from Microsoft Update. To access this either type \"Check for updates\" in your Windows search, or open Settings, choose Update \u0026 Security and then click Check for Updates.\n\n### Other\n\nAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/222\nAn Issue for this can be found at https://github.com/dotnet/aspnetcore/issues/41609\nMSRC details for this can be found at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-29145",
"id": "GHSA-fcg8-mg9g-6hc4",
"modified": "2026-06-08T23:41:10Z",
"published": "2022-08-30T19:35:52Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/dotnet/aspnetcore/security/advisories/GHSA-fcg8-mg9g-6hc4"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-29145"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GNXQL7EZORGU4PZCPJ5EPQ4P7IEY3ZZO"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IBYSBUDJYQ76HK4TULXVIIPCKK2U6WDB"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/W5FPEQ6BTYRGTS6IYCDTZW6YF5HLQ3BY"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNXQL7EZORGU4PZCPJ5EPQ4P7IEY3ZZO"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IBYSBUDJYQ76HK4TULXVIIPCKK2U6WDB"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/W5FPEQ6BTYRGTS6IYCDTZW6YF5HLQ3BY"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-29145"
},
{
"type": "WEB",
"url": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2022-29145"
}
],
"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": ".NET Denial of Service Vulnerability"
}
GHSA-FCM2-6C3H-PG6J
Vulnerability from github – Published: 2022-06-06 21:50 – Updated: 2023-07-24 19:33
VLAI
Summary
Node DOS by way of memory exhaustion through ExecSync request in CRI-O
Details
Description
An ExecSync request runs a command in a container and returns the output to the Kubelet. It is used for readiness and liveness probes within a pod. The way CRI-O runs ExecSync commands is through conmon. CRI-O asks conmon to start the process, and conmon writes the output to disk. CRI-O then reads the output and returns it to the Kubelet.
If the output of the command is large enough, it is possible to exhaust the memory (or disk usage) of the node. The following deployment is an example yaml file that will output around 8GB of ‘A’ characters, which would be written to disk by conmon and read by CRI-O.
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx-deployment100
spec:
selector:
matchLabels:
app: nginx
replicas: 2
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.14.2
lifecycle:
postStart:
exec:
command: ["/bin/sh", "-c", "seq 1 50000000`; do echo -n 'aaaaaaaaaaaaaaaa'; done"]
Impact
It is possible for the node to be exhausted of memory or disk space, depending on the node the command is being run on. What is further problematic is that the memory and disk usage aren't attributed to the container, as this file and its processing are implementation details of CRI-O. The consequence of the exhaustion is that other services on the node, e.g. other containers, will be unable to allocate memory and thus causing a denial of service.
Patches
This vulnerability will be fixed in 1.24.1, 1.23.3, 1.22.5, v1.21.8, v1.20.8, v1.19.7
Workarounds
At the time of writing, no workaround exists other than ensuring only trusted images are used.
References
https://github.com/containerd/containerd/security/advisories/GHSA-5ffw-gxpp-mxpf
For more information
If you have any questions or comments about this advisory: * Open an issue in the CRI-O repo * To make a report, email your vulnerability to the private cncf-crio-security@lists.cncf.io list with the security details and the details expected for all CRI-O bug reports.
Credits
Disclosed by Ada Logics in a security audit sponsored by CNCF and facilitated by OSTIF.
Severity
7.5 (High)
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/cri-o/cri-o"
},
"ranges": [
{
"events": [
{
"introduced": "1.24.0"
},
{
"fixed": "1.24.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.24.0"
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/cri-o/cri-o"
},
"ranges": [
{
"events": [
{
"introduced": "1.23.0"
},
{
"fixed": "1.23.3"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/cri-o/cri-o"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.22.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-1708"
],
"database_specific": {
"cwe_ids": [
"CWE-400",
"CWE-770"
],
"github_reviewed": true,
"github_reviewed_at": "2022-06-06T21:50:21Z",
"nvd_published_at": "2022-06-07T18:15:00Z",
"severity": "HIGH"
},
"details": "### Description\nAn ExecSync request runs a command in a container and returns the output to the Kubelet. It is used for readiness and liveness probes within a pod. The way CRI-O runs ExecSync commands is through conmon. CRI-O asks conmon to start the process, and conmon writes the output to disk. CRI-O then reads the output and returns it to the Kubelet.\n\nIf the output of the command is large enough, it is possible to exhaust the memory (or disk usage) of the node. The following deployment is an example yaml file that will output around 8GB of \u2018A\u2019 characters, which would be written to disk by conmon and read by CRI-O.\n\n```yaml\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n name: nginx-deployment100\nspec:\n selector:\n matchLabels:\n app: nginx\n replicas: 2\n template:\n metadata:\n labels:\n app: nginx\n spec:\n containers:\n - name: nginx\n image: nginx:1.14.2\n lifecycle:\n postStart:\n exec:\n command: [\"/bin/sh\", \"-c\", \"seq 1 50000000`; do echo -n \u0027aaaaaaaaaaaaaaaa\u0027; done\"]\n```\n\n### Impact\nIt is possible for the node to be exhausted of memory or disk space, depending on the node the command is being run on. What is further problematic is that the memory and disk usage aren\u0027t attributed to the container, as this file and its processing are implementation details of CRI-O. The consequence of the exhaustion is that other services on the node, e.g. other containers, will be unable to allocate memory and thus causing a denial of service.\n\n### Patches\nThis vulnerability will be fixed in 1.24.1, 1.23.3, 1.22.5, v1.21.8, v1.20.8, v1.19.7\n\n### Workarounds\nAt the time of writing, no workaround exists other than ensuring only trusted images are used.\n\n### References\nhttps://github.com/containerd/containerd/security/advisories/GHSA-5ffw-gxpp-mxpf\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the CRI-O repo](http://github.com/cri-o/cri-o/issues)\n* To make a report, email your vulnerability to the private\n[cncf-crio-security@lists.cncf.io](mailto:cncf-crio-security@lists.cncf.io) list\nwith the security details and the details expected for [all CRI-O bug\nreports](https://github.com/cri-o/cri-o/blob/main/.github/ISSUE_TEMPLATE/bug-report.yml).\n\n### Credits\nDisclosed by Ada Logics in a security audit sponsored by CNCF and facilitated by OSTIF.\n",
"id": "GHSA-fcm2-6c3h-pg6j",
"modified": "2023-07-24T19:33:40Z",
"published": "2022-06-06T21:50:21Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/cri-o/cri-o/security/advisories/GHSA-fcm2-6c3h-pg6j"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-1708"
},
{
"type": "WEB",
"url": "https://github.com/cri-o/cri-o/commit/f032cf649ecc7e0c46718bd9e7814bfb317cb544"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2085361"
},
{
"type": "PACKAGE",
"url": "https://github.com/cri-o/cri-o"
}
],
"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": "Node DOS by way of memory exhaustion through ExecSync request in CRI-O"
}
GHSA-FCVX-J7F9-JVWV
Vulnerability from github – Published: 2022-05-24 17:19 – Updated: 2022-05-24 17:19
VLAI
Details
An issue was discovered in Foxit Reader and PhantomPDF before 9.7.2. It allows resource consumption via crafted cross-reference stream data.
{
"affected": [],
"aliases": [
"CVE-2020-13808"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-06-04T15:15:00Z",
"severity": "MODERATE"
},
"details": "An issue was discovered in Foxit Reader and PhantomPDF before 9.7.2. It allows resource consumption via crafted cross-reference stream data.",
"id": "GHSA-fcvx-j7f9-jvwv",
"modified": "2022-05-24T17:19:19Z",
"published": "2022-05-24T17:19:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-13808"
},
{
"type": "WEB",
"url": "https://www.foxitsoftware.com/support/security-bulletins.php"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-FF3W-9CGH-8H6X
Vulnerability from github – Published: 2023-08-10 15:30 – Updated: 2024-04-04 06:47
VLAI
Details
Adobe XMP Toolkit versions 2022.06 is affected by a Uncontrolled Resource Consumption vulnerability. An unauthenticated attacker could leverage this vulnerability to achieve an application denial-of-service in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
Severity
5.5 (Medium)
{
"affected": [],
"aliases": [
"CVE-2023-38210"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-08-10T14:15:12Z",
"severity": "MODERATE"
},
"details": "Adobe XMP Toolkit versions 2022.06 is affected by a Uncontrolled Resource Consumption vulnerability. An unauthenticated attacker could leverage this vulnerability to achieve an application denial-of-service in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.",
"id": "GHSA-ff3w-9cgh-8h6x",
"modified": "2024-04-04T06:47:24Z",
"published": "2023-08-10T15:30:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-38210"
},
{
"type": "WEB",
"url": "https://helpx.adobe.com/security/products/xmpcore/apsb23-45.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-FF6R-5JWM-8292
Vulnerability from github – Published: 2018-07-24 19:51 – Updated: 2023-09-11 21:52
VLAI
Summary
Regular Expression Denial of Service in no-case
Details
Affected versions of no-case are vulnerable to a regular expression denial of service when parsing untrusted user input.
Recommendation
Update to version 2.3.2 or later.
Severity
7.5 (High)
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "no-case"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.3.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2017-16099"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2020-06-16T21:34:26Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "Affected versions of `no-case` are vulnerable to a regular expression denial of service when parsing untrusted user input.\n\n\n## Recommendation\n\nUpdate to version 2.3.2 or later.",
"id": "GHSA-ff6r-5jwm-8292",
"modified": "2023-09-11T21:52:22Z",
"published": "2018-07-24T19:51:16Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-16099"
},
{
"type": "WEB",
"url": "https://github.com/blakeembrey/no-case/issues/17"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-ff6r-5jwm-8292"
},
{
"type": "WEB",
"url": "https://www.npmjs.com/advisories/529"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "Regular Expression Denial of Service in no-case"
}
Mitigation
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
Mitigation
Architecture and Design
- 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
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
Mitigation
Implementation
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.