# CVE-2006-4019: Code injection in n/a

> Remote attackers can overwrite program variables to read or modify other users' attachments and preferences in SquirrelMail.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1154, GHSA-hx28-58mx-whmj, RHSA-2006:0668

## What is CVE-2006-4019?

CVE-2006-4019 is a medium-severity code injection vulnerability in Squirrelmail Squirrelmail, published on 11 Aug 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Dynamic variable evaluation vulnerability in compose.php in SquirrelMail 1.4.0 to 1.4.7 allows remote attackers to overwrite arbitrary program variables and read or write the attachments and preferences of other users.

## Which versions are affected by CVE-2006-4019?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `squirrelmail` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.8-2.el3 |
| `squirrelmail` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.8-2.el3 |
| `squirrelmail` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.8-2.el3 |
| `squirrelmail` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.8-2.el3 |
| `squirrelmail` | Red Hat:enterprise_linux:4::as | All versions | 0:1.4.8-2.el4 |
| `squirrelmail` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.4.8-2.el4 |
| `squirrelmail` | Red Hat:enterprise_linux:4::es | All versions | 0:1.4.8-2.el4 |
| `squirrelmail` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.4.8-2.el4 |

Products: Squirrelmail Squirrelmail.

## How do I fix CVE-2006-4019?

Upgrade to a fixed version.

## Is CVE-2006-4019 being exploited?

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

Public exploit code:

- SquirrelMail < 1.4.7 - Arbitrary Variable Overwrite (exploitdb)

## 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-2006-4019 and fix it if it is affected.

What it is: CVE-2006-4019 is a medium-severity code injection vulnerability in Squirrelmail Squirrelmail, published on 11 Aug 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4019 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-2006-4019/ (Markdown: https://insights.sbomify.com/CVE-2006-4019/index.md)
```

## Sources

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

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