CVE-2023-50442
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 · uneditedEncrypted folders created by PRIMX ZONECENTRAL through 2023.5 can be modified by a local attacker (with appropriate privileges) so that specific file types are excluded from encryption temporarily. (This modification can, however, be detected, as described in the Administrator Guide.)
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 ZONECENTRAL through version 2023.5 contains a local privilege manipulation vulnerability where an attacker with appropriate (elevated) privileges can modify encrypted folder configurations to exclude specific file types from encryption temporarily. This creates a window where files that should be protected are written unencrypted to disk. The modification is detectable through built-in mechanisms described in the Administrator Guide.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2023.5CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
-
Identify the installed PRIMX ZONECENTRAL versionOpen the PRIMX ZONECENTRAL management console or check the software version through the system control panel (usually found under Programs and Features or via the product's 'About' dialog)Affected if The installed version is 2023.5 or any earlier version (any version <= 2023.5 is affected)
-
Review encrypted folder configuration settingsAccess the ZONECENTRAL administration interface and navigate to the encrypted folder configuration panel. Inspect the list of protected folders and any associated file type filters or exclusion rules that may be definedAffected if Any folder configuration shows file type exclusions or modified encryption rules that were not authorized by your security policy
-
Examine audit and event logs for configuration changesOpen the ZONECENTRAL built-in audit logging system (typically accessible through the administrator console or Windows Event Viewer under the product's event log source) and search for events related to folder configuration modifications, policy changes, or encryption exclusion rule changesAffected if Audit logs contain entries indicating unauthorized or unexpected changes to encrypted folder configurations or file type exclusion rules
-
Inspect current encryption policy for anomaliesReview the active ZONECENTRAL encryption policy through the management console. Compare the currently enforced file type encryption rules against your documented baseline configurationAffected if The active policy includes file type exclusions or modified rules that differ from your documented secure baseline
A user is affected if they are running PRIMX ZONECENTRAL version 2023.5 or earlier AND their encrypted folder configurations show unauthorized file type exclusions or modifications detected through the product's built-in audit mechanisms.
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 dataUpgrade to a version beyond 2023.5 and review the Administrator Guide for detection and audit capabilities to identify any unauthorized folder configuration modifications. Investigate any detected modifications for potential data exfiltration.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50442 — 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-2023-50442 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