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.
5379 vulnerabilities reference this CWE, most recent first.
GHSA-C8F8-J53J-393C
Vulnerability from github – Published: 2024-06-25 12:30 – Updated: 2024-06-25 12:30OnCell G3470A-LTE Series firmware versions v1.7.7 and prior have been identified as vulnerable due to a lack of neutralized inputs in IPSec configuration. An attacker could modify the intended commands sent to target functions, which could cause malicious users to execute unauthorized commands.
{
"affected": [],
"aliases": [
"CVE-2024-4639"
],
"database_specific": {
"cwe_ids": [
"CWE-77"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-06-25T10:15:19Z",
"severity": "HIGH"
},
"details": "OnCell G3470A-LTE Series firmware versions v1.7.7 and prior have been identified as vulnerable due to a lack of neutralized inputs in IPSec configuration. An attacker could modify the intended commands sent to target functions, which could cause malicious users to execute unauthorized commands.",
"id": "GHSA-c8f8-j53j-393c",
"modified": "2024-06-25T12:30:55Z",
"published": "2024-06-25T12:30:55Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-4639"
},
{
"type": "WEB",
"url": "https://www.moxa.com/en/support/product-support/security-advisory/mpsa-242550-oncell-g3470a-lte-series-multiple-web-application-vulnerabilities"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-C8FH-XHVF-2GP8
Vulnerability from github – Published: 2022-05-17 03:13 – Updated: 2022-05-17 03:13The server in IBM Tivoli Storage Manager FastBack 6.1 before 6.1.12 allows remote attackers to execute arbitrary commands via unspecified vectors, a different vulnerability than CVE-2015-1938.
{
"affected": [],
"aliases": [
"CVE-2015-1986"
],
"database_specific": {
"cwe_ids": [
"CWE-77"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2015-06-30T15:59:00Z",
"severity": "HIGH"
},
"details": "The server in IBM Tivoli Storage Manager FastBack 6.1 before 6.1.12 allows remote attackers to execute arbitrary commands via unspecified vectors, a different vulnerability than CVE-2015-1938.",
"id": "GHSA-c8fh-xhvf-2gp8",
"modified": "2022-05-17T03:13:20Z",
"published": "2022-05-17T03:13:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-1986"
},
{
"type": "WEB",
"url": "http://www-01.ibm.com/support/docview.wss?uid=swg21959398"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/75461"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id/1032773"
},
{
"type": "WEB",
"url": "http://www.zerodayinitiative.com/advisories/ZDI-15-274"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-C8G6-QRWH-M3VP
Vulnerability from github – Published: 2025-10-21 20:25 – Updated: 2025-10-30 14:56Impact
A vulnerability was identified in NeuVector, where the enforcer used environment variables CLUSTER_RPC_PORT and CLUSTER_LAN_PORT to generate a command to be executed via popen, without first sanitising their values.
The entry process of the enforcer container is the monitor process. When the enforcer container stops, the monitor process checks whether the consul subprocess has exited. To perform this check, the monitor process uses the popen function to execute a shell command that determines whether the ports used by the consul subprocess are still active.
The values of environment variables CLUSTER_RPC_PORT and CLUSTER_LAN_PORT are used directly to compose shell commands via popen without validation or sanitization. This behavior could allow a malicious user to inject malicious commands through these variables within the enforcer container.
In the patched version, the monitor process validates the values of CLUSTER_RPC_PORT and CLUSTER_LAN_PORT to ensure they contain only valid port numbers before invoking the popen command.
If validation fails, the monitor process exits immediately, causing the enforcer container to terminate. This prevents the execution of any injected or malicious commands.
Patches
Patched versions include release v5.4.7 and above.
Workarounds
There is no workaround for this issue. Users are recommended to upgrade, as soon as possible, to a version of NeuVector that contains the fix.
References
If you have any questions or comments about this advisory: - Reach out to the SUSE Rancher Security team for security related inquiries. - Open an issue in the NeuVector repository. - Verify with our support matrix and product support lifecycle.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/neuvector/neuvector"
},
"ranges": [
{
"events": [
{
"introduced": "5.3.0"
},
{
"fixed": "5.3.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 5.4.6"
},
"package": {
"ecosystem": "Go",
"name": "github.com/neuvector/neuvector"
},
"ranges": [
{
"events": [
{
"introduced": "5.4.0"
},
{
"fixed": "5.4.7"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/neuvector/neuvector"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-20230727023453-1c4957d53911"
},
{
"fixed": "0.0.0-20251020133207-084a437033b4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-54469"
],
"database_specific": {
"cwe_ids": [
"CWE-120",
"CWE-77",
"CWE-78"
],
"github_reviewed": true,
"github_reviewed_at": "2025-10-21T20:25:11Z",
"nvd_published_at": "2025-10-30T10:15:34Z",
"severity": "CRITICAL"
},
"details": "### Impact\nA vulnerability was identified in NeuVector, where the enforcer used environment variables `CLUSTER_RPC_PORT` and `CLUSTER_LAN_PORT` to generate a command to be executed via `popen`, without first sanitising their values.\n\nThe entry process of the enforcer container is the monitor process. When the enforcer container stops, the monitor process checks whether the consul subprocess has exited. To perform this check, the monitor process uses the `popen` function to execute a shell command that determines whether the ports used by the consul subprocess are still active.\n\nThe values of environment variables `CLUSTER_RPC_PORT` and `CLUSTER_LAN_PORT` are used directly to compose shell commands via popen without validation or sanitization. This behavior could allow a malicious user to inject malicious commands through these variables within the enforcer container.\n\nIn the patched version, the monitor process validates the values of `CLUSTER_RPC_PORT` and `CLUSTER_LAN_PORT` to ensure they contain only valid port numbers before invoking the `popen` command.\n\nIf validation fails, the monitor process exits immediately, causing the enforcer container to terminate. This prevents the execution of any injected or malicious commands.\n\n\n### Patches\nPatched versions include release `v5.4.7` and above.\n\n### Workarounds\nThere is no workaround for this issue. Users are recommended to upgrade, as soon as possible, to a version of NeuVector that contains the fix.\n\n### References\nIf you have any questions or comments about this advisory:\n- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.\n- Open an issue in the [NeuVector](https://github.com/neuvector/neuvector/issues/new/choose) repository.\n- Verify with our [support matrix](https://www.suse.com/suse-neuvector/support-matrix/all-supported-versions/neuvector-v-all-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/#suse-security).",
"id": "GHSA-c8g6-qrwh-m3vp",
"modified": "2025-10-30T14:56:42Z",
"published": "2025-10-21T20:25:11Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/neuvector/neuvector/security/advisories/GHSA-c8g6-qrwh-m3vp"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-54469"
},
{
"type": "WEB",
"url": "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-54469"
},
{
"type": "PACKAGE",
"url": "https://github.com/neuvector/neuvector"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "NeuVector Enforcer is vulnerable to Command Injection and Buffer overflow"
}
GHSA-C8H4-QPCX-5G8G
Vulnerability from github – Published: 2022-05-17 03:33 – Updated: 2025-04-12 12:47BitTorrent Sync allows remote attackers to execute arbitrary commands via a crafted btsync: link.
{
"affected": [],
"aliases": [
"CVE-2015-2846"
],
"database_specific": {
"cwe_ids": [
"CWE-77"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2015-04-13T14:59:00Z",
"severity": "HIGH"
},
"details": "BitTorrent Sync allows remote attackers to execute arbitrary commands via a crafted btsync: link.",
"id": "GHSA-c8h4-qpcx-5g8g",
"modified": "2025-04-12T12:47:00Z",
"published": "2022-05-17T03:33:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-2846"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/73906"
},
{
"type": "WEB",
"url": "http://www.zerodayinitiative.com/advisories/ZDI-15-115"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-C8HM-V577-P7V7
Vulnerability from github – Published: 2022-09-01 00:00 – Updated: 2022-09-08 00:00All versions of iSTAR Ultra prior to version 6.8.9.CU01are vulnerable to a command injection that could allow an unauthenticated user root access to the system.
{
"affected": [],
"aliases": [
"CVE-2022-21941"
],
"database_specific": {
"cwe_ids": [
"CWE-77"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-08-31T16:15:00Z",
"severity": "CRITICAL"
},
"details": "All versions of iSTAR Ultra prior to version 6.8.9.CU01are vulnerable to a command injection that could allow an unauthenticated user root access to the system.",
"id": "GHSA-c8hm-v577-p7v7",
"modified": "2022-09-08T00:00:32Z",
"published": "2022-09-01T00:00:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-21941"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/uscert/ics/advisories/icsa-22-242-11"
},
{
"type": "WEB",
"url": "https://www.johnsoncontrols.com/cyber-solutions/security-advisories"
}
],
"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"
}
]
}
GHSA-C8JJ-4GRW-46CF
Vulnerability from github – Published: 2021-12-27 00:01 – Updated: 2022-01-05 00:01NETGEAR XR1000 devices before 1.0.0.58 are affected by command injection by an unauthenticated attacker.
{
"affected": [],
"aliases": [
"CVE-2021-45513"
],
"database_specific": {
"cwe_ids": [
"CWE-77"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-12-26T01:15:00Z",
"severity": "CRITICAL"
},
"details": "NETGEAR XR1000 devices before 1.0.0.58 are affected by command injection by an unauthenticated attacker.",
"id": "GHSA-c8jj-4grw-46cf",
"modified": "2022-01-05T00:01:40Z",
"published": "2021-12-27T00:01:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-45513"
},
{
"type": "WEB",
"url": "https://kb.netgear.com/000064149/Security-Advisory-for-Command-Injection-on-XR1000-PSV-2021-0010"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-C8QX-8JR7-QRJ4
Vulnerability from github – Published: 2022-05-24 17:36 – Updated: 2022-05-24 17:36A command injection vulnerability in Trend Micro InterScan Web Security Virtual Appliance 6.5 SP2, with the improved password hashing method enabled, could allow an unauthenticated attacker to execute certain commands by providing a manipulated password.
{
"affected": [],
"aliases": [
"CVE-2020-8466"
],
"database_specific": {
"cwe_ids": [
"CWE-77"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-12-17T21:15:00Z",
"severity": "CRITICAL"
},
"details": "A command injection vulnerability in Trend Micro InterScan Web Security Virtual Appliance 6.5 SP2, with the improved password hashing method enabled, could allow an unauthenticated attacker to execute certain commands by providing a manipulated password.",
"id": "GHSA-c8qx-8jr7-qrj4",
"modified": "2022-05-24T17:36:48Z",
"published": "2022-05-24T17:36:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-8466"
},
{
"type": "WEB",
"url": "https://sec-consult.com/vulnerability-lab/advisory/multiple-critical-vulnerabilities-in-trend-micro-interscan-web-security-virtual-appliance"
},
{
"type": "WEB",
"url": "https://success.trendmicro.com/solution/000283077"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-C969-5X3P-VQ3V
Vulnerability from github – Published: 2026-06-18 14:25 – Updated: 2026-06-18 14:25Summary
The email search tool in src/praisonai-agents/praisonaiagents/tools/email_tools.py constructs IMAP SEARCH commands by interpolating LLM-controlled parameters (from_addr, subject, query) directly into IMAP protocol strings using f-string formatting with double-quote delimiters. An attacker who can influence the arguments to the search_emails or reply_email tool (via crafted agent prompts) can inject arbitrary IMAP commands, potentially exfiltrating email data from other folders, deleting emails, or performing other unauthorized IMAP operations.
Details
Vulnerable code (lines 493–502):
criteria = []
if from_addr:
criteria.append(f'FROM "{from_addr}"')
if subject:
criteria.append(f'SUBJECT "{subject}"')
if query:
criteria.append(f'TEXT "{query}"')
if not criteria:
criteria.append("ALL")
search_str = " ".join(criteria)
status, data = mail.search(None, search_str)
The from_addr, subject, and query parameters originate from LLM tool call arguments (the search_emails public function at line 665). These values flow through without any sanitization or escaping. The double-quote (") characters in these parameters allow breaking out of the IMAP SEARCH quoted string context.
Additional injection points:
- Line 416: mail.search(None, f'HEADER Message-ID "{search_id}"')
- Line 447: Same pattern in _smtp_reply_email
- Line 542: Same pattern in _smtp_archive_email
The search_id / message_id parameter in these functions is also LLM-controlled via the reply_email and archive_email public tool functions.
Reachability: The search_emails, reply_email, and archive_email functions are exposed as agent tools. They are reachable when an agent is configured with email tools (EMAIL_ADDRESS + EMAIL_PASSWORD environment variables set). This is a documented deployment scenario for email-capable agents.
PoC
Setup: Requires an IMAP server (not run here — this is a static proof). The vulnerability is demonstrated by tracing the data flow.
Positive trigger — IMAP injection via search_emails:
An LLM agent processing a crafted prompt calls:
search_emails(from_addr='user@example.com" LOGOUT')
This produces the IMAP command:
SEARCH FROM "user@example.com" LOGOUT"
The LOGOUT command is injected after the prematurely closed quoted string, causing the IMAP connection to be terminated.
More severe injection — exfiltrate emails from another folder:
search_emails(query='" SEARCH RETURN (MIN) ALL')
Produces: TEXT "" SEARCH RETURN (MIN) ALL" — injects a secondary SEARCH command.
Negative control — legitimate search:
search_emails(from_addr='user@example.com')
Produces: FROM "user@example.com" — correct, no injection.
Cleanup: No persistent changes for read-only injection. For destructive injection (DELETE, EXPUNGE), impact persists.
Impact
An attacker who can craft prompts that cause an LLM agent to call search_emails with injection payloads can:
- Terminate IMAP connections (denial of service)
- Inject arbitrary IMAP commands — including LIST (enumerate folders), SELECT (switch folders), FETCH (read emails from other mailboxes), STORE (modify flags), COPY/MOVE (move emails), DELETE/EXPUNGE (permanently delete emails)
- Exfiltrate email contents from folders the user did not intend to expose to the agent
- Permanently delete emails via injected DELETE + EXPUNGE commands
The attack requires the IMAP backend to be configured (EMAIL_ADDRESS + EMAIL_PASSWORD env vars), which is a documented and common deployment for email-capable agents.
Suggested remediation
- Escape double-quote characters in IMAP parameters. Per RFC 3501, literal strings use
{n}\r\nformat or quoted strings with\escaping:
def _escape_imap_string(s: str) -> str:
"""Escape a string for safe use in IMAP quoted strings."""
# Use IMAP literal syntax for safety: {length}\r\n<data>
encoded = s.encode('utf-8')
return f'{{{len(encoded)}}}\r\n{encoded}'
-
Use IMAP literal syntax (
{n}\r\ndata) instead of quoted strings for all user-controlled parameters. This prevents any injection regardless of content. -
Apply the escaping to all IMAP search criteria parameters:
from_addr,subject,query, andsearch_id/message_id.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.6.48"
},
"package": {
"ecosystem": "PyPI",
"name": "praisonaiagents"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.6.59"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-20",
"CWE-77"
],
"github_reviewed": true,
"github_reviewed_at": "2026-06-18T14:25:03Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "## Summary\n\nThe email search tool in `src/praisonai-agents/praisonaiagents/tools/email_tools.py` constructs IMAP SEARCH commands by interpolating LLM-controlled parameters (from_addr, subject, query) directly into IMAP protocol strings using f-string formatting with double-quote delimiters. An attacker who can influence the arguments to the `search_emails` or `reply_email` tool (via crafted agent prompts) can inject arbitrary IMAP commands, potentially exfiltrating email data from other folders, deleting emails, or performing other unauthorized IMAP operations.\n## Details\n\n**Vulnerable code (lines 493\u2013502):**\n```python\ncriteria = []\nif from_addr:\n criteria.append(f\u0027FROM \"{from_addr}\"\u0027)\nif subject:\n criteria.append(f\u0027SUBJECT \"{subject}\"\u0027)\nif query:\n criteria.append(f\u0027TEXT \"{query}\"\u0027)\nif not criteria:\n criteria.append(\"ALL\")\nsearch_str = \" \".join(criteria)\nstatus, data = mail.search(None, search_str)\n```\n\nThe `from_addr`, `subject`, and `query` parameters originate from LLM tool call arguments (the `search_emails` public function at line 665). These values flow through without any sanitization or escaping. The double-quote (`\"`) characters in these parameters allow breaking out of the IMAP SEARCH quoted string context.\n\n**Additional injection points:**\n- Line 416: `mail.search(None, f\u0027HEADER Message-ID \"{search_id}\"\u0027)`\n- Line 447: Same pattern in `_smtp_reply_email`\n- Line 542: Same pattern in `_smtp_archive_email`\n\nThe `search_id` / `message_id` parameter in these functions is also LLM-controlled via the `reply_email` and `archive_email` public tool functions.\n\n**Reachability:** The `search_emails`, `reply_email`, and `archive_email` functions are exposed as agent tools. They are reachable when an agent is configured with email tools (EMAIL_ADDRESS + EMAIL_PASSWORD environment variables set). This is a documented deployment scenario for email-capable agents.\n\n## PoC\n\n**Setup:** Requires an IMAP server (not run here \u2014 this is a static proof). The vulnerability is demonstrated by tracing the data flow.\n\n**Positive trigger \u2014 IMAP injection via `search_emails`:**\nAn LLM agent processing a crafted prompt calls:\n```python\nsearch_emails(from_addr=\u0027user@example.com\" LOGOUT\u0027)\n```\nThis produces the IMAP command:\n```\nSEARCH FROM \"user@example.com\" LOGOUT\"\n```\nThe `LOGOUT` command is injected after the prematurely closed quoted string, causing the IMAP connection to be terminated.\n\n**More severe injection \u2014 exfiltrate emails from another folder:**\n```python\nsearch_emails(query=\u0027\" SEARCH RETURN (MIN) ALL\u0027)\n```\nProduces: `TEXT \"\" SEARCH RETURN (MIN) ALL\"` \u2014 injects a secondary SEARCH command.\n\n**Negative control \u2014 legitimate search:**\n```python\nsearch_emails(from_addr=\u0027user@example.com\u0027)\n```\nProduces: `FROM \"user@example.com\"` \u2014 correct, no injection.\n\n**Cleanup:** No persistent changes for read-only injection. For destructive injection (DELETE, EXPUNGE), impact persists.\n\n## Impact\n\nAn attacker who can craft prompts that cause an LLM agent to call `search_emails` with injection payloads can:\n\n- **Terminate IMAP connections** (denial of service)\n- **Inject arbitrary IMAP commands** \u2014 including LIST (enumerate folders), SELECT (switch folders), FETCH (read emails from other mailboxes), STORE (modify flags), COPY/MOVE (move emails), DELETE/EXPUNGE (permanently delete emails)\n- **Exfiltrate email contents** from folders the user did not intend to expose to the agent\n- **Permanently delete emails** via injected DELETE + EXPUNGE commands\n\nThe attack requires the IMAP backend to be configured (EMAIL_ADDRESS + EMAIL_PASSWORD env vars), which is a documented and common deployment for email-capable agents.\n\n## Suggested remediation\n\n1. **Escape double-quote characters** in IMAP parameters. Per RFC 3501, literal strings use `{n}\\r\\n` format or quoted strings with `\\` escaping:\n```python\ndef _escape_imap_string(s: str) -\u003e str:\n \"\"\"Escape a string for safe use in IMAP quoted strings.\"\"\"\n # Use IMAP literal syntax for safety: {length}\\r\\n\u003cdata\u003e\n encoded = s.encode(\u0027utf-8\u0027)\n return f\u0027{{{len(encoded)}}}\\r\\n{encoded}\u0027\n```\n\n2. Use IMAP literal syntax (`{n}\\r\\ndata`) instead of quoted strings for all user-controlled parameters. This prevents any injection regardless of content.\n\n3. Apply the escaping to all IMAP search criteria parameters: `from_addr`, `subject`, `query`, and `search_id`/`message_id`.",
"id": "GHSA-c969-5x3p-vq3v",
"modified": "2026-06-18T14:25:03Z",
"published": "2026-06-18T14:25:03Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-c969-5x3p-vq3v"
},
{
"type": "PACKAGE",
"url": "https://github.com/MervinPraison/PraisonAI"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "PraisonAI: IMAP Command Injection via Unsanitized Email Search Parameters"
}
GHSA-C969-QWM2-PF77
Vulnerability from github – Published: 2025-09-02 15:31 – Updated: 2025-09-02 21:30Wavlink WN535K3 20191010 was found to contain a command injection vulnerability in the set_sys_adm function via the username parameter. This vulnerability allows attackers to execute arbitrary commands via a crafted request.
{
"affected": [],
"aliases": [
"CVE-2025-50757"
],
"database_specific": {
"cwe_ids": [
"CWE-77"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-09-02T15:15:32Z",
"severity": "MODERATE"
},
"details": "Wavlink WN535K3 20191010 was found to contain a command injection vulnerability in the set_sys_adm function via the username parameter. This vulnerability allows attackers to execute arbitrary commands via a crafted request.",
"id": "GHSA-c969-qwm2-pf77",
"modified": "2025-09-02T21:30:57Z",
"published": "2025-09-02T15:31:08Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-50757"
},
{
"type": "WEB",
"url": "https://github.com/Summermu/VulnForIoT/tree/main/Wavlink_WN535K3/set_sys_adm_username/readme.md"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-C96R-89XW-Q4PV
Vulnerability from github – Published: 2022-05-24 17:45 – Updated: 2022-07-11 00:00A command injection on the /admin/broadcast.php script of Invigo Automatic Device Management (ADM) through 5.0 allows remote authenticated attackers to execute arbitrary PHP code on the server as the user running the application.
{
"affected": [],
"aliases": [
"CVE-2020-10580"
],
"database_specific": {
"cwe_ids": [
"CWE-77"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-03-25T20:15:00Z",
"severity": "HIGH"
},
"details": "A command injection on the /admin/broadcast.php script of Invigo Automatic Device Management (ADM) through 5.0 allows remote authenticated attackers to execute arbitrary PHP code on the server as the user running the application.",
"id": "GHSA-c96r-89xw-q4pv",
"modified": "2022-07-11T00:00:25Z",
"published": "2022-05-24T17:45:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-10580"
},
{
"type": "WEB",
"url": "https://cwe.mitre.org/data/definitions/77.html"
},
{
"type": "WEB",
"url": "https://www.on-x.com/sites/default/files/security_advisory_-_multiple_vulnerabilities_-_invigo_adm.pdf"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
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.