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

> Local attackers can read the management-server configuration file to obtain cleartext LDAP/AD bind passwords, exposing sensitive credentials.

- **Severity:** Medium 4.9 (`AV:L/AC:L/Au:N/C:C/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:** 1 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xmx6-ccgm-jqvf

## What is CVE-2013-3278?

CVE-2013-3278 is a medium-severity vulnerability in n/a, published on 1 Oct 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

EMC VPLEX before VPLEX GeoSynchrony 5.2 SP1 uses cleartext for storage of the LDAP/AD bind password, which allows local users to obtain sensitive information by reading the management-server configuration file.

Weakness: CWE-255

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

It affects 4 products.


Products: Emc Geosynchrony, Emc Vplex Geo, Emc Vplex Local, Emc Vplex Metro.

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

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

## Is CVE-2013-3278 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3278 is a medium-severity vulnerability in n/a, published on 1 Oct 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-3278 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-3278/ (Markdown: https://insights.sbomify.com/CVE-2013-3278/index.md)
```

## Sources

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

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