# CVE-2009-4417: Other in n/a

> Attackers can send arbitrary emails to any recipient via the Zend_Log_Writer_Mail shutdown function in the Zend Framework library.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m29x-48p8-pr8r

## What is CVE-2009-4417?

CVE-2009-4417 is a medium-severity vulnerability in n/a, published on 24 Dec 2009. It can be exploited over the network, with no action from the victim.

### Official description

The shutdown function in the Zend_Log_Writer_Mail class in Zend Framework (ZF) allows context-dependent attackers to send arbitrary e-mail messages to any recipient address via vectors related to "events not yet mailed."

Weakness: CWE-264

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

It affects 1 product.


Products: Zend Framework.

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

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

## Is CVE-2009-4417 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-0270](https://insights.sbomify.com/CVE-2015-0270/): Zend Framework Allows SQL Injection (critical 9.8)
- [CVE-2011-3825](https://insights.sbomify.com/CVE-2011-3825/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-4417 is a medium-severity vulnerability in n/a, published on 24 Dec 2009. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-4417 in the wild and no public exploit code.

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-4417/ (Markdown: https://insights.sbomify.com/CVE-2009-4417/index.md)
```

## Sources

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

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