dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-4229

HIGH · 7.8 CVSS v3.1 Published 2024-12-19
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
Incorrect Default Permissions vulnerability in Edgecross Basic Software for Windows versions 1.00 and later and Edgecross Basic Software for Developers versions 1.00 and later allows a malicious local attacker to execute an arbitrary malicious code, resulting in information disclosure, tampering with and deletion, or a denial-of-service (DoS) condition, if the product is installed in a folder other than a folder that only users with administrative privilege have permission to modify.

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

This is a local privilege escalation vulnerability caused by incorrect default file permissions in Edgecross Basic Software for Windows. When installed in a user-writable directory (not a protected system folder like Program Files), local attackers can modify executable files, DLLs, or configuration files to inject and execute malicious code with the software's privileges, leading to information disclosure, tampering, or DoS.

MitigationEnsure the software is installed only in protected directories (e.g., Program Files) that require administrative privileges for modification. For existing installations in unprotected locations, audit and correct file/folder permissions to restrict write access to administrators only.

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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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 Edgecross Basic Software installation directory
    Check common installation paths: C:\Program Files\Edgecross\, C:\Edgecross\, or the installation directory specified during setup. Use 'dir /s /b C:\*edgecross* 2>nul' or check Add/Remove Programs for the installation path.
    Affected if The software is found installed on the system
  2. Verify installation directory is user-writable
    Inspect the installation path. Common protected locations include Program Files, Program Files (x86), or Windows\System32. User-writable locations include user profile folders, desktop, or custom directories created in C:\ root.
    Affected if The installation directory is NOT under Program Files or other protected system folders (e.g., installed directly to C:\Edgecross\, a user folder, or a custom directory that standard users can modify)
  3. Check write permissions on installation folder
    Right-click the installation folder, go to Properties > Security tab, and review permissions. Or run 'icacls "<installation_path>"' from command prompt to list effective permissions.
    Affected if Standard users or the 'Users' group have Write or Modify permissions to the installation folder or its contents
  4. Identify modifiable executables and DLLs
    Run 'dir /b "<installation_path>\*.exe"' and 'dir /b "<installation_path>\*.dll"' to list executable and DLL files. Then check if these files are writable using 'icacls "<file_path>"' or by attempting to rename/modify (in a non-production test).
    Affected if Executable files (.exe), dynamic libraries (.dll), or configuration files in the installation directory are writable by non-administrator users

The system is affected if Edgecross Basic Software is installed in a directory where standard users have write access (not Program Files or other protected system folders), allowing modification of executables, DLLs, or configuration files.

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

Ensure the software is installed only in protected directories (e.g., Program Files) that require administrative privileges for modification. For existing installations in unprotected locations, audit and correct file/folder permissions to restrict write access to administrators only.

Have this fixed 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-2024-4229 — 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-4229 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