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

> Local attackers can read log and configuration files to discover cleartext operating-system, proxy, and SNMP passwords.

- **Severity:** Low 2.1 (`AV:L/AC:L/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:** 7 Jun 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m7fj-x53w-pr9v

## What is CVE-2013-0947?

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

### Official description

EMC RSA Authentication Manager 8.0 before P1 allows local users to discover cleartext operating-system passwords, HTTP plug-in proxy passwords, and SNMP communities by reading a (1) log file or (2) configuration file.

Weakness: CWE-255

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

It affects 1 product.


Products: Rsa Authentication Manager.

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

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

## Is CVE-2013-0947 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-15782](https://insights.sbomify.com/CVE-2018-15782/): DSA-2018-226: RSA® Authentication Manager Relative Path Traversal Vulnerability (high 7.7)
- [CVE-2018-1247](https://insights.sbomify.com/CVE-2018-1247/): XML external entity in RSA Authentication Manager Security Console (high 7.1)
- [CVE-2018-1248](https://insights.sbomify.com/CVE-2018-1248/): Open redirect in RSA Authentication Manager Security Console, Operation Console and Self-Service Console (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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