# CVE-2012-3454: Misconfiguration in n/a

> Local attackers can delete or overwrite arbitrary files due to world-writable permissions on the FTP temporary directory in eXtplorer.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-w92m-w2r7-m24j

## What is CVE-2012-3454?

CVE-2012-3454 is a low-severity vulnerability in n/a, published on 7 Aug 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

eXtplorer 2.1.0b6 uses world writable permissions for the /var/lib/extplorer/ftp_tmp directory, which allows local users to delete or overwrite arbitrary files.

Weakness: CWE-264

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

It affects 1 product.


Products: Extplorer Extplorer.

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

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

## Is CVE-2012-3454 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-6710](https://insights.sbomify.com/CVE-2012-6710/): Auth bypass in n/a (critical 9.8)
- [CVE-2023-54335](https://insights.sbomify.com/CVE-2023-54335/): eXtplorer<= 2.1.14 - Authentication Bypass & Remote Code Execution (RCE) (critical 9.3)
- [CVE-2023-29657](https://insights.sbomify.com/CVE-2023-29657/): File upload in n/a (high 8.8)
- [CVE-2023-27842](https://insights.sbomify.com/CVE-2023-27842/): Missing authorization in n/a (high 8.8)
- [CVE-2016-4313](https://insights.sbomify.com/CVE-2016-4313/): Path traversal in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-3454 is a low-severity vulnerability in n/a, published on 7 Aug 2012. 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-2012-3454 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-2012-3454/ (Markdown: https://insights.sbomify.com/CVE-2012-3454/index.md)
```

## Sources

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

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