# CVE-2014-5004: brbackup exposes database password to unauthorized users

> Local attackers can read database passwords from process listings because the brbackup gem exposes them in command-line arguments.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 10 Jan 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vqcm-7f7f-r539

## What is CVE-2014-5004?

CVE-2014-5004 is a high-severity vulnerability in n/a, published on 10 Jan 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

lib/brbackup.rb in the brbackup gem 0.1.1 for Ruby places the database password on the mysql command line, which allows local users to obtain sensitive information by listing the process.

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

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

2 open source packages ship an affected version, including brbackup. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `brbackup` | RubyGems | All versions | None |
| `brbackup` | RubyGems | All versions | None |

Products: Brbackup Project Brbackup.

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

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

## Is CVE-2014-5004 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5004 is a high-severity vulnerability in n/a, published on 10 Jan 2018. 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-5004 in the wild and no public exploit code.

Affected packages and fixed versions:
- brbackup (RubyGems): affected all versions; no fix listed
- brbackup (RubyGems): affected all versions; no fix listed

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

## Sources

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

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