dbcve.org
Zed\!Application · Primx

CVE-2023-50439

MEDIUM · 5.3 CVSS v3.1 Published 2023-12-13
Fix available
A fix is available. Upgrade to 2023.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
ZED containers produced by PRIMX ZED! for Windows before Q.2020.3 (ANSSI qualification submission), ZED! for Windows before Q.2021.2 (ANSSI qualification submission), ZONECENTRAL for Windows before Q.2021.2 (ANSSI qualification submission), ZONECENTRAL for Windows before 2023.5, or ZEDMAIL for Windows before 2023.5 disclose the original path in which the containers were created, which allows an unauthenticated attacker to obtain some information regarding the context of use (project name, etc.).

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 · high confidence

ZED containers created by PRIMX products (ZED!, ZONECENTRAL, ZEDMAIL) for Windows leak the original filesystem path where the container was created, exposing potentially sensitive context like project or user names to unauthenticated attackers who can read the container metadata.

MitigationUpgrade to Q.2020.3 or later for ZED!, Q.2021.2 or later for ZONECENTRAL, or 2023.5 or later for ZEDMAIL to remove path disclosure from container metadata.

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
Zed\!Application
Affected:< q.2020.3>= 2023.0, < 2023.5>= q.2021.0, < q.2021.2
ZedmailApplication
Affected:< 2023.5
ZonecentralApplication
Affected:< q.2021.2>= 2023.0, < 2023.5

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed PRIMX product
    Check for PRIMX software installations: ZED!, ZEDMAIL, or ZONECENTRAL. Look in Program Files for PRIMX folders, or check installed programs list.
    Affected if Any PRIMX product (ZED!, ZEDMAIL, or ZONECENTRAL) is installed
  2. Determine product version
    Open the installed PRIMX product, go to Help > About or check the version in the software's main window. Alternatively, check the version in Add/Remove Programs or the program's executable properties.
    Affected if Version falls within affected ranges: ZED! (< q.2020.3; >= 2023.0, < 2023.5; >= q.2021.0, < q.2021.2), ZEDMAIL (< 2023.5), ZONECENTRAL (< q.2021.2; >= 2023.0, < 2023.5)
  3. Locate existing ZED containers
    Search for .zed container files created by the PRIMX product. Default locations may include user documents folders, project directories, or custom paths configured during container creation. Look for files with .zed extension.
    Affected if Any .zed container files exist on the system
  4. Inspect container metadata for path disclosure
    Open the container file or its associated metadata (check for .xml, .json, or hidden metadata files alongside the container). Look for fields that may contain the original filesystem path where the container was created, such as paths containing usernames, project folder names, or directory structures.
    Affected if Container metadata contains absolute filesystem paths revealing user names, project names, or directory structures from the original creation location

User is affected if a PRIMX product (ZED!, ZEDMAIL, or ZONECENTRAL) with a version in the affected ranges is installed AND any existing ZED containers contain original filesystem paths in their metadata that expose sensitive context like user or project names.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2023.5 or later
Fixed in 2023.5
Interim mitigation

Upgrade to Q.2020.3 or later for ZED!, Q.2021.2 or later for ZONECENTRAL, or 2023.5 or later for ZEDMAIL to remove path disclosure from container metadata.

Recommended fix High confidence

Q.2020.3, Q.2021.2, or 2023.5 (depending on product)

  1. Identify which PRIMX product is in use (ZED!, ZEDMAIL, or ZONECENTRAL)
  2. Determine the current installed version of the product
  3. If using ZED! for Windows: upgrade to Q.2020.3 (ANSSI qualified) or Q.2021.2 (ANSSI qualified) or version 2023.5 or later
  4. If using ZEDMAIL for Windows: upgrade to version 2023.5 or later
  5. If using ZONECENTRAL for Windows: upgrade to Q.2021.2 (ANSSI qualified) or version 2023.5 or later
  6. Verify the upgrade was successful by checking the product version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zed\! Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50439 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50439 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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