deepset-ai haystack up to 2.3.0 special elements used in a template engine

Summaryinfo

A vulnerability labeled as critical has been found in deepset-ai haystack up to 2.3.0. This vulnerability affects unknown code. The manipulation results in improper neutralization of special elements used in a template engine. This vulnerability is identified as CVE-2024-41950. The attack can be executed remotely. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as critical has been found in deepset-ai haystack up to 2.3.0. Affected is an unknown part. The manipulation with an unknown input leads to a improper neutralization of special elements used in a template engine vulnerability. CWE is classifying the issue as CWE-1336. The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

Haystack is an end-to-end LLM framework that allows you to build applications powered by LLMs, Transformer models, vector search and more. Haystack clients that let their users create and run Pipelines from scratch are vulnerable to remote code executions. Certain Components in Haystack use Jinja2 templates, if anyone can create and render that template on the client machine they run any code. The vulnerability has been fixed with Haystack `2.3.1`.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2024-41950 since 07/24/2024. The exploitability is told to be difficult. It is possible to launch the attack remotely. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1221.

Upgrading to version 2.3.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 3fed1366c448b02189851bf08166c1f6477a02b0 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• deepset-ai

Name

• haystack

Version

• 2.0
• 2.1
• 2.2
• 2.3.0

License

• open-source

Website

• Product: https://github.com/deepset-ai/haystack/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion