Reuse of session IDs in oatpp-mcp leads to session hijacking and prompt hijacking by remote attackers
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| oatpp | oatpp-mcp | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Oatpp | Mcp | — |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.401% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Oatpp
Oatpp mcp |
|
| Vendors & Products |
Oatpp
Oatpp mcp |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The MCP SSE endpoint in oatpp-mcp returns an instance pointer as the session ID, which is not unique nor cryptographically secure. This allows network attackers with access to the oatpp-mcp server to guess future session IDs and hijack legitimate client MCP sessions, returning malicious responses from the oatpp-mcp server. | |
| Title | Reuse of session IDs in oatpp-mcp leads to session hijacking and prompt hijacking by remote attackers | |
| Weaknesses | CWE-330 | |
| References |
| |
| Metrics |
cvssV3_1
|