CyberRota Analysis
AI-GeneratedBentoPDF versions 2.8.6 and earlier are vulnerable due to improper validation of the tsaUrl control in the deserializeWorkflow() function, allowing attackers to specify an endpoint for timestamp requests. This can lead to the disclosure of a document's SHA-256 digest, enabling correlation of documents across users without exposing their contents. Organizations using BentoPDF for PDF processing should prioritize updating to version 2.8.7 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
BentoPDF is a client-side PDF toolkit that is self hostable. In 2.8.6 and earlier, deserializeWorkflow() accepts the Timestamp node's tsaUrl control from imported JSON without schema or destination validation. When a user imports the crafted workflow and runs it against a PDF, timestampPdf() sends an RFC 3161 TimeStampReq containing the PDF's SHA-256 MessageImprint to the attacker-selected endpoint. The default self-hosted configuration does not set VITE_CORS_PROXY_URL, so the request bypasses the proxy's ALLOWED_TSA_HOSTS checks and is sent directly. The disclosed digest can confirm that a document matches a known file and can correlate the same document across users without revealing its contents. This vulnerability is fixed in 2.8.7.