dbcve.org
PlatformApplication · 1e

CVE-2023-45163

HIGH · 7.2 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to 18.1 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-CommandLinePing instruction that is part of the Network product pack available on the 1E Exchange does not properly validate the input parameter, 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 download the updated Network product pack from the 1E Exchange and update the 1E-Exchange-CommandLinePing instruction to v18.1 by uploading it through the 1E Platform instruction upload UI

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-CommandLinePing instruction in the Network product pack fails to properly validate input parameters, enabling specially crafted input to achieve arbitrary code execution with SYSTEM-level privileges on Windows clients.

MitigationUpdate the 1E-Exchange-CommandLinePing instruction to version 18.1 by downloading the updated Network product pack from the 1E Exchange and uploading it through the 1E Platform instruction upload UI.

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:< 18.1

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. Check 1E Platform version
    Open 1E Platform admin console or check the installed software version on the 1E server. The version is typically visible in the About section or can be retrieved via the platform's help/about dialog.
    Affected if Version is below 18.1 (e.g., 18.0.x, 17.x, etc.)
  2. Verify Network product pack is installed
    Access the 1E Platform admin interface and navigate to the Product Packs or Instructions section. Look for the Network product pack in the list of installed packs.
    Affected if Network product pack is present in the installation
  3. Confirm 1E-Exchange-CommandLinePing instruction exists
    In the 1E Platform admin console, search for '1E-Exchange-CommandLinePing' in the instructions library or product pack contents. This instruction is part of the Network product pack.
    Affected if The instruction is listed and available for use
  4. Check for recent executions of the vulnerable instruction
    Review instruction execution logs in the 1E Platform console or check Windows event logs for executions of 1E-Exchange-CommandLinePing. Look for executions occurring within the timeframe the vulnerability was present.
    Affected if The instruction has been executed in the environment while running a version below 18.1

Environment is affected if 1E Platform version is below 18.1 AND the Network product pack containing the 1E-Exchange-CommandLinePing instruction is installed and has been used.

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

Update the 1E-Exchange-CommandLinePing instruction to version 18.1 by downloading the updated Network product pack from the 1E Exchange and uploading it through the 1E Platform instruction upload UI.

Recommended fix High confidence

v18.1

  1. Download the updated Network product pack from the 1E Exchange (exchange.1e.com)
  2. Access the 1E Platform instruction upload UI
  3. Upload the updated 1E-Exchange-CommandLinePing instruction version 18.1 to replace the vulnerable version

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

Fix this in Platform Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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