# CVE-2009-1669: Command injection in n/a

> Attackers can execute arbitrary commands via shell metacharacters in the math function equation attribute of the Smarty template engine.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 18 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9qvp-f6pr-8g42

## What is CVE-2009-1669?

CVE-2009-1669 is a critical command injection vulnerability in n/a, published on 18 May 2009. It can be exploited over the network.

### Official description

The smarty_function_math function in libs/plugins/function.math.php in Smarty 2.6.22 allows context-dependent attackers to execute arbitrary commands via shell metacharacters in the equation attribute of the math function.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2009-1669?

It affects 1 product.


Products: Smarty Smarty.

## How do I fix CVE-2009-1669?

Upgrade to a fixed version.

## Is CVE-2009-1669 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1669 exists.

Public exploit code:

- Bitweaver 2.6 - 'saveFeed()' Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-5052](https://insights.sbomify.com/CVE-2009-5052/): Other in n/a (critical 10.0)
- [CVE-2010-4722](https://insights.sbomify.com/CVE-2010-4722/): Other in n/a (critical 10.0)
- [CVE-2010-4724](https://insights.sbomify.com/CVE-2010-4724/): Other in n/a (critical 10.0)
- [CVE-2010-4725](https://insights.sbomify.com/CVE-2010-4725/): Code injection in n/a (critical 10.0)
- [CVE-2010-4726](https://insights.sbomify.com/CVE-2010-4726/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1669 and fix it if it is affected.

What it is: CVE-2009-1669 is a critical command injection vulnerability in n/a, published on 18 May 2009. It can be exploited over the network.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1669 exists.

Affected product: n/a. 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-2009-1669/ (Markdown: https://insights.sbomify.com/CVE-2009-1669/index.md)
```

## Sources

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

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