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

> Remote attackers can obtain sensitive internal URL information by triggering a stack trace via an invalid product rename action.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pwvw-67m7-qcqh

## What is CVE-2014-9245?

CVE-2014-9245 is a medium-severity vulnerability in n/a, published on 15 Dec 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Zenoss Core through 5 Beta 3 allows remote attackers to obtain sensitive information by attempting a product-rename action with an invalid new name and then reading a stack trace, as demonstrated by internal URL information, aka ZEN-15382.

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

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

It affects 1 product.


Products: Zenoss Zenoss Core.

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

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

## Is CVE-2014-9245 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-6261](https://insights.sbomify.com/CVE-2014-6261/): Code injection in n/a (critical 9.3)
- [CVE-2014-6256](https://insights.sbomify.com/CVE-2014-6256/): Missing authorization in n/a (high 7.5)
- [CVE-2014-9249](https://insights.sbomify.com/CVE-2014-9249/): Missing authorization in n/a (high 7.5)
- [CVE-2014-6253](https://insights.sbomify.com/CVE-2014-6253/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2014-6260](https://insights.sbomify.com/CVE-2014-6260/): Command injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9245 is a medium-severity vulnerability in n/a, published on 15 Dec 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9245 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-9245/ (Markdown: https://insights.sbomify.com/CVE-2014-9245/index.md)
```

## Sources

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

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