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

> Remote attackers can obtain arbitrary user passwords by exploiting a session key exposed in the URL of the web administrative portal.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-33rm-chj2-wr75

## What is CVE-2014-8357?

CVE-2014-8357 is a high-severity vulnerability in n/a, published on 17 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

backupsettings.html in the web administrative portal in Zhone zNID GPON 2426A before S3.0.501 places a session key in a URL, which allows remote attackers to obtain arbitrary user passwords via the sessionKey parameter in a getConfig action to backupsettings.conf.

Weakness: CWE-255

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

It affects 1 product.


Products: Dasanzhone Znid 2426a Firmware.

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

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

## Is CVE-2014-8357 being exploited?

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

Public exploit code:

- ZHONE < S3.0.501 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-8356](https://insights.sbomify.com/CVE-2014-8356/): Auth bypass in n/a (high 8.8)
- [CVE-2014-9118](https://insights.sbomify.com/CVE-2014-9118/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8357 is a high-severity vulnerability in n/a, published on 17 Oct 2017. 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-8357 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-8357/ (Markdown: https://insights.sbomify.com/CVE-2014-8357/index.md)
```

## Sources

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

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