dbcve.org
Zed\!Application · Primx

CVE-2023-50440

MEDIUM · 5.5 CVSS v3.1 Published 2023-12-13
Fix available
A fix is available. Upgrade to 2023.5 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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; ZEDMAIL for Windows before 2023.5; ZED! for Windows, Mac, Linux before 2023.5; ZEDFREE for Windows, Mac, Linux before 2023.5; or ZEDPRO for Windows, Mac, Linux before 2023.5 can be modified by an unauthenticated attacker to include a UNC reference so that it could trigger network access to an attacker-controlled computer when opened by the victim.

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 container files can be modified by an unauthenticated attacker to embed a UNC path reference. When a victim opens the tampered container, the application attempts to access the attacker-controlled network path (e.g., \\attacker-server\share), causing the victim's system to initiate an outbound SMB connection to the attacker's infrastructure, enabling potential information disclosure or relay attacks.

MitigationUpdate PRIMX ZED products to the fixed versions: ZED! for Windows Q.2020.3+ or Q.2021.2+, ZONECENTRAL Q.2021.2+ or 2023.5+, ZEDMAIL 2023.5+, ZED!/ZEDFREE/ZEDPRO 2023.5+ (or later). Additionally, block outbound SMB (ports 445/139) to untrusted networks as a compensating control.

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:< 2023.5< 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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 ZED!, ZEDMAIL, or ZONECENTRAL applications installed on the system via Programs and Features (Windows) or by searching for PRIMX in the Start menu
    Affected if Any of these PRIMX products are installed
  2. Determine installed version of PRIMX ZED!
    Right-click the ZED! application shortcut, select Properties, and check the Details tab for the version number, or open the application and look in Help > About
    Affected if Version is < 2023.5, or >= 2023.0 and < 2023.5, or >= q.2021.0 and < q.2021.2, or < q.2020.3
  3. Determine installed version of PRIMX ZEDMAIL
    Right-click the ZEDMAIL application shortcut, select Properties, and check the Details tab for the version number, or open the application and look in Help > About
    Affected if Version is < 2023.5
  4. Determine installed version of PRIMX ZONECENTRAL
    Right-click the ZONECENTRAL application shortcut, select Properties, and check the Details tab for the version number, or open the application and look in Help > About
    Affected if Version is < q.2021.2, or >= 2023.0 and < 2023.5

A user is affected if any PRIMX ZED!, ZEDMAIL, or ZONECENTRAL version falls within the specified vulnerable ranges and the application is used to open container files.

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

Update PRIMX ZED products to the fixed versions: ZED! for Windows Q.2020.3+ or Q.2021.2+, ZONECENTRAL Q.2021.2+ or 2023.5+, ZEDMAIL 2023.5+, ZED!/ZEDFREE/ZEDPRO 2023.5+ (or later). Additionally, block outbound SMB (ports 445/139) to untrusted networks as a compensating control.

Recommended fix High confidence

Upgrade to PRIMX 2023.5 (or Q.2021.2 minimum, depending on current version branch)

  1. Identify the currently installed PRIMX product (ZED!, ZEDMAIL, ZONECENTRAL, ZEDFREE, or ZEDPRO) and its exact version number
  2. Navigate to the official PRIMX website (www.primx.eu) to download the latest qualified version
  3. If currently using a version before Q.2020.3, upgrade to Q.2020.3 or later (preferably Q.2021.2 or 2023.5 for broadest coverage)
  4. If currently using version Q.2021.0 through Q.2021.1, upgrade to Q.2021.2 or later (preferably 2023.5)
  5. If currently using version 2023.0 through 2023.4, upgrade to version 2023.5 or later
  6. For ZEDMAIL, ensure upgrade to version 2023.5 or later
  7. For ZONECENTRAL, ensure upgrade to version Q.2021.2 or later (if pre-Q.2021.2), or 2023.5 or later (if 2023.0-2023.4)
  8. After upgrade, verify the new version by checking the application's about or version information
Caveat Standard upgrade; ensure backup of existing containers before upgrade as a precautionary measure

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

Fix this in Zed\! Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50440 — 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-50440 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