CVE-2025-56404
BaseFortify
Publication date: 2025-09-10
Last updated on: 2025-09-17
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mariadb | model_context_protocol | 0.1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-20 | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-56404 is an unauthorized access vulnerability in the Server-Sent Events (SSE) mode of MariaDB MCP version 0.1.0. The SSE service lacks any user authentication, allowing attackers to connect to the SSE endpoint without validation and directly access sensitive database information. This happens because the SSE transport implementation in the server.py script does not enforce authentication checks. [1, 2]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of sensitive database information by allowing attackers to bypass authentication and access data through the SSE endpoint. If exploited, it could result in data breaches, loss of confidentiality, and potential misuse of sensitive information. The vulnerability is especially critical if the service is exposed to untrusted networks or the public internet. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking if the MariaDB MCP server is running in SSE mode without authentication. One way is to run the server with the command `python3 server.py --transport sse --host 0.0.0.0 --port 8888` and then attempt to access the SSE stream via a URL such as `http://<server-ip>:8888/sse`. If you can access sensitive data without authentication, the vulnerability is present. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Deploy the affected system within a VPN or internal network to restrict access to trusted IPs only. 2) Configure firewall rules to limit inbound connections to the vulnerable service port (e.g., port 8888) to authorized clients. 3) Ensure the vulnerable service is not exposed to the public internet. 4) Monitor official vendor updates and apply patches promptly once available. [2]