Lightning Flow Scanner is Vulnerable to Code Injection via Unsafe Use of new Function() in APIVersion Rule
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Flow-Scanner | lightning-flow-scanner | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Flow-scanner | Lightning-flow-scanner | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-55jh-84jv-8mx8 | Lightning Flow Scanner Vulnerable to Code Injection via Unsafe Use of `new Function()` in APIVersion Rule |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.207% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Flow-scanner
Flow-scanner lightning-flow-scanner |
|
| Vendors & Products |
Flow-scanner
Flow-scanner lightning-flow-scanner |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Lightning Flow Scanner provides a A CLI plugin, VS Code Extension and GitHub Action for analysis and optimization of Salesforce Flows. Versions 6.10.5 and below allow a maliciously crafted flow metadata file to cause arbitrary JavaScript execution during scanning. The APIVersion rule uses new Function() to evaluate expression strings, enabling an attacker to supply a malicious expression within rule configuration or crafted flow metadata. This could compromise developer machines, CI runners, or editor environments. This issue is fixed in version 6.10.6. | |
| Title | Lightning Flow Scanner is Vulnerable to Code Injection via Unsafe Use of new Function() in APIVersion Rule | |
| Weaknesses | CWE-94 | |
| References |
| |
| Metrics |
cvssV3_1
|