n8n Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n8n-io | n8n | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| N8n | N8n | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-49mx-fj45-q3p6 | n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.396% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:n8n:n8n:*:*:*:*:*:node.js:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
N8n
N8n n8n |
|
| Vendors & Products |
N8n
N8n n8n |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | n8n is an open source workflow automation platform. From version 1.65.0 to before 1.114.3, the use of Buffer.allocUnsafe() and Buffer.allocUnsafeSlow() in the task runner allowed untrusted code to allocate uninitialized memory. Such uninitialized buffers could contain residual data from within the same Node.js process (for example, data from prior requests, tasks, secrets, or tokens), resulting in potential information disclosure. This issue has been patched in version 1.114.3. | |
| Title | n8n Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner | |
| Weaknesses | CWE-200 CWE-668 |
|
| References |
| |
| Metrics |
cvssV3_1
|