invoke-ai invokeai up to 5.4.2 API /api/v2/models/install deserialization

Summaryinfo

A vulnerability was found in invoke-ai invokeai up to 5.4.2. It has been rated as very critical. This affects an unknown function of the file /api/v2/models/install of the component API. The manipulation leads to deserialization. This vulnerability is traded as CVE-2024-12029. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in invoke-ai invokeai up to 5.4.2 and classified as very critical. This issue affects an unknown function of the file /api/v2/models/install of the component API. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

A remote code execution vulnerability exists in invoke-ai/invokeai versions 5.3.1 through 5.4.2 via the /api/v2/models/install API. The vulnerability arises from unsafe deserialization of model files using torch.load without proper validation. Attackers can exploit this by embedding malicious code in model files, which is executed upon loading. This issue is fixed in version 5.4.3.

The advisory is shared at huntr.com. The identification of this vulnerability is CVE-2024-12029 since 12/02/2024. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/20/2025).

The exploit is available at 0day.today. It is declared as proof-of-concept.

Upgrading to version 5.4.3 eliminates this vulnerability. Applying the patch 756008dc5899081c5aa51e5bd8f24c1b3975a59e 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.

The vulnerability is also documented in the vulnerability database at 0day.today (39920). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• invoke-ai

Name

• invokeai

Version

• 5.4.0
• 5.4.1
• 5.4.2

License

• open-source

Website

• Product: https://github.com/invoke-ai/invokeai/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion