CVE-2024-46466
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 · uneditedBy default, dedicated folders of ZONECENTRAL for Windows up to 2024.3 or up to Q.2021.2 (ANSSI qualification submission) can be accessed by other users to misuse technical files and make them perform tasks with higher privileges. Configuration of ZONECENTRAL has to be modified to prevent this vulnerability.
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 confidenceZONECENTRAL for Windows contains improper access control on dedicated folders, allowing unprivileged users to access technical files. This enables misuse of those files to perform tasks with elevated privileges, representing a local privilege escalation vulnerability.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify ZONECENTRAL installationCheck for ZONECENTRAL installation by looking in Program Files, Program Files (x86), or using registry keys under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. Also check for ZONECENTRAL service running via Get-Service in PowerShell.Affected if ZONECENTRAL is installed and running on the system
-
Locate ZONECENTRAL data directoriesIdentify folders where ZONECENTRAL stores technical or configuration files. Check installation directory, common data paths (\ProgramData\ZONECENTRAL, \Users\*\AppData\Local\ZONECENTRAL), or examine the application's log/config files to find references to dedicated folders.Affected if ZONECENTRAL stores technical files in dedicated folders accessible via the file system
-
Examine folder access control listsUse icacls or Get-Acl PowerShell cmdlets on identified ZONECENTRAL folders. Run 'icacls "<folder_path>"' to list all security principals with access permissions, noting any entries granting access to Users, Everyone, or authenticated users.Affected if Folders grant read or write access to unprivileged groups such as Users, Everyone, or authenticated users
-
Test unprivileged user file accessCreate a standard Windows user account without administrative privileges if one does not exist. Using that account, attempt to navigate to and read files in ZONECENTRAL's dedicated folders via file explorer or command line (type, copy).Affected if A non-administrative user can read sensitive technical files, configuration files, or credentials stored in ZONECENTRAL folders
-
Identify privilege escalation vectorsReview accessible files for embedded credentials, stored tokens, configuration specifying privileged commands, or scripts that run with elevated privileges. Check for .exe, .bat, .ps1, .xml, .ini, or credential store files.Affected if Technical files contain credentials, privilege escalation scripts, or configuration enabling elevated task execution
If unprivileged users can access sensitive technical files in ZONECENTRAL's dedicated folders, the improper access control vulnerability is present and could enable local privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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 dataModify ZONECENTRAL configuration to restrict access to dedicated folders, implementing proper access control lists to prevent other users from accessing sensitive technical files.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46466 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-46466 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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