CVE-2024-46462
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 ZEDMAIL for Windows up to 2024.3 can be accessed by other users to misuse technical files and make them perform tasks with higher privileges. Configuration of ZEDMAIL 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 confidenceZEDMAIL for Windows versions up to 2024.3 have insecure default folder permissions on dedicated folders, allowing local unprivileged users to access technical files and execute tasks with elevated privileges due to improper access control configurations.
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.
-
Confirm ZEDMAIL installation and versionOpen Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or check Program Files for ZEDMAIL folder. Locate version information in uninstall string or version.txt file within the ZEDMAIL directory.Affected if ZEDMAIL version is 2024.3 or lower (any version up to and including 2024.3)
-
Locate ZEDMAIL dedicated foldersIdentify the ZEDMAIL installation directory (typically C:\Program Files\ZEDMAIL or C:\Program Files (x86)\ZEDMAIL) and any designated data/configuration folders created during setup.Affected if ZEDMAIL is installed and dedicated folders exist on the system
-
Examine folder permission settingsRight-click each ZEDMAIL folder, select Properties, go to Security tab, and review the entries under 'Group or user names'. Check whether Users, Everyone, or unprivileged groups have Read, Write, or Modify access.Affected if Users group or unprivileged accounts are granted Read, Write, or Modify permissions to ZEDMAIL folders
-
Verify unprivileged user accessUsing a standard (non-admin) Windows account or icacls.exe, attempt to list or access files within ZEDMAIL installation and data folders.Affected if Unprivileged users can successfully read, write, or modify files in ZEDMAIL dedicated folders
The environment is affected if ZEDMAIL version 2024.3 or lower is installed with default folder permissions that grant unprivileged users access to dedicated folders.
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 ZEDMAIL configuration to restrict folder access permissions according to vendor hardening guidance, ensuring dedicated folders are only accessible to authorized users and processes.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46462 — 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-46462 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