dbcve.org
PlatformApplication · 1e

CVE-2023-5964

HIGH · 7.2 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to 23.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
The 1E-Exchange-DisplayMessageinstruction that is part of the End-User Interaction product pack available on the 1E Exchange does not properly validate the Caption or Message parameters, which allows for a specially crafted input to perform arbitrary code execution with SYSTEM permissions. This instruction only runs on Windows clients. To remediate this issue DELETE the instruction “Show dialogue with caption %Caption% and message %Message%” from the list of instructions in the Settings UI, and replace it with the new instruction 1E-Exchange-ShowNotification instruction available in the updated End-User Interaction product pack. The new instruction should show as “Show %Type% type notification with header %Header% and message %Message%” with a version of 7.1 or above.

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

The 1E Exchange-DisplayMessage instruction in the End-User Interaction product pack fails to properly validate the Caption and Message parameters, allowing specially crafted input to achieve arbitrary code execution with SYSTEM-level privileges. This is a parameter injection vulnerability specific to Windows clients.

MitigationDelete the vulnerable DisplayMessage instruction and replace it with the updated ShowNotification instruction (version 7.1+) which properly validates the Type, Header, and Message parameters.

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
PlatformApplication
Affected:< 23.0

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Identify the installed 1E Platform version
    Run the 1E platform installer with version check flag, or inspect the product's About/Version information in the 1E Console. On the server, check the 1E Platform version from the installer or registry if applicable.
    Affected if The installed version is lower than 23.0 (any version < 23.0 is affected)
  2. Locate the End-User Interaction product pack
    In the 1E Console, navigate to the product packs or instruction library section and search for 'End-User Interaction' or 'Exchange-DisplayMessage'. Alternatively, check the installation directory for the End-User Interaction pack files.
    Affected if The End-User Interaction product pack is installed on the system
  3. Verify the Exchange-DisplayMessage instruction exists
    In the 1E Console instruction browser, locate the DisplayMessage instruction under the Exchange category. Check its parameters: Caption and Message fields.
    Affected if The Exchange-DisplayMessage instruction with unsanitized Caption and Message parameters is present and available for use
  4. Confirm Windows client environment
    Verify that target endpoints are Windows machines running the 1E client, as this vulnerability is specific to Windows clients.
    Affected if Windows-based 1E clients are managed by the platform and the vulnerable instruction can be invoked against them

The environment is affected if 1E Platform version is below 23.0 AND the End-User Interaction product pack containing the Exchange-DisplayMessage instruction is installed and accessible to Windows clients.

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 23.0 or later
Fixed in 23.0
Interim mitigation

Delete the vulnerable DisplayMessage instruction and replace it with the updated ShowNotification instruction (version 7.1+) which properly validates the Type, Header, and Message parameters.

Recommended fix High confidence
  1. Navigate to the Settings UI in the 1E Exchange platform
  2. Locate the instruction named "Show dialogue with caption %Caption% and message %Message%" in the list of instructions
  3. DELETE this instruction from the list
  4. Download and install the updated End-User Interaction product pack containing version 7.1 or above of the 1E-Exchange-ShowNotification instruction
  5. Add the new instruction "Show %Type% type notification with header %Header% and message %Message%" to replace the deleted instruction

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

Fix this in Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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 locally
dbcve dependency scanner

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