# CVE-2016-4524: Information disclosure in n/a

> Local attackers can obtain sensitive OPC Server IEC61850 passwords due to improper storage in ABB PCM600.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **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 Jun 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8mqx-rxrp-v4x5

## What is CVE-2016-4524?

CVE-2016-4524 is a medium-severity vulnerability in n/a, published on 10 Jun 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ABB PCM600 before 2.7 improperly stores OPC Server IEC61850 passwords in unspecified temporary circumstances, which allows local users to obtain sensitive information via unknown vectors.

Weakness: CWE-310, CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Abb Pcm600.

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

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

## Is CVE-2016-4524 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-4516](https://insights.sbomify.com/CVE-2016-4516/): Information disclosure in n/a (low 3.3)
- [CVE-2016-4527](https://insights.sbomify.com/CVE-2016-4527/): Hardcoded credentials in n/a (low 3.3)
- [CVE-2016-4511](https://insights.sbomify.com/CVE-2016-4511/): Weak cryptography in n/a (low 2.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-4524 is a medium-severity vulnerability in n/a, published on 10 Jun 2016. 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-2016-4524 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-2016-4524/ (Markdown: https://insights.sbomify.com/CVE-2016-4524/index.md)
```

## Sources

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

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