CVE-2019-10995
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedABB CP651 HMI products revision BSP UN30 v1.76 and prior implement hidden administrative accounts that are used during the provisioning phase of the HMI interface.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceABB CP651 HMI products running BSP UN30 v1.76 and prior contain hidden administrative accounts that are active during the provisioning phase, allowing unauthorized attackers to gain elevated privileges and access the system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= bsp_un30_1.76<= bsp_un30_1.76<= bsp_un30_1.76<= bsp_un30_1.76<= bsp_un30_1.76<= bsp_un30_1.76<= bsp_un30_1.76<= bsp_un30_1.76CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the HMI modelDetermine the exact ABB HMI model number (CP651, CP661, CP665, or CP676) from the device label, web interface, or system documentationAffected if The model is any of CP651, CP661, CP665, or CP676 and the firmware version is at or below bsp_un30_1.76
-
Check the BSP firmware versionAccess the HMI system information or firmware version display (typically found in the web interface under System or About, or via the device console if available) and identify the BSP UN30 version numberAffected if The displayed BSP UN30 version is 1.76 or any version lower than 1.76
-
Determine if provisioning mode is accessibleAttempt to access or observe the provisioning phase of the HMI (this may be accessible via the web interface, console, or during initial setup/configuration boot sequence)Affected if Provisioning mode is active, accessible, or has been run on the device
-
Audit for undocumented administrative accountsDuring provisioning phase or by reviewing the user account list in the HMI web interface or system settings, enumerate all accounts with administrative or elevated privileges and compare against documented authorized accountsAffected if Hidden, undocumented, or undocumented administrative accounts are present in the system beyond the officially documented accounts
The environment is affected if the HMI is a CP651, CP661, CP665, or CP676 model running BSP UN30 firmware version 1.76 or lower, and hidden administrative accounts exist during the provisioning phase.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the HMI firmware to a version newer than BSP UN30 v1.76 to remove the hidden accounts, or identify and disable the undocumented administrative accounts through vendor guidance if firmware update is not immediately feasible.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10995 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10995 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data