|
| 1 | +--- |
| 2 | +id: MCP_WEBDRIVER_SESSIONID_EXPOSURE_LT |
| 3 | +info: |
| 4 | + name: WebDriver Session Identifier Exposure in MCP Logs |
| 5 | + description: | |
| 6 | + This test checks whether the MCP server response contains raw WebDriver `sessionId` |
| 7 | + values inside automation test logs or responses. Session IDs are sensitive and can |
| 8 | + allow attackers to hijack active browser automation sessions. |
| 9 | + details: | |
| 10 | + The test invokes an MCP API that fetches automation test logs (e.g., WebDriver command |
| 11 | + or session logs). If the response payload includes `"sessionId": "<value>"`, it indicates |
| 12 | + that the MCP server is leaking session identifiers directly to clients. An attacker could |
| 13 | + reuse these session IDs (if the hub or node is accessible) to control active sessions, |
| 14 | + extract cookies, tokens, or perform malicious actions. |
| 15 | + impact: | |
| 16 | + Disclosure of WebDriver session identifiers allows potential session hijacking. |
| 17 | + Attackers may drive the victim’s browser session, steal authentication tokens, |
| 18 | + exfiltrate sensitive application data, or use the session as a pivot point into |
| 19 | + other parts of the infrastructure. Severity may escalate to CRITICAL if the |
| 20 | + WebDriver grid is reachable beyond the sandboxed environment. |
| 21 | + category: |
| 22 | + name: MCP |
| 23 | + shortName: MCP |
| 24 | + displayName: Model Context Protocol (MCP) Security |
| 25 | + subCategory: MCP_WEBDRIVER_SESSIONID_EXPOSURE_LT |
| 26 | + severity: HIGH |
| 27 | + tags: |
| 28 | + - information_disclosure |
| 29 | + - session_hijacking |
| 30 | + - webdriver |
| 31 | + - mcp_security |
| 32 | + references: |
| 33 | + - https://cwe.mitre.org/data/definitions/200.html |
| 34 | + - https://cwe.mitre.org/data/definitions/522.html |
| 35 | + - https://owasp.org/Top10/A07_2021-Identification_and_Authentication_Failures |
| 36 | + cwe: |
| 37 | + - CWE-200 |
| 38 | + - CWE-522 |
| 39 | + cve: [] |
| 40 | +attributes: |
| 41 | + nature: NON_INTRUSIVE |
| 42 | + plan: PRO |
| 43 | + duration: FAST |
| 44 | +api_selection_filters: |
| 45 | + response_code: |
| 46 | + gte: 200 |
| 47 | + lt: 300 |
| 48 | + method: |
| 49 | + eq: POST |
| 50 | + request_payload: |
| 51 | + contains_all: |
| 52 | + - method |
| 53 | + - id |
| 54 | + - jsonrpc |
| 55 | +execute: |
| 56 | + type: single |
| 57 | + requests: |
| 58 | + - req: [] |
| 59 | +validate: |
| 60 | + response_payload: |
| 61 | + magic_validate: "Whenever WebDriver sessionIds are exposed in the response body then it is a serious vulnerability. check for any such data in the given response. IGNORE errors, ids, sessionIds, etc that are not related to webDrivers." |
0 commit comments