Chroma through 1.5.9 Authorization Bypass via Collection Identifier
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| chroma-core | chroma | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Chroma-core | Chroma |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.448% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Chroma-core
Chroma-core chroma |
|
| Vendors & Products |
Chroma-core
Chroma-core chroma |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Chroma through 1.5.9 fails to validate tenant and database segments when resolving collections, allowing authenticated attackers to access collections from other tenants by knowing the collection identifier. Attackers can read, modify, and update records in foreign collections by issuing requests under their own tenant path, bypassing authorization checks. | |
| Title | Chroma through 1.5.9 Authorization Bypass via Collection Identifier | |
| Weaknesses | CWE-863 | |
| References |
|
|
| Metrics |
cvssV3_1
|