Obot before v0.23.0 Authentication Bypass via Registry API
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| obot-platform | obot | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Obot-platform | Obot |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.244% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Obot-platform
Obot-platform obot |
|
| Vendors & Products |
Obot-platform
Obot-platform obot |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Obot versions before v0.23.0 fail to enforce authentication on MCP Registry endpoints under /v0.1/* when registry authentication is enabled. Unauthenticated attackers can read registry metadata including server names, descriptions, repository URLs, and connect URLs by sending GET requests to /v0.1/servers. | |
| Title | Obot before v0.23.0 Authentication Bypass via Registry API | |
| Weaknesses | CWE-862 | |
| References |
| |
| Metrics |
cvssV3_1
|