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

> Authenticated administrators can read log files containing sensitive credentials, leading to information disclosure.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2014
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-9m2c-xgjp-gppg

## What is CVE-2014-8735?

CVE-2014-8735 is a medium-severity vulnerability in n/a, published on 12 Nov 2014. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Bad Behavior module 6.x-2.x before 6.x-2.2216 and 7.x-2.x before 7.x-2.2216 for Drupal logs usernames and passwords, which allows remote authenticated users with the "administer bad behavior" permission to obtain sensitive information by reading a log file.

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

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

It affects 1 product.


Products: Bad Behavior Project Bad Behavior.

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

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

## Is CVE-2014-8735 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8735 is a medium-severity vulnerability in n/a, published on 12 Nov 2014. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-8735 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-8735/ (Markdown: https://insights.sbomify.com/CVE-2014-8735/index.md)
```

## Sources

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

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