modelscope agentscope up to 0.0.4 /load-workflow filename information expsure

Summaryinfo

A vulnerability has been found in modelscope agentscope up to 0.0.4 and classified as problematic. This affects an unknown part of the file /load-workflow. This manipulation of the argument filename causes information expsure. This vulnerability is registered as CVE-2024-8550. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability classified as problematic was found in modelscope agentscope up to 0.0.4. Affected by this vulnerability is an unknown part of the file /load-workflow. The manipulation of the argument filename with an unknown input leads to a information expsure vulnerability. The CWE definition for the vulnerability is CWE-497. The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does. As an impact it is known to affect confidentiality. The summary by CVE is:

A Local File Inclusion (LFI) vulnerability exists in the /load-workflow endpoint of modelscope/agentscope version v0.0.4. This vulnerability allows an attacker to read arbitrary files from the server, including sensitive files such as API keys, by manipulating the filename parameter. The issue arises due to improper sanitization of user input passed to the os.path.join function, which can be exploited to access files outside the intended directory.

The advisory is shared at huntr.com. This vulnerability is known as CVE-2024-8550 since 09/06/2024. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• modelscope

Name

• agentscope

Version

• 0.0.1
• 0.0.2
• 0.0.3
• 0.0.4

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion