dbcve.org
Cn80Hardware / appliance · Honeywell

CVE-2018-14825

MEDIUM · 5.8 CVSS v3.0 Published 2018-09-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
No privileges

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 · unedited
On Honeywell Mobile Computers (CT60 running Android OS 7.1, CN80 running Android OS 7.1, CT40 running Android OS 7.1, CK75 running Android OS 6.0, CN75 running Android OS 6.0, CN75e running Android OS 6.0, CT50 running Android OS 6.0, D75e running Android OS 6.0, CT50 running Android OS 4.4, D75e running Android OS 4.4, CN51 running Android OS 6.0, EDA50k running Android 4.4, EDA50 running Android OS 7.1, EDA50k running Android OS 7.1, EDA70 running Android OS 7.1, EDA60k running Android OS 7.1, and EDA51 running Android OS 8.1), a skilled attacker with advanced knowledge of the target system could exploit this vulnerability by creating an application that would successfully bind to the service and gain elevated system privileges. This could enable the attacker to obtain access to keystrokes, passwords, personal identifiable information, photos, emails, or business-critical documents.

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 confidence

Local privilege escalation vulnerability in Honeywell mobile computers where a malicious application can bind to an exposed service to gain elevated system privileges, potentially exposing keystrokes, passwords, PII, photos, emails, and business documents.

MitigationRestrict app installation to trusted sources only (disable 'Allow unknown sources'), implement MDM policies to control app deployment, and apply vendor-provided security patches when available.

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
Cn80Hardware / appliance
Affected:all versions
Ct40Hardware / appliance
Affected:all versions
Ct60Hardware / appliance
Affected:all versions
Eda50Hardware / appliance
Affected:all versions
Eda50kHardware / appliance
Affected:all versions
Eda60kHardware / appliance
Affected:all versions
Eda70Hardware / appliance
Affected:all versions
Ck75Hardware / appliance
Affected:all versions

CVSS 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
Local
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Go to Settings > About Device > Model Number (or similar path depending on Android version) and confirm the exact model name
    Affected if Device model is Cn80, Ct40, Ct60, Eda50, Eda50k, Eda60k, Eda70, or Ck75
  2. Check if unknown sources is allowed
    Go to Settings > Security > Install unknown apps (or Settings > Apps > Special access > Install unknown apps) and see if the toggle is enabled for any app sources
    Affected if Any application source is permitted to install apps (toggle is ON for any source)
  3. Review installed applications
    Go to Settings > Apps > See all apps and look for any applications that are not from trusted corporate deployment or known trusted sources
    Affected if There are applications installed from untrusted or unknown sources that should not be present
  4. Check for MDM enrollment
    Look for a Mobile Device Management profile or agent app installed (often visible in Settings > Security > Device admin or as a management app icon)
    Affected if The device is not enrolled in an MDM solution to control app installation policies

The device is affected if it is one of the listed Honeywell models and either unknown app sources are enabled or untrusted applications are present on the device.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict app installation to trusted sources only (disable 'Allow unknown sources'), implement MDM policies to control app deployment, and apply vendor-provided security patches when available.

Fix this in Cn80 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-14825 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-14825 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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