CVE-2024-46464
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 · uneditedIn PRIMX ZED Enterprise up to 2024.3, technical files stored in local folders with common user access can be manipulated to render the host computer unavailable or to execute programs with an elevation of privilege.
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 confidencePRIMX ZED Enterprise up to version 2024.3 stores technical files in local folders that are accessible to common users without proper access controls. Low-privilege users can manipulate these files to either cause denial of service (rendering the host unavailable) or achieve privilege escalation by executing programs with elevated permissions.
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 PRIMX ZED Enterprise installation and versionLocate the PRIMX ZED Enterprise installation directory and check the version information, typically found in the application metadata, about dialog, or version file within the install folder. Compare the installed version to the affected range (versions up to and including 2024.3).Affected if The installed version is 2024.3 or lower, indicating the application is vulnerable.
-
Identify technical file storage locationsLocate folders where PRIMX ZED Enterprise stores technical files such as logs, configuration files, temporary files, or data exchange files. These are typically within the application installation directory or in a dedicated data folder under the user's profile or program data.Affected if The application stores technical files in local folders that exist on the system.
-
Examine file permissions on storage directoriesUse file system auditing tools or commands (such as icacls on Windows or ls -la on Linux) to inspect the access control lists on the identified technical file storage directories.Affected if Users without administrative privileges have write, modify, or execute permissions on directories containing technical files.
-
Test write access for low-privilege usersIf possible, attempt to create or modify files in the technical file storage locations using a standard non-administrator user account to confirm whether write access is improperly granted.Affected if A standard user account can successfully write or modify files in directories intended for technical storage.
-
Check for executable files in accessible locationsList all files in the technical file storage directories and identify any executable files (scripts, binaries, or configuration files that could be manipulated to trigger execution).Affected if Executable or script files exist in directories where low-privilege users have write access.
A user is affected if PRIMX ZED Enterprise version 2024.3 or lower is installed and technical file storage directories grant write access to non-privileged users, allowing potential manipulation for denial of service or 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 dataImplement strict file system permissions on technical file storage locations to prevent modification by non-privileged users, or apply vendor-supplied security patches to harden file handling routines.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46464 — 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-46464 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