# CVE-2014-3045: Information disclosure in n/a

> Local users with root access can obtain administrative passwords from shell history in IBM SONAS, leading to sensitive information disclosure.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-74p5-wh3g-f9rh

## What is CVE-2014-3045?

CVE-2014-3045 is a low-severity vulnerability in n/a, published on 19 Jul 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Scale Out Network Attached Storage (SONAS) 1.3.x and 1.4.x before 1.4.3.3 places an administrative password in the shell history upon use of the -p option to chuser, which allows local users to obtain sensitive information by leveraging root access.

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

## Which versions are affected by CVE-2014-3045?

It affects 1 product.


Products: Ibm Scale Out Network Attached Storage.

## How do I fix CVE-2014-3045?

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

## Is CVE-2014-3045 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2163](https://insights.sbomify.com/CVE-2012-2163/): Code injection in n/a (critical 9.0)
- [CVE-2012-0706](https://insights.sbomify.com/CVE-2012-0706/): Hardcoded credentials in n/a (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3045 and fix it if it is affected.

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

## Sources

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

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