CVE-2024-46467
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 ZONEPOINT for Windows up to 2024.1 can be accessed by other users to misuse technical files and make them perform tasks with higher privileges. Configuration of ZONEPOINT 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 confidenceZONEPOINT for Windows up to version 2024.1 ships with default folder permissions that allow other users on the same system to access technical files in dedicated folders. This insecure configuration can be exploited to make the application perform privileged tasks, resulting in privilege escalation.
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 ZONEPOINT installation and versionCheck for ZONEPOINT in the list of installed programs (via Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or Programs and Features) and note the installed version.Affected if ZONEPOINT is installed and the version is 2024.1 or earlier.
-
Locate ZONEPOINT application foldersIdentify the installation directory (commonly C:\Program Files\ZONEPOINT or C:\Program Files (x86)\ZONEPOINT) and look for dedicated subfolders that store technical files, configuration, or data.Affected if The application directory contains dedicated folders with technical files accessible to the system.
-
Inspect folder permissions on dedicated foldersRight-click on each dedicated folder, open Properties, go to the Security tab, and review which users and groups have permissions. Check for grants to "Users", "Authenticated Users", or other non-administrative groups with Modify or Full Control access.Affected if Any dedicated folder grants read, write, or modify permissions to unprivileged users or groups such as "Users" or "Authenticated Users".
-
Check for sensitive technical files accessible to other usersWithin the dedicated folders, enumerate files (e.g., configuration files, scripts, data files, logs) and verify their accessibility to unprivileged accounts by checking file ownership and effective permissions.Affected if Sensitive or technical files are present in folders with overly permissive access controls, allowing manipulation by unprivileged users.
If ZONEPOINT version 2024.1 or earlier is installed and its dedicated folders grant access to unprivileged users, the environment is affected by this privilege escalation vulnerability.
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 ZONEPOINT configuration to restrict folder access permissions according to vendor security guidance, ensuring dedicated folders are only accessible to authorized users and service accounts.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46467 — 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-46467 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