# CVE-2009-4354: Auth bypass in n/a

> Remote attackers can hijack web sessions in TransWARE Active! mail due to insecure session cookie handling, leading to account takeover.

- **Severity:** Medium 5.8 (`AV:N/AC:M/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:** No
- **Published:** 17 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5fpx-cqw2-436p

## What is CVE-2009-4354?

CVE-2009-4354 is a medium-severity authentication bypass vulnerability in n/a, published on 17 Dec 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TransWARE Active! mail 2003 build 2003.0139.0871 and earlier does not properly secure the session ID in a session cookie, which allows remote attackers to hijack web sessions, probably related to the "secure" flag for cookies in SSL sessions.

Weakness: CWE-255

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

It affects 1 product.


Products: Transware Active\! Mail.

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

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

## Is CVE-2009-4354 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4353](https://insights.sbomify.com/CVE-2009-4353/): Information disclosure in n/a (medium 5.8)
- [CVE-2010-3913](https://insights.sbomify.com/CVE-2010-3913/): Other in n/a (medium 4.3)
- [CVE-2013-2302](https://insights.sbomify.com/CVE-2013-2302/): Information disclosure in n/a (low 1.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-4354 is a medium-severity authentication bypass vulnerability in n/a, published on 17 Dec 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-4354 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-4354/ (Markdown: https://insights.sbomify.com/CVE-2009-4354/index.md)
```

## Sources

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

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