# CVE-2012-4940: Path traversal in n/a

> Remote attackers can read or delete arbitrary files via directory traversal in the View Log Files component of Axigen Free Mail Server.

- **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:** No
- **Published:** 31 Oct 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-32jr-8q2g-wwf3

## What is CVE-2012-4940?

CVE-2012-4940 is a medium-severity path traversal vulnerability in n/a, published on 31 Oct 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in the View Log Files component in Axigen Free Mail Server allow remote attackers to read or delete arbitrary files via a .. (dot dot) in (1) the fileName parameter in a download action to source/loggin/page_log_dwn_file.hsp, or the fileName parameter in (2) an edit action or (3) a delete action to the default URI.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2012-4940?

It affects 1 product.


Products: Gecad Axigen Free Mail Server.

## How do I fix CVE-2012-4940?

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

## Is CVE-2012-4940 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4940 exists.

Public exploit code:

- Axigen Mail Server - 'Filename' Directory Traversal (exploitdb)
- Axigen Arbitrary File Read and Delete (metasploit)
- Axigen Mail Server Filename Directory Traversal (nuclei): http/cves/2012/CVE-2012-4940.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4940 and fix it if it is affected.

What it is: CVE-2012-4940 is a medium-severity path traversal vulnerability in n/a, published on 31 Oct 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4940 exists.

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

## Sources

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

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