Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreTypesenseVectorStore is vulnerable to a filter expression injection that can bypass application-enforced metadata filters.
TypesenseFilterExpressionConverter escapes user-controlled filter values only as JSON string literals before embedding them in the filter_by string sent to Typesense. Typesense's own filter-query tokenizer does not treat those escapes as delimiting a literal value and instead splits on characters that can appear inside an unescaped value, so a crafted value can terminate the intended clause and introduce additional filter conditions of the attacker's choosing.
Applications that incorporate untrusted input into a metadata filter value passed to SearchRequest.filterExpression(...) (or otherwise reach TypesenseVectorStore's filter conversion, including delete operations) are affected. An attacker who controls such a value can inject an additional clause that overrides or extends an application's own restrictions, such as a tenant- or permission-scoping filter, resulting in disclosure of documents that should not have been visible to them.
Spring AI:
| Fix version | Availability |
|---|---|
| 2.0.3 | OSS |
| 2.0.2.1 | Enterprise Support Only |
| 1.1.10 | Enterprise Support Only |
| 1.0.11 | Enterprise Support Only |
No further mitigation steps are necessary.
The issue was reported responsibly by 75ACOL - https://github.com/75ACOL and independently reported by: Ishaq Mohammed (https://ishaqmohammed.me/), Jaafer Rahmani (https://github.com/bIackr0se)
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy