Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreTikaDocumentReader in Spring AI uses Apache Tika to extract text from documents. Its default configuration disables Tika's built-in content-size limit, so the extracted text of a parsed document is buffered in memory with no absolute bound. Apache Tika still aborts a parse when the extracted text is disproportionate to the size of the input, which rejects highly compressed inputs such as archive bombs, but that guard is relative to the input and places no ceiling on the total amount of text extracted. An application that uses TikaDocumentReader to process documents from an untrusted source (e.g., user-uploaded files or attacker-supplied URLs) may therefore be induced to allocate an excessive amount of memory while parsing a sufficiently large document, potentially exhausting available JVM heap and causing a denial of service.
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 aleister1102 (https://github.com/aleister1102) and independently reported by Raphael Zanarelli - https://github.com/zanarellidev
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy