dbcve.org
PlatformApplication · 1e

CVE-2023-45162

CRITICAL · 9.8 CVSS v3.1 Published 2023-10-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Affected 1E Platform versions have a Blind SQL Injection vulnerability that can lead to arbitrary code execution.  Application of the relevant hotfix remediates this issue. for v8.1.2 apply hotfix Q23166 for v8.4.1 apply hotfix Q23164 for v9.0.1 apply hotfix Q23169 SaaS implementations on v23.7.1 will automatically have hotfix Q23173 applied. Customers with SaaS versions below this are urged to upgrade urgently - please contact 1E to arrange this

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

A blind SQL injection vulnerability in 1E Platform versions 8.1.2, 8.4.1, and 9.0.1 allows attackers to inject malicious SQL queries through unsanitized input, which can lead to arbitrary code execution on the underlying database and system.

MitigationApply the appropriate vendor hotfix (Q23166 for v8.1.2, Q23164 for v8.4.1, Q23169 for v9.0.1) or upgrade SaaS deployments to v23.7.1 which includes hotfix Q23173.

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:= 8.1.2= 8.4.1= 9.0.1= 23.7.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 1E Platform version
    Locate the installed version of 1E Platform by checking the application itself, typically found in the product UI under About or Version information, or by querying the platform's configuration files or registry entries where version metadata is stored.
    Affected if The installed version is 8.1.2, 8.4.1, 9.0.1, or 23.7.1
  2. Confirm web interface or API is accessible
    Verify whether the 1E Platform web interface or any exposed API endpoints are reachable from network locations where untrusted input could be submitted.
    Affected if The web interface or API is exposed without proper network segmentation or authentication barriers.
  3. Identify user input points
    Review the 1E Platform for any features, search functions, forms, or API parameters that accept user-supplied input which could be passed to database queries.
    Affected if Any unsanitized user input fields or parameters exist that interface directly with database operations.
  4. Review database query logs
    Examine database logs for any unexpected or anomalous SQL query patterns that may indicate injection attempts, focusing on queries containing UNION, OR, AND, or SLEEP commands typical of blind SQL injection.
    Affected if Suspicious SQL patterns appear in logs originating from 1E Platform application connections.

Your environment is affected if the installed 1E Platform version is 8.1.2, 8.4.1, 9.0.1, or 23.7.1 and the platform accepts external user input through its web interface or API endpoints.

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 the appropriate vendor hotfix (Q23166 for v8.1.2, Q23164 for v8.4.1, Q23169 for v9.0.1) or upgrade SaaS deployments to v23.7.1 which includes hotfix Q23173.

Recommended fix High confidence

Apply respective hotfix (Q23166 for v8.1.2, Q23164 for v8.4.1, Q23169 for v9.0.1); SaaS customers should upgrade to v23.7.1 which includes Q23173

  1. For 1E Platform v8.1.2: Apply hotfix Q23166 to remediate the SQL injection vulnerability
  2. For 1E Platform v8.4.1: Apply hotfix Q23164 to remediate the SQL injection vulnerability
  3. For 1E Platform v9.0.1: Apply hotfix Q23169 to remediate the SQL injection vulnerability
  4. For SaaS customers on versions below v23.7.1: Contact 1E urgently to arrange upgrade to v23.7.1 or later, which includes hotfix Q23173
  5. For SaaS customers on v23.7.1: Hotfix Q23173 is automatically applied

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

Fix this in Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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