dbcve.org
Qca6174 FirmwareOperating system · Qualcomm

CVE-2019-10617

HIGH · 7.8 CVSS v3.1 Published 2019-11-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Low privilege users can access service configuration which contains registry data that admins uses to create or delete entries in the registry in QCA6174_9377.WIN.1.0 in QCA6174_9377

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

This is a privilege escalation/information disclosure vulnerability in the Qualcomm QCA6174_9377 wireless driver for Windows. The driver exposes service configuration data containing registry information to low-privilege users, which should be restricted to administrators. This allows unprivileged users to access sensitive registry configuration that admins use for managing registry entries.

MitigationApply the vendor patch/update for the QCA6174_9377 driver to restrict service configuration access to administrator-level users only, preventing low-privilege access to sensitive registry data.

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
Qca6174 FirmwareOperating system
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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Identify Qualcomm wireless adapter presence
    Open Device Manager, expand Network adapters, and look for any Qualcomm QCA6174 or QCA9377 wireless adapter entries. Alternatively, run 'get-childitem -path hklm:\system\currentcontrolset\services' in PowerShell and search for service names containing 'QCA6174' or 'QCA9377' or 'Qualcomm' wireless-related entries.
    Affected if A Qualcomm QCA6174 or QCA9377 wireless adapter driver is installed on the system
  2. Verify driver service exists
    Run 'sc query type= service state= all' and look for services related to the Qualcomm wireless driver (typically named with QCA or Qualcomm prefixes). Note the service display name and binary path.
    Affected if A Qualcomm wireless driver service is found in the system services list
  3. Check service configuration permissions
    Run 'sc qc <servicename>' to query the service configuration, then use 'accesschk.exe' or PowerShell 'Get-Acl' on the service binary path to determine if low-privilege users (Authenticated Users, Users group) have read or write access to the service executable or its configuration.
    Affected if Low-privilege users have read or write access to the driver service binary or configuration
  4. Inspect registry permissions on service key
    Use regedit or PowerShell 'Get-Acl' on registry keys under HKLM\System\CurrentControlSet\Services\<QualcommServiceName> to check if Authenticated Users or Users group has access beyond read-only, particularly to Parameters or Config subkeys.
    Affected if Non-admin users have elevated permissions (write/modify) on the driver service registry keys containing configuration data
  5. Test low-privilege registry access
    As a non-administrator user (or use 'runas /user:StandardUser regedit'), attempt to read the registry keys under the Qualcomm driver service configuration. Check if sensitive configuration data is accessible to standard user accounts.
    Affected if A standard (non-admin) user account can read sensitive registry configuration data intended for administrator-only access

The environment is affected if a Qualcomm QCA6174 or QCA9377 wireless driver is installed and low-privilege users can access the driver service configuration or its registry keys containing sensitive administrative data.

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

Apply the vendor patch/update for the QCA6174_9377 driver to restrict service configuration access to administrator-level users only, preventing low-privilege access to sensitive registry data.

Fix this in Qca6174 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10617 — 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-2019-10617 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