GHSA-55JH-84JV-8MX8
Vulnerability from github – Published: 2025-12-12 20:20 – Updated: 2025-12-20 05:00
VLAI
Summary
Lightning Flow Scanner Vulnerable to Code Injection via Unsafe Use of `new Function()` in APIVersion Rule
Details
Impact
The APIVersion rule uses new Function() to evaluate expression strings. A malicious crafted flow metadata file can cause arbitrary JavaScript execution during scanning. An attacker could execute arbitrary JavaScript during a scan by supplying a malicious expression within rule configuration or crafted flow metadata. This could compromise developer machines, CI runners, or editor environments.
Patches
The patch removes all uses of new Function() and replaces them with a safer parser. It now validates operators (>, >=,<,<=,==`) and performs numeric comparisons without evaluating untrusted JavaScript.
version: core-v6.10.6, version vsx:: v2.4.4 version app:: v3.1.0
Work around
// --- Handle APIVersion rule separately to avoid unsafe-eval in the core library ---
const apiVersionConfig = ruleConfig.rules.APIVersion;
if (apiVersionConfig) {
delete ruleConfig.rules.APIVersion;
}
// Manually evaluate the APIVersion rule, if it was configured.
if (apiVersionConfig) {
const flowApiVer = this.currentFlow.apiVersion || this.currentFlow.xmlData?.apiVersion;
const apiVersionRuleDef = allRules.find(r => r.name === "APIVersion");
// Determine the required expression (e.g. ">=58").
let requiredExpr;
if (apiVersionConfig.expression) {
requiredExpr = apiVersionConfig.expression;
} else if (apiVersionConfig.threshold != null) {
requiredExpr = `>=${apiVersionConfig.threshold}`;
}
if (requiredExpr) {
const minVer = parseInt(requiredExpr.replace(/[^0-9]/g, ""), 10);
const operator = requiredExpr.replace(/[0-9]/g, "").trim();
const operators = {
">=": (a, b) => a < b,
"<": (a, b) => a >= b,
">": (a, b) => a <= b,
"<=": (a, b) => a > b,
"==": (a, b) => a !== b,
"=": (a, b) => a !== b
};
const violation = operators[operator] ? operators[operator](flowApiVer, minVer) : flowApiVer < minVer;
if (violation) {
// Craft a result object that mimics the core scanner output so downstream logic remains unchanged.
const manualScanResult = [{
flow: parsedFlow,
ruleResults: [{
ruleName: "APIVersion",
ruleDefinition: {
description: apiVersionRuleDef?.description || "API Version check",
label: apiVersionRuleDef?.label || "APIVersion"
},
occurs: true,
severity: apiVersionConfig.severity,
details: [{
name: String(flowApiVer),
type: "apiVersion",
expression: requiredExpr
}]
}]
}];
results.push(...this.processScanResults(manualScanResult));
}
}
}
Severity
8.4 (High)
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "lightning-flow-scanner"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.10.6"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-67750"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": true,
"github_reviewed_at": "2025-12-12T20:20:34Z",
"nvd_published_at": "2025-12-12T21:15:59Z",
"severity": "HIGH"
},
"details": "### Impact\nThe APIVersion rule uses `new Function()` to evaluate expression strings. A malicious crafted flow metadata file can cause arbitrary JavaScript execution during scanning. An attacker could execute arbitrary JavaScript during a scan by supplying a malicious expression within rule configuration or crafted flow metadata. This could compromise developer machines, CI runners, or editor environments.\n\n### Patches\nThe patch removes all uses of `new Function()` and replaces them with a safer parser. It now validates operators (`\u003e`, \u003e=`, `\u003c`, `\u003c=`, `==`) and performs numeric comparisons without evaluating untrusted JavaScript.\n\n**version:** core-v6.10.6,\n**version vsx:**: v2.4.4\n**version app:**: v3.1.0\n\n### Work around\n\n```\n// --- Handle APIVersion rule separately to avoid unsafe-eval in the core library ---\n const apiVersionConfig = ruleConfig.rules.APIVersion;\n if (apiVersionConfig) {\n delete ruleConfig.rules.APIVersion;\n }\n\n// Manually evaluate the APIVersion rule, if it was configured.\n if (apiVersionConfig) {\n const flowApiVer = this.currentFlow.apiVersion || this.currentFlow.xmlData?.apiVersion;\n const apiVersionRuleDef = allRules.find(r =\u003e r.name === \"APIVersion\");\n\n // Determine the required expression (e.g. \"\u003e=58\").\n let requiredExpr;\n if (apiVersionConfig.expression) {\n requiredExpr = apiVersionConfig.expression;\n } else if (apiVersionConfig.threshold != null) {\n requiredExpr = `\u003e=${apiVersionConfig.threshold}`;\n }\n\n if (requiredExpr) {\n const minVer = parseInt(requiredExpr.replace(/[^0-9]/g, \"\"), 10);\n const operator = requiredExpr.replace(/[0-9]/g, \"\").trim();\n const operators = {\n \"\u003e=\": (a, b) =\u003e a \u003c b,\n \"\u003c\": (a, b) =\u003e a \u003e= b,\n \"\u003e\": (a, b) =\u003e a \u003c= b,\n \"\u003c=\": (a, b) =\u003e a \u003e b,\n \"==\": (a, b) =\u003e a !== b,\n \"=\": (a, b) =\u003e a !== b\n };\n const violation = operators[operator] ? operators[operator](flowApiVer, minVer) : flowApiVer \u003c minVer;\n\n if (violation) {\n // Craft a result object that mimics the core scanner output so downstream logic remains unchanged.\n const manualScanResult = [{\n flow: parsedFlow,\n ruleResults: [{\n ruleName: \"APIVersion\",\n ruleDefinition: {\n description: apiVersionRuleDef?.description || \"API Version check\",\n label: apiVersionRuleDef?.label || \"APIVersion\"\n },\n occurs: true,\n severity: apiVersionConfig.severity,\n details: [{\n name: String(flowApiVer),\n type: \"apiVersion\",\n expression: requiredExpr\n }]\n }]\n }];\n results.push(...this.processScanResults(manualScanResult));\n }\n }\n }\n\n```",
"id": "GHSA-55jh-84jv-8mx8",
"modified": "2025-12-20T05:00:37Z",
"published": "2025-12-12T20:20:34Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/Flow-Scanner/lightning-flow-scanner/security/advisories/GHSA-55jh-84jv-8mx8"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-67750"
},
{
"type": "WEB",
"url": "https://github.com/Flow-Scanner/lightning-flow-scanner/commit/10f64a5eb193d8a777e453b25e910144e4540795"
},
{
"type": "PACKAGE",
"url": "https://github.com/Flow-Scanner/lightning-flow-scanner"
},
{
"type": "WEB",
"url": "https://github.com/Flow-Scanner/lightning-flow-scanner/releases/tag/core-v6.10.6"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Lightning Flow Scanner Vulnerable to Code Injection via Unsafe Use of `new Function()` in APIVersion Rule"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…