dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-32861

HIGH · 7.8 CVSS v3.1 Published 2024-07-16
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
Under certain circumstances the impacted Software House C•CURE 9000 installer will utilize unnecessarily wide permissions.

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

The Software House C•CURE 9000 installer improperly grants unnecessarily wide permissions to files, directories, or system resources during installation under certain conditions. This likely allows local users with limited privileges to modify or access resources they should not have permission to touch, representing a local privilege escalation or integrity violation with high CVSS integrity impact.

MitigationApply the vendor-provided patch or updated installer for C•CURE 9000 that corrects the permission handling, then re-run installation or verify installed permissions are properly scoped to least-privilege principles.

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
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. Verify C•CURE 9000 is installed
    Check for the presence of C•CURE 9000 by searching for installation directories (commonly in C:\Program Files\Software House\C-CURE 9000 or C:\CCURE9000) or check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'C-CURE 9000'
    Affected if The software is present on the system without the vendor patch applied
  2. Identify installation directory and version
    Locate the main installation folder and look for version information in an 'About' or 'Version' file, or right-click the main executable and view Properties > Details to obtain the installed version number
    Affected if The installed version matches the affected release range (prior to vendor patch) and permissions have not been manually corrected
  3. Examine directory permissions for overly broad access
    Right-click the C•CURE 9000 installation folder, select Properties > Security, and review the permissions. Check if Users, Everyone, or other non-admin groups have Write or Modify permissions beyond what is required for normal operation
    Affected if Non-administrator users or groups have Write, Modify, or Full Control permissions on the installation directory or its subfolders
  4. Check critical executable and config file permissions
    Inspect permissions on key files such as the main application executable (.exe), configuration files (.xml, .ini), and any service-related binaries. Use icacls.exe (e.g., 'icacls "C:\Program Files\Software House\C-CURE 9000\*"') to list ACLs and look for Everyone:(I)(W) or similar overly permissive entries
    Affected if Executable files, configuration files, or service binaries grant write access to standard users or Everyone
  5. Verify service account privileges
    Open Services (services.msc), locate any C•CURE services, right-click and view Properties > Log On tab. Check if the service runs under a privileged account (like LocalSystem) and whether the service executable directory is writable by low-privilege users
    Affected if The service runs under a highly privileged account and the installation directory permits write access by limited users, enabling potential privilege escalation

A user is affected if C•CURE 9000 is installed with the vulnerable installer and the installation directory or its contents grant Write or Modify permissions to non-administrator users or groups.

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-provided patch or updated installer for C•CURE 9000 that corrects the permission handling, then re-run installation or verify installed permissions are properly scoped to least-privilege principles.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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