OpenMetadata: TEST_CONNECTION workflow leaks ingestion-bot JWT and database password to regular users
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| open-metadata | OpenMetadata | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Open-metadata | Openmetadata |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-9vmh-whc4-7phg | OpenMetadata: TEST_CONNECTION workflow leaks ingestion-bot JWT and database password to regular users |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.241% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Open-metadata
Open-metadata openmetadata |
|
| Vendors & Products |
Open-metadata
Open-metadata openmetadata |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OpenMetadata is a unified metadata platform. Prior to version 1.12.4, a non-admin SSO user can trigger a TEST_CONNECTION workflow for a Database Service and receive, in the HTTP 201 response of POST /api/v1/automations/workflows, both the cleartext database password in request.connection.config.password and the ingestion bot JWT in openMetadataServerConnection.securityConfig.jwtToken. The leaked ingestion-bot token can then be reused as Authorization: Bearer <jwt> to access sensitive service APIs with bot-level privileges. This issue has been patched in version 1.12.4. | |
| Title | OpenMetadata: TEST_CONNECTION workflow leaks ingestion-bot JWT and database password to regular users | |
| Weaknesses | CWE-201 | |
| References |
| |
| Metrics |
cvssV3_1
|