Mintplex Labs/Anything Llm
Approved changes feed: RSS · Atom
cpe:2.3:a:mintplex-labs:mintplex-labs\/anything-llm:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Mintplex Labs (e54a2d9f-d3cf-523b-bbb7-c499d4853e27) |
|---|---|
| Product | Mintplex Labs/Anything Llm (5e0c3059-b98c-5940-84dd-413931672f98) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-3025 |
vulnerable | 2026-06-08 06:41:52.235882 |
Path Traversal in mintplex-labs/anything-llm
CRITICAL (9.9)
mintplex-labs/anything-llm is vulnerable to path traversal attacks due to insufficient validation of user-supplied input in the logo filename functionality. Attackers can exploit this vulnerability by manipulating the logo filename to reference files outside of the restricted directory. This can lead to unauthorized reading or deletion of files by utilizing the `/api/system/upload-logo` and `/api/system/logo` endpoints. The issue stems from the lack of filtering or validation on the logo filename, allowing attackers to target sensitive files such as the application's database.
Published: 2024-04-10T17:07:52.626Z
Updated: 2024-08-01T19:32:42.584Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-0455 |
vulnerable | 2026-06-08 06:22:01.160495 |
SSRF on AWS deployed instances of AnythingLLM via /metadata
CRITICAL (9.9)
The inclusion of the web scraper for AnythingLLM means that any user with the proper authorization level (manager, admin, and when in single user) could put in the URL
```
http://169.254.169.254/latest/meta-data/identity-credentials/ec2/security-credentials/ec2-instance
```
which is a special IP and URL that resolves only when the request comes from within an EC2 instance. This would allow the user to see the connection/secret credentials for their specific instance and be able to manage it regardless of who deployed it.
The user would have to have pre-existing knowledge of the hosting infra which the target instance is deployed on, but if sent - would resolve if on EC2 and the proper `iptable` or firewall rule is not configured for their setup.
Published: 2024-02-25T08:10:17.100Z
Updated: 2024-08-12T13:40:34.185Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.