CVE-2019-10851
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 · uneditedComputrols CBAS 18.0.0 has hard-coded encryption keys.
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 confidenceComputrols CBAS 18.0.0 contains hard-coded encryption keys embedded directly in the software binary or configuration. This vulnerability allows attackers who obtain the keys to decrypt sensitive data, bypass authentication mechanisms, or impersonate legitimate system communications, potentially leading to full system compromise.
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<= 19.0.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 installed CBAS versionLocate the Computrols Building Automation Software installation and check the version number. This is typically found in the application properties, about dialog, or installation directory metadata.Affected if The installed version is 19.0.0 or any earlier version (e.g., 18.0.0, 17.x.x, etc.)
-
Locate CBAS executable and configuration filesFind the main CBAS application executable and any associated configuration files in the installation directory. Typical locations include C:\Program Files\Computrols\ or C:\Program Files (x86)\Computrols\.Affected if Files exist in the Computrols installation directory, indicating the software is present
-
Search binary for embedded encryption key patternsUse a hex editor or strings utility to examine the CBAS executable for hardcoded cryptographic material. Look for sequences that resemble encryption keys, such as long hexadecimal strings, base64-encoded strings, or recognizable key identifiers.Affected if Readable strings resembling encryption keys (typically 16, 24, or 32 character strings of mixed case and numbers) are found embedded in the binary code section
-
Examine configuration files for static keysReview all .ini, .xml, .json, or .config files in the CBAS installation and data directories. Search for fields labeled 'key', 'encryptionKey', 'cryptoKey', 'passwordKey', or similar that contain static values.Affected if Configuration files contain hardcoded values in key-related fields that are not dynamically generated or referenced from an external key management system
You are affected if CBAS version is 19.0.0 or lower AND hard-coded encryption keys are found embedded in the binary or stored in configuration files.
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 dataReplace all hard-coded encryption keys with dynamically generated keys managed through a secure key management system (KMS) or hardware security module (HSM). Restrict network access to affected systems and monitor for indicators of compromise while awaiting an official vendor patch.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10851 — 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-10851 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