dbcve.org
ClientApplication · 1e

CVE-2023-45160

HIGH · 8.8 CVSS v3.1 Published 2023-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
In the affected version of the 1E Client, an ordinary user could subvert downloaded instruction resource files, e.g., to substitute a harmful script. by replacing a resource script file created by an instruction at run time with a malicious script. The 1E Client's temporary directory is now locked down in the released patch. Resolution: This has been fixed in patch Q23094  This issue has also been fixed in the Mac Client in updated versions of Non-Windows release v8.1.2.62 - please re-download from the 1E Support site. Customers with Mac Client versions higher than v8.1 will need to upgrade to v23.11 to remediate this vulnerability.

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 Client before the patch allowed unprivileged users to modify temporary script files created during instruction execution. An attacker could replace these runtime-generated resource files with malicious scripts, potentially achieving arbitrary code execution with the privileges of the 1E Client service.

MitigationApply vendor patch Q23094 for Windows clients; upgrade Mac clients to v23.11 (or v8.1.2.62 for v8.1 branch) to secure the temporary directory and prevent file substitution attacks.

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
ClientApplication
Affected:= 8.1.2.62= 8.4.1.159= 9.0.1.88= 23.7.1.151

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Client installation
    Check for 1E Client service or executable. On Windows, open Services.msc and look for '1E Client' service, or check Program Files for 1E folder. On Mac, check /Applications for 1E Client or run 'system_profiler SPApplications' and search for 1E.
    Affected if 1E Client is not found on the system, the system is not affected.
  2. Identify installed version
    On Windows, right-click the 1E Client executable in Program Files\1E\Client\ and select Properties > Details to view File Version. On Mac, run 'pkgutil --info com.1e.client' or check the app bundle Info.plist for CFBundleVersion.
    Affected if Installed version matches one of the vulnerable versions (8.1.x before 8.1.2.62, 8.4.x before 8.4.1.159, 9.0.x before 9.0.1.88, or 23.7.x before 23.7.1.151). Compare your version to these ranges.
  3. Check temporary script directory permissions
    Locate the temporary directory used by 1E Client for script execution. Common locations: %TEMP%\1E or C:\ProgramData\1E\Temp. Use icacls (Windows) or ls -la (Mac) to list folder permissions and verify if standard users have Write or Modify access to this directory.
    Affected if Standard (non-admin) users have Write or Modify permissions to the temporary script directory.
  4. Confirm instruction execution feature is enabled
    Check 1E Client configuration. On Windows, examine config files in C:\ProgramData\1E\Client\ or registry keys under HKLM\SOFTWARE\1E\Client. Look for settings related to InstructionExecution, ScriptExecution, or TSEngine that are set to enabled or true.
    Affected if Instruction execution or script execution feature is enabled in 1E Client configuration.

System is affected if 1E Client is installed with a version prior to the fixed releases AND the temporary directory used for script execution allows write access from unprivileged user accounts.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch Q23094 for Windows clients; upgrade Mac clients to v23.11 (or v8.1.2.62 for v8.1 branch) to secure the temporary directory and prevent file substitution attacks.

Recommended fix Moderate confidence

Apply patch Q23094; for Mac clients: upgrade to v23.11

  1. Apply patch Q23094 to remediate the vulnerability in the 1E Client
  2. For Mac Clients: If running versions higher than v8.1, upgrade to v23.11 to remediate this vulnerability
  3. Verify the temporary directory lockdown is in place after applying the patch
  4. Re-download the Mac Client v8.1.2.62 from the 1E Support site if that specific version is required

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

Fix this in Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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