# CVE-2024-49400: Security feature bypass in Tacquito

> Tacquito library allowed unauthorized command execution due to improper regex matching on allowed commands, requiring configuration of allowed commands.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2024
- **Updated:** 1 Nov 2024

## What is CVE-2024-49400?

CVE-2024-49400 is a critical vulnerability in Meta Tacquito, published on 17 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tacquito prior to commit 07b49d1358e6ec0b5aa482fcd284f509191119e2 was not properly performing regex matches on authorized commands and arguments. Configured allowed commands/arguments were intended to require a match on the entire string, but instead only enforced a match on a sub-string. That would have potentially allowed unauthorized commands to be executed.

## Which versions are affected by CVE-2024-49400?


## How do I fix CVE-2024-49400?

No fix has been published for CVE-2024-49400 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-49400 being exploited?

There is no known exploitation of CVE-2024-49400 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-49400 and fix it if it is affected.

What it is: CVE-2024-49400 is a critical vulnerability in Meta Tacquito, published on 17 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-49400 in the wild and no public exploit code.

Affected product: Meta Tacquito. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-49400/ (Markdown: https://insights.sbomify.com/CVE-2024-49400/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-49400
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-49400
- OSV: https://osv.dev/vulnerability/CVE-2024-49400

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-49400/
Summaries are generated and may contain mistakes; the official description above is the record.