PlatformApplication · 1e

CVE-2023-45161

HIGH · 7.2 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to 20.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-URLResponseTime instruction that is part of the Network product pack available on the 1E Exchange does not properly validate the URL 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-URLResponseTime instruction to v20.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-URLResponseTime instruction in the Network product pack fails to properly validate the URL parameter, allowing specially crafted input to achieve arbitrary code execution with SYSTEM privileges on Windows clients.

MitigationDownload the updated Network product pack (v20.1) from the 1E Exchange and upload it through the 1E Platform instruction upload UI to replace the vulnerable instruction.

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:< 20.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. Verify 1E Platform version
    Access the 1E Platform administration console or check the platform installation to determine the installed version number
    Affected if The platform version is below 20.1 (e.g., 20.0.x, 19.x, etc.)
  2. Confirm Network product pack is loaded
    Check the installed product packs within the 1E Platform console to verify the Network product pack is present
    Affected if The Network product pack is installed and loaded in the platform
  3. Locate the URLResponseTime instruction
    Browse the instruction library in the 1E Platform to find the 1E-Exchange-URLResponseTime instruction
    Affected if The URLResponseTime instruction exists in the instruction library
  4. Check instruction execution permissions
    Review the permissions and configuration settings for the URLResponseTime instruction to determine which users or roles can execute it
    Affected if The instruction is accessible to users who can supply arbitrary URL input

A user is affected if they are running 1E Platform version below 20.1 with the Network product pack loaded containing the vulnerable URLResponseTime instruction that can accept user-supplied URL parameters.

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

Download the updated Network product pack (v20.1) from the 1E Exchange and upload it through the 1E Platform instruction upload UI to replace the vulnerable instruction.

Recommended fix High confidence

20.1

  1. Download the updated Network product pack from the 1E Exchange
  2. Access the 1E Platform instruction upload UI
  3. Upload the updated Network product pack to remediate the vulnerability
  4. Verify the 1E-Exchange-URLResponseTime instruction is updated to v20.1

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

Fix this in Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45161 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