# CVE-2016-6602: Weak cryptography in n/a

> Attackers with file access can decrypt stored passwords due to weak obfuscation, potentially leading to credential theft.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rrpj-43vg-95p8

## What is CVE-2016-6602?

CVE-2016-6602 is a critical vulnerability in n/a, published on 23 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ZOHO WebNMS Framework 5.2 and 5.2 SP1 use a weak obfuscation algorithm to store passwords, which allows context-dependent attackers to obtain cleartext passwords by leveraging access to WEB-INF/conf/securitydbData.xml.  NOTE: this issue can be combined with CVE-2016-6601 for a remote exploit.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2016-6602?

It affects 1 product.


Products: Zohocorp Webnms Framework.

## How do I fix CVE-2016-6602?

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

## Is CVE-2016-6602 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-6602 exists.

Public exploit code:

- WebNMS Framework Server Credential Disclosure (metasploit)
- WebNMS Framework Server 5.2/5.2 SP1 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2016-6600](https://insights.sbomify.com/CVE-2016-6600/): Path traversal in n/a (critical 9.8)
- [CVE-2016-6603](https://insights.sbomify.com/CVE-2016-6603/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-6601](https://insights.sbomify.com/CVE-2016-6601/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6602 and fix it if it is affected.

What it is: CVE-2016-6602 is a critical vulnerability in n/a, published on 23 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-6602 exists.

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

## Sources

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

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