CWE-306
AllowedMissing Authentication for Critical Function
Abstraction: Base · Status: Draft
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
3495 vulnerabilities reference this CWE, most recent first.
GHSA-C4GW-5QV5-6333
Vulnerability from github – Published: 2022-05-13 01:23 – Updated: 2022-05-13 01:23An issue was discovered on D-Link DIR-878 1.12B01 devices. Because strncpy is misused, there is a stack-based buffer overflow vulnerability that does not require authentication via the HNAP_AUTH HTTP header.
{
"affected": [],
"aliases": [
"CVE-2019-9125"
],
"database_specific": {
"cwe_ids": [
"CWE-306",
"CWE-787"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-02-25T05:29:00Z",
"severity": "CRITICAL"
},
"details": "An issue was discovered on D-Link DIR-878 1.12B01 devices. Because strncpy is misused, there is a stack-based buffer overflow vulnerability that does not require authentication via the HNAP_AUTH HTTP header.",
"id": "GHSA-c4gw-5qv5-6333",
"modified": "2022-05-13T01:23:02Z",
"published": "2022-05-13T01:23:02Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-9125"
},
{
"type": "WEB",
"url": "https://github.com/WhooAmii/whooamii.github.io/blob/master/2018/DIR-878/overflow1.md"
},
{
"type": "WEB",
"url": "https://github.com/WhooAmii/whooamii.github.io/blob/master/2018/DIR-878/overflow2.md"
}
],
"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-C4HV-PJJQ-493X
Vulnerability from github – Published: 2026-04-22 15:31 – Updated: 2026-04-22 15:31Inadequate access control in the registration process in Fullstep V5, which could allow unauthenticated users to obtain a valid JWT token with which to interact with authenticated API resources. Successful exploitation of this vulnerability could allow an unauthenticated attacker to compromise the confidentiality of the affected resource, provided they have a valid token with which to interact with the API.
{
"affected": [],
"aliases": [
"CVE-2026-5749"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-22T14:17:05Z",
"severity": "HIGH"
},
"details": "Inadequate access control in the registration process in Fullstep V5, which could allow unauthenticated users to obtain a valid JWT token with which to interact with authenticated API resources. Successful exploitation of this vulnerability could allow an unauthenticated attacker to compromise the confidentiality of the affected resource, provided they have a valid token with which to interact with the API.",
"id": "GHSA-c4hv-pjjq-493x",
"modified": "2026-04-22T15:31:44Z",
"published": "2026-04-22T15:31:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-5749"
},
{
"type": "WEB",
"url": "https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-fullstep"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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-C4MM-2HH3-RQRF
Vulnerability from github – Published: 2025-08-27 12:30 – Updated: 2025-08-27 12:30The system exposes several endpoints, typically including "/int/" in their path, that should be restricted to internal services, but are instead publicly accessible without authentication to any host able to reach the application server on port 443/tcp.
{
"affected": [],
"aliases": [
"CVE-2025-30037"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-08-27T11:15:32Z",
"severity": "HIGH"
},
"details": "The system exposes several endpoints, typically including \"/int/\" in their path, that should be restricted to internal services, but are instead publicly accessible without authentication to any host able to reach the application server on port 443/tcp.",
"id": "GHSA-c4mm-2hh3-rqrf",
"modified": "2025-08-27T12:30:26Z",
"published": "2025-08-27T12:30:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-30037"
},
{
"type": "WEB",
"url": "https://cert.pl/en/posts/2025/08/CVE-2025-2313"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/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-C4PF-HC84-698H
Vulnerability from github – Published: 2024-11-07 18:31 – Updated: 2024-11-08 00:30An issue was discovered in Logpoint before 7.5.0. Endpoints for creating, editing, or deleting third-party authentication modules lacked proper authorization checks. This allowed unauthenticated users to register their own authentication plugins in Logpoint, resulting in unauthorized access.
{
"affected": [],
"aliases": [
"CVE-2024-48953"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-11-07T17:15:08Z",
"severity": "HIGH"
},
"details": "An issue was discovered in Logpoint before 7.5.0. Endpoints for creating, editing, or deleting third-party authentication modules lacked proper authorization checks. This allowed unauthenticated users to register their own authentication plugins in Logpoint, resulting in unauthorized access.",
"id": "GHSA-c4pf-hc84-698h",
"modified": "2024-11-08T00:30:45Z",
"published": "2024-11-07T18:31:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-48953"
},
{
"type": "WEB",
"url": "https://docs.logpoint.com/docs/whats-new-in-logpoint/en/latest"
},
{
"type": "WEB",
"url": "https://servicedesk.logpoint.com/hc/en-us/articles/21968899128221-Authentication-Bypass-using-URL-endpoints-in-the-Authentication-Modules"
},
{
"type": "WEB",
"url": "https://servicedesk.logpoint.com/hc/en-us/sections/7201103730845-Product-Security"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-C5CP-VX83-JHQX
Vulnerability from github – Published: 2026-01-02 21:11 – Updated: 2026-01-05 01:01Summary
Multiple critical API endpoints in Langflow are missing authentication controls, allowing any unauthenticated user to access sensitive user conversation data, transaction histories, and perform destructive operations including message deletion. This affects endpoints handling personal data and system operations that should require proper authorization.
Details
The vulnerability exists in three API endpoints within src/backend/base/langflow/api/v1/monitor.py that are missing the required dependencies=[Depends(get_current_active_user)] authentication dependency:
Affected Endpoints:
-
GET
/api/v1/monitor/messages(Line 61)python @router.get("/messages") # ❌ Missing authentication async def get_messages( session: DbSession, flow_id: Annotated[UUID | None, Query()] = None, session_id: Annotated[str | None, Query()] = None, # ... other parameters ) -> list[MessageResponse]: -
GET
/api/v1/monitor/transactions(Line 183)python @router.get("/transactions") # ❌ Missing authentication async def get_transactions( flow_id: Annotated[UUID, Query()], session: DbSession, params: Annotated[Params | None, Depends(custom_params)], ) -> Page[TransactionTable]: -
DELETE
/api/v1/monitor/messages/session/{session_id}(Line 165)python @router.delete("/messages/session/{session_id}", status_code=204) # ❌ Missing authentication async def delete_messages_session( session_id: str, session: DbSession, ):
Inconsistency Evidence: Other endpoints in the same file properly implement authentication:
@router.get("/messages/sessions", dependencies=[Depends(get_current_active_user)]) # ✅ Properly secured
@router.delete("/messages", status_code=204, dependencies=[Depends(get_current_active_user)]) # ✅ Properly secured
PoC
Complete reproduction steps to demonstrate the vulnerability:
Prerequisites: 1. Start a Langflow server instance 2. Ensure no authentication headers or API keys are provided
Reproduction Commands:
# 1. Access all user conversations without authentication
curl http://localhost:7860/api/v1/monitor/messages
# 2. Access transaction history without authentication
curl "http://localhost:7860/api/v1/monitor/transactions?flow_id=00000000-0000-0000-0000-000000000000"
# 3. Delete user messages by session without authentication
curl -X DELETE http://localhost:7860/api/v1/monitor/messages/session/00000000-0000-0000-0000-000000000000
Expected vs Actual Behavior:
- Expected: All requests should return 401 Unauthorized
- Actual: All requests return successful responses with sensitive data or perform destructive operations
Impact
Vulnerability Type: Broken Authentication and Authorization (OWASP Top 10 - A01:2021)
Severity: High
Who is Impacted: - All Langflow users: Personal conversation data exposed to unauthorized access - System administrators: Transaction logs disclosed
Specific Impacts: 1. Data Breach: Unauthorized access to user conversations containing potentially sensitive personal information 2. Privacy Violation: Transaction histories and user activity patterns exposed without consent 3. Data Destruction: Malicious actors can delete user conversation histories without authorization 4. Compliance Risk: Potential violations of data protection regulations (GDPR, CCPA, etc.) 5. System Intelligence: Attackers can gather information about system usage patterns and user behavior
Attack Scenarios: - Malicious users accessing proprietary conversation data - Malicious users deleting other users' conversation histories - Automated scraping of all user conversations for data harvesting - Reconnaissance attacks to understand system architecture and usage patterns
Recommended Fix: Add authentication dependencies to all affected endpoints:
@router.get("/messages", dependencies=[Depends(get_current_active_user)])
@router.get("/transactions", dependencies=[Depends(get_current_active_user)])
@router.delete("/messages/session/{session_id}", dependencies=[Depends(get_current_active_user)])
Environment:
- Langflow Version: Current main branch
- Affected Components: API v1 monitoring endpoints
- Authentication System: FastAPI dependency injection with get_current_active_user
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.6.9"
},
"package": {
"ecosystem": "PyPI",
"name": "langflow-base"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.7.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.7.0.dev44"
},
"package": {
"ecosystem": "PyPI",
"name": "langflow"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.7.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-21445"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": true,
"github_reviewed_at": "2026-01-02T21:11:50Z",
"nvd_published_at": "2026-01-02T20:16:17Z",
"severity": "HIGH"
},
"details": "### Summary\nMultiple critical API endpoints in Langflow are missing authentication controls, allowing any unauthenticated user to access sensitive user conversation data, transaction histories, and perform destructive operations including message deletion. This affects endpoints handling personal data and system operations that should require proper authorization.\n\n### Details\nThe vulnerability exists in three API endpoints within `src/backend/base/langflow/api/v1/monitor.py` that are missing the required `dependencies=[Depends(get_current_active_user)]` authentication dependency:\n\n**Affected Endpoints:**\n\n1. **GET `/api/v1/monitor/messages`** (Line 61)\n ```python\n @router.get(\"/messages\") # \u274c Missing authentication\n async def get_messages(\n session: DbSession,\n flow_id: Annotated[UUID | None, Query()] = None,\n session_id: Annotated[str | None, Query()] = None,\n # ... other parameters\n ) -\u003e list[MessageResponse]:\n ```\n\n2. **GET `/api/v1/monitor/transactions`** (Line 183)\n ```python\n @router.get(\"/transactions\") # \u274c Missing authentication\n async def get_transactions(\n flow_id: Annotated[UUID, Query()],\n session: DbSession,\n params: Annotated[Params | None, Depends(custom_params)],\n ) -\u003e Page[TransactionTable]:\n ```\n\n3. **DELETE `/api/v1/monitor/messages/session/{session_id}`** (Line 165)\n ```python\n @router.delete(\"/messages/session/{session_id}\", status_code=204) # \u274c Missing authentication\n async def delete_messages_session(\n session_id: str,\n session: DbSession,\n ):\n ```\n\n**Inconsistency Evidence:**\nOther endpoints in the same file properly implement authentication:\n```python\n@router.get(\"/messages/sessions\", dependencies=[Depends(get_current_active_user)]) # \u2705 Properly secured\n@router.delete(\"/messages\", status_code=204, dependencies=[Depends(get_current_active_user)]) # \u2705 Properly secured\n```\n\n### PoC\nComplete reproduction steps to demonstrate the vulnerability:\n\n**Prerequisites:**\n1. Start a Langflow server instance\n2. Ensure no authentication headers or API keys are provided\n\n**Reproduction Commands:**\n```bash\n# 1. Access all user conversations without authentication\ncurl http://localhost:7860/api/v1/monitor/messages\n\n# 2. Access transaction history without authentication\ncurl \"http://localhost:7860/api/v1/monitor/transactions?flow_id=00000000-0000-0000-0000-000000000000\"\n\n# 3. Delete user messages by session without authentication\ncurl -X DELETE http://localhost:7860/api/v1/monitor/messages/session/00000000-0000-0000-0000-000000000000\n```\n\n**Expected vs Actual Behavior:**\n- **Expected:** All requests should return `401 Unauthorized` \n- **Actual:** All requests return successful responses with sensitive data or perform destructive operations\n\n### Impact\n\n**Vulnerability Type:** Broken Authentication and Authorization (OWASP Top 10 - A01:2021)\n\n**Severity:** High\n\n**Who is Impacted:**\n- **All Langflow users**: Personal conversation data exposed to unauthorized access\n- **System administrators**: Transaction logs disclosed\n\n**Specific Impacts:**\n1. **Data Breach**: Unauthorized access to user conversations containing potentially sensitive personal information\n2. **Privacy Violation**: Transaction histories and user activity patterns exposed without consent\n3. **Data Destruction**: Malicious actors can delete user conversation histories without authorization\n4. **Compliance Risk**: Potential violations of data protection regulations (GDPR, CCPA, etc.)\n5. **System Intelligence**: Attackers can gather information about system usage patterns and user behavior\n\n**Attack Scenarios:**\n- Malicious users accessing proprietary conversation data\n- Malicious users deleting other users\u0027 conversation histories\n- Automated scraping of all user conversations for data harvesting\n- Reconnaissance attacks to understand system architecture and usage patterns\n\n**Recommended Fix:**\nAdd authentication dependencies to all affected endpoints:\n\n```python\n@router.get(\"/messages\", dependencies=[Depends(get_current_active_user)])\n@router.get(\"/transactions\", dependencies=[Depends(get_current_active_user)])\n@router.delete(\"/messages/session/{session_id}\", dependencies=[Depends(get_current_active_user)])\n```\n\n**Environment:**\n- Langflow Version: Current main branch\n- Affected Components: API v1 monitoring endpoints\n- Authentication System: FastAPI dependency injection with `get_current_active_user`\n\n\u003cimg width=\"1908\" height=\"1029\" alt=\"25-090901\" src=\"https://github.com/user-attachments/assets/44bd03b4-6ada-45b7-b81b-9cb83747172b\" /\u003e",
"id": "GHSA-c5cp-vx83-jhqx",
"modified": "2026-01-05T01:01:41Z",
"published": "2026-01-02T21:11:50Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/langflow-ai/langflow/security/advisories/GHSA-c5cp-vx83-jhqx"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-21445"
},
{
"type": "WEB",
"url": "https://github.com/langflow-ai/langflow/commit/3fed9fe1b5658f2c8656dbd73508e113a96e486a"
},
{
"type": "PACKAGE",
"url": "https://github.com/langflow-ai/langflow"
},
{
"type": "WEB",
"url": "https://github.com/langflow-ai/langflow/releases/tag/1.7.1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P",
"type": "CVSS_V4"
}
],
"summary": "Langflow Missing Authentication on Critical API Endpoints"
}
GHSA-C5FX-H6FR-53H9
Vulnerability from github – Published: 2026-04-29 18:31 – Updated: 2026-04-29 18:31A vulnerability in the access control mechanism of SonicOS may allow certain management interface functions to be accessible under specific conditions.
{
"affected": [],
"aliases": [
"CVE-2026-0204"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-29T17:16:40Z",
"severity": "HIGH"
},
"details": "A vulnerability in the access control mechanism of SonicOS may allow certain management interface functions to be accessible under specific conditions.",
"id": "GHSA-c5fx-h6fr-53h9",
"modified": "2026-04-29T18:31:35Z",
"published": "2026-04-29T18:31:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-0204"
},
{
"type": "WEB",
"url": "https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0004"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-C5GQ-4H56-4MMX
Vulnerability from github – Published: 2026-02-05 00:33 – Updated: 2026-02-06 21:42Description
An information disclosure vulnerability in FUXA allows an unauthenticated, remote attacker to retrieve sensitive administrative database credentials. This affects FUXA through version 1.2.9. This issue has been patched in FUXA version 1.2.10.
Impact
This affects all deployments, including those with runtime.settings.secureEnabled set to true.
Exploitation allows an unauthenticated, remote attacker to obtain the full system configuration, including administrative credentials for the InfluxDB database. Possession of these credentials may allow an attacker to authenticate directly to the database service, enabling them to read, modify, or delete all historical process data, or perform a Denial of Service by corrupting the database.
Patches
This issue has been patched in FUXA version 1.2.10. Users are strongly encouraged to update to the latest available release.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.2.9"
},
"package": {
"ecosystem": "npm",
"name": "fuxa-server"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.2.10"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-25751"
],
"database_specific": {
"cwe_ids": [
"CWE-306",
"CWE-312"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-05T00:33:44Z",
"nvd_published_at": "2026-02-06T19:16:10Z",
"severity": "CRITICAL"
},
"details": "### Description\nAn information disclosure vulnerability in FUXA allows an unauthenticated, remote attacker to retrieve sensitive administrative database credentials. This affects FUXA through version 1.2.9. This issue has been patched in FUXA version 1.2.10.\n\n### Impact\nThis affects all deployments, including those with `runtime.settings.secureEnabled` set to `true`.\n\nExploitation allows an unauthenticated, remote attacker to obtain the full system configuration, including administrative credentials for the InfluxDB database. Possession of these credentials may allow an attacker to authenticate directly to the database service, enabling them to read, modify, or delete all historical process data, or perform a Denial of Service by corrupting the database.\n\n### Patches\nThis issue has been patched in FUXA version 1.2.10. Users are strongly encouraged to update to the latest available release.",
"id": "GHSA-c5gq-4h56-4mmx",
"modified": "2026-02-06T21:42:42Z",
"published": "2026-02-05T00:33:44Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/frangoteam/FUXA/security/advisories/GHSA-c5gq-4h56-4mmx"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25751"
},
{
"type": "WEB",
"url": "https://github.com/frangoteam/FUXA/commit/c6c4cba1a62545e8e3ae0f43b2269e61209fbee8"
},
{
"type": "PACKAGE",
"url": "https://github.com/frangoteam/FUXA"
},
{
"type": "WEB",
"url": "https://github.com/frangoteam/FUXA/releases/tag/v1.2.10"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H",
"type": "CVSS_V4"
}
],
"summary": "FUXA Unauthenticated Exposure of Plaintext Database Credentials"
}
GHSA-C5GV-WRCX-CW6X
Vulnerability from github – Published: 2022-05-26 00:01 – Updated: 2022-06-08 00:00An external config control vulnerability exists in the OAS Engine SecureAddSecurity functionality of Open Automation Software OAS Platform V16.00.0112. A specially-crafted series of network requests can lead to the creation of a custom Security Group. An attacker can send a sequence of requests to trigger this vulnerability.
{
"affected": [],
"aliases": [
"CVE-2022-26043"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-05-25T21:15:00Z",
"severity": "HIGH"
},
"details": "An external config control vulnerability exists in the OAS Engine SecureAddSecurity functionality of Open Automation Software OAS Platform V16.00.0112. A specially-crafted series of network requests can lead to the creation of a custom Security Group. An attacker can send a sequence of requests to trigger this vulnerability.",
"id": "GHSA-c5gv-wrcx-cw6x",
"modified": "2022-06-08T00:00:59Z",
"published": "2022-05-26T00:01:08Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-26043"
},
{
"type": "WEB",
"url": "https://talosintelligence.com/vulnerability_reports/TALOS-2022-1489"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-C5HH-282X-JRGH
Vulnerability from github – Published: 2024-10-14 09:30 – Updated: 2025-01-17 09:30The affected product lacks an authentication check when sending commands to the server via the Moxa service. This vulnerability allows an attacker to execute specified commands, potentially leading to unauthorized downloads or uploads of configuration files and system compromise.
{
"affected": [],
"aliases": [
"CVE-2024-9137"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-10-14T09:15:04Z",
"severity": "HIGH"
},
"details": "The affected product lacks an authentication check when sending commands to the server via the Moxa service. This vulnerability allows an attacker to execute specified commands, potentially leading to unauthorized downloads or uploads of configuration files and system compromise.",
"id": "GHSA-c5hh-282x-jrgh",
"modified": "2025-01-17T09:30:38Z",
"published": "2024-10-14T09:30:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-9137"
},
{
"type": "WEB",
"url": "https://www.moxa.com/en/support/product-support/security-advisory/mpsa-241154-missing-authentication-and-os-command-injection-vulnerabilities-in-routers-and-network-security-appliances"
},
{
"type": "WEB",
"url": "https://www.moxa.com/en/support/product-support/security-advisory/mpsa-241156-cve-2024-9137-missing-authentication-vulnerability-in-ethernet-switches"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/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-C649-6R6M-R7MW
Vulnerability from github – Published: 2023-08-08 12:30 – Updated: 2024-04-04 06:38A vulnerability has been identified in RUGGEDCOM CROSSBOW (All versions < V5.4). The affected applications accept unauthenticated file write messages. An unauthenticated remote attacker could write arbitrary files to the affected application's file system.
{
"affected": [],
"aliases": [
"CVE-2023-37373"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-08-08T10:15:15Z",
"severity": "HIGH"
},
"details": "A vulnerability has been identified in RUGGEDCOM CROSSBOW (All versions \u003c V5.4). The affected applications accept unauthenticated file write messages. An unauthenticated remote attacker could write arbitrary files to the affected application\u0027s file system.",
"id": "GHSA-c649-6r6m-r7mw",
"modified": "2024-04-04T06:38:48Z",
"published": "2023-08-08T12:30:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-37373"
},
{
"type": "WEB",
"url": "https://cert-portal.siemens.com/productcert/pdf/ssa-472630.pdf"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
Mitigation
- Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability.
- Identify all potential communication channels, or other means of interaction with the software, to ensure that all channels are appropriately protected, including those channels that are assumed to be accessible only by authorized parties. Developers sometimes perform authentication at the primary channel, but open up a secondary channel that is assumed to be private. For example, a login mechanism may be listening on one network port, but after successful authentication, it may open up a second port where it waits for the connection, but avoids authentication because it assumes that only the authenticated party will connect to the port.
- In general, if the software or protocol allows a single session or user state to persist across multiple connections or channels, authentication and appropriate credential management need to be used throughout.
Mitigation MIT-15
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Mitigation
- Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment. These capabilities may avoid common weaknesses that are unique to authentication; support automatic auditing and tracking; and make it easier to provide a clear separation between authentication tasks and authorization tasks.
- In environments such as the World Wide Web, the line between authentication and authorization is sometimes blurred. If custom authentication routines are required instead of those provided by the server, then these routines must be applied to every single page, since these pages could be requested directly.
Mitigation MIT-4.5
Strategy: Libraries or Frameworks
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator [REF-45].
Mitigation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data [REF-1297] [REF-1298] [REF-1302].
CAPEC-12: Choosing Message Identifier
This pattern of attack is defined by the selection of messages distributed via multicast or public information channels that are intended for another client by determining the parameter value assigned to that client. This attack allows the adversary to gain access to potentially privileged information, and to possibly perpetrate other attacks through the distribution means by impersonation. If the channel/message being manipulated is an input rather than output mechanism for the system, (such as a command bus), this style of attack could be used to change the adversary's identifier to more a privileged one.
CAPEC-166: Force the System to Reset Values
An attacker forces the target into a previous state in order to leverage potential weaknesses in the target dependent upon a prior configuration or state-dependent factors. Even in cases where an attacker may not be able to directly control the configuration of the targeted application, they may be able to reset the configuration to a prior state since many applications implement reset functions.
CAPEC-216: Communication Channel Manipulation
An adversary manipulates a setting or parameter on communications channel in order to compromise its security. This can result in information exposure, insertion/removal of information from the communications stream, and/or potentially system compromise.
CAPEC-36: Using Unpublished Interfaces or Functionality
An adversary searches for and invokes interfaces or functionality that the target system designers did not intend to be publicly available. If interfaces fail to authenticate requests, the attacker may be able to invoke functionality they are not authorized for.
CAPEC-62: Cross Site Request Forgery
An attacker crafts malicious web links and distributes them (via web pages, email, etc.), typically in a targeted manner, hoping to induce users to click on the link and execute the malicious action against some third-party application. If successful, the action embedded in the malicious link will be processed and accepted by the targeted application with the users' privilege level. This type of attack leverages the persistence and implicit trust placed in user session cookies by many web applications today. In such an architecture, once the user authenticates to an application and a session cookie is created on the user's system, all following transactions for that session are authenticated using that cookie including potential actions initiated by an attacker and simply "riding" the existing session cookie.