# CVE-2013-2302: Information disclosure in n/a

> Local users with shell access can obtain sensitive information from arbitrary users in TransWARE Active! mail when an external public interface is enabled.

- **Severity:** Low 1.9 (`AV:L/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-9rxw-2q74-f2mq

## What is CVE-2013-2302?

CVE-2013-2302 is a low-severity vulnerability in n/a, published on 4 Apr 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TransWARE Active! mail 6, when an external public interface is used, allows local users to obtain sensitive information belonging to arbitrary users by leveraging shell access, as demonstrated by a TELNET or SSH session to the server.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2013-2302?

It affects 1 product.


Products: Transware Active\! Mail.

## How do I fix CVE-2013-2302?

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

## Is CVE-2013-2302 being exploited?

There is no known exploitation of CVE-2013-2302 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-2009-4354](https://insights.sbomify.com/CVE-2009-4354/): Auth bypass in n/a (medium 5.8)
- [CVE-2010-3913](https://insights.sbomify.com/CVE-2010-3913/): Other in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2302 and fix it if it is affected.

What it is: CVE-2013-2302 is a low-severity vulnerability in n/a, published on 4 Apr 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2302 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-2013-2302/ (Markdown: https://insights.sbomify.com/CVE-2013-2302/index.md)
```

## Sources

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

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