Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-11969

HIGH · 8.8 CVSS v3.1 Published 2024-11-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
The NetCloud Exchange client for Windows, version 1.110.50, contains an insecure file and folder permissions vulnerability. A normal (non-admin) user could exploit the weakness in file and folder permissions to escalate privileges, execute arbitrary code and maintain persistence on the compromised machine. It has been identified that full control permissions exist on the ‘Everyone’ group (i.e. any user who has local access to the operating system regardless of their privileges).

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 · high confidence

The NetCloud Exchange client for Windows v1.110.50 has incorrect file and folder permissions where the 'Everyone' group has Full Control access to application files and directories. This allows any local user to modify executable files, replace binaries, or alter configuration files to achieve privilege escalation, execute arbitrary code, and establish persistence on the affected system.

MitigationApply restrictive NTFS permissions to the NetCloud Exchange client installation directory, removing 'Everyone' full control and granting only necessary permissions to required service accounts and administrators; verify with vendor patch when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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. Locate NetCloud Exchange installation directory
    Check common installation paths such as C:\Program Files\Cradlepoint\NetCloud Exchange or C:\Program Files (x86)\Cradlepoint\NetCloud Exchange, or use the search feature to find folders containing 'NetCloud Exchange' executables.
    Affected if The application is installed in any directory.
  2. Identify installed version
    Right-click on the main executable (often named NCXClient.exe or similar) in the NetCloud Exchange installation folder, select Properties, and view the Details tab to find the Product Version. Alternatively, check Add/Remove Programs or Programs and Features for the installed version.
    Affected if The installed version is 1.110.50.
  3. Verify Everyone group permissions on application directory
    Right-click the NetCloud Exchange installation folder, select Properties, go to the Security tab, and click on 'Everyone' to view permissions. Check if the 'Full control' checkbox is enabled under the Allow column.
    Affected if The Everyone group has Full control or Write permissions on the application directory.
  4. Check permissions on executable files
    In the application directory, right-click on executable files (such as .exe files), select Properties, then Security tab. Verify if the Everyone group has Write or Modify permissions that would allow replacement of these files.
    Affected if Executable files are writable or modifiable by the Everyone group.

A system is affected if NetCloud Exchange client version 1.110.50 is installed and the Everyone group has full control or write permissions on the application directory or its executables.

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 restrictive NTFS permissions to the NetCloud Exchange client installation directory, removing 'Everyone' full control and granting only necessary permissions to required service accounts and administrators; verify with vendor patch when available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11969 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11969 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