# CVE-2009-2964: Cross-site request forgery in n/a

> Remote attackers can hijack user sessions to send messages or change preferences in SquirrelMail and NaSMail webmail clients via CSRF.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jj6p-27w9-hh6m, RHSA-2009:1490

## What is CVE-2009-2964?

CVE-2009-2964 is a medium-severity vulnerability in Squirrelmail Squirrelmail, published on 25 Aug 2009. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in SquirrelMail 1.4.19 and earlier, and NaSMail before 1.7, allow remote attackers to hijack the authentication of unspecified victims via features such as send message and change preferences, related to (1) functions/mailbox_display.php, (2) src/addrbook_search_html.php, (3) src/addressbook.php, (4) src/compose.php, (5) src/folders.php, (6) src/folders_create.php, (7) src/folders_delete.php, (8) src/folders_rename_do.php, (9) src/folders_rename_getname.php, (10) src/folders_subscribe.php, (11) src/move_messages.php, (12) src/options.php, (13) src/options_highlight.php, (14) src/options_identities.php, (15) src/options_order.php, (16) src/search.php, and (17) src/vcard.php.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `squirrelmail` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.8-16.el3 |
| `squirrelmail` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.8-16.el3 |
| `squirrelmail` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.8-16.el3 |
| `squirrelmail` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.8-16.el3 |
| `squirrelmail` | Red Hat:enterprise_linux:4::as | All versions | 0:1.4.8-5.el4_8.8 |
| `squirrelmail` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.4.8-5.el4_8.8 |
| `squirrelmail` | Red Hat:enterprise_linux:4::es | All versions | 0:1.4.8-5.el4_8.8 |
| `squirrelmail` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.4.8-5.el4_8.8 |
| `squirrelmail` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.4.8-5.el5_4.10 |
| `squirrelmail` | Red Hat:enterprise_linux:5::server | All versions | 0:1.4.8-5.el5_4.10 |

Products: Squirrelmail Squirrelmail.

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

Upgrade to a fixed version.

## Is CVE-2009-2964 being exploited?

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

## Other vulnerabilities in Squirrelmail Squirrelmail

- [CVE-2002-0516](https://insights.sbomify.com/CVE-2002-0516/): Command injection in n/a (critical 10.0)
- [CVE-2020-14932](https://insights.sbomify.com/CVE-2020-14932/): Deserialization in n/a (critical 9.8)
- [CVE-2020-14933](https://insights.sbomify.com/CVE-2020-14933/): Deserialization in n/a (high 8.8)
- [CVE-2017-7692](https://insights.sbomify.com/CVE-2017-7692/): Command injection in n/a (high 8.8)
- [CVE-2007-2631](https://insights.sbomify.com/CVE-2007-2631/): Cross-site request forgery in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2964 is a medium-severity vulnerability in Squirrelmail Squirrelmail, published on 25 Aug 2009. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-2964 in the wild and no public exploit code.

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

## Sources

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

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