Menu

Star on GitHub · 3.2k

CVE-2016-4511

2.8 · LOW

ABB PCM600 before 2.7 uses an improper hash algorithm for the main application password, which makes it easier for local users to obtain sensitive cleartext information by leveraging read access to…

Published Jun 10, 2016CWE-310EPSS 0.30%

Overview

CVE-2016-4511 is a low-severity vulnerability. It was published on June 10, 2016 and has a CVSS 3.0 base score of 2.8 (LOW).

This vulnerability has a CVSS 3.0 base score of 2.8, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

ABB PCM600 before 2.7 uses an improper hash algorithm for the main application password, which makes it easier for local users to obtain sensitive cleartext information by leveraging read access to the ACTConfig configuration file.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2016-4511?

CVE-2016-4511 is a low-severity vulnerability. It was published on June 10, 2016 and has a CVSS 3.0 base score of 2.8 (LOW).

How severe is CVE-2016-4511?

This vulnerability has a CVSS 3.0 base score of 2.8, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2016-4511?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2016-4511?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-4511 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2016

View all