dbcve.org
EaglesoftApplication · Pattersondental

CVE-2022-37710

HIGH · 7.8 CVSS v3.1 Published 2022-11-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Patterson Dental Eaglesoft 21 has AES-256 encryption but there are two ways to obtain a keyfile: (1) keybackup.data > License > Encryption Key or (2) Eaglesoft.Server.Configuration.data > DbEncryptKeyPrimary > Encryption Key. Applicable files are encrypted with keys and salt that are hardcoded into a DLL or EXE file.

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

Patterson Dental Eaglesoft 21 stores AES-256 encryption keys and salt values hardcoded within DLL or EXE files. The encryption keys can be extracted from two accessible locations: keybackup.data (License > Encryption Key) and Eaglesoft.Server.Configuration.data (DbEncryptKeyPrimary > Encryption Key). An attacker with local access or the ability to read these files can obtain the hardcoded keys and decrypt sensitive data stored by the application.

MitigationReplace hardcoded encryption keys with dynamically generated keys managed through a secure key management system (KMS) or hardware security module (HSM). Implement proper key derivation functions and ensure keys are not stored in plaintext within application binaries.

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
EaglesoftApplication
Affected:= 21.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Confirm Eaglesoft 21 installation
    Check for Eaglesoft installation directory (commonly C:\Program Files\Patterson Dental\Eaglesoft or similar) and verify version in program files or registry at HKEY_LOCAL_MACHINE\SOFTWARE\Patterson Dental\Eaglesoft
    Affected if Eaglesoft version 21.0 is installed
  2. Locate keybackup.data file
    Search for keybackup.data file in Eaglesoft data directories, typically found in the application data folder or configuration folder within the Eaglesoft installation directory
    Affected if keybackup.data file exists and contains plaintext encryption keys under License > Encryption Key section
  3. Locate Eaglesoft.Server.Configuration.data
    Search for Eaglesoft.Server.Configuration.data file in Eaglesoft configuration or data directories, commonly in AppData or program data folders
    Affected if Eaglesoft.Server.Configuration.data exists and contains DbEncryptKeyPrimary with plaintext encryption keys
  4. Inspect hardcoded keys in binaries
    Open DLL and EXE files in Eaglesoft installation directory with a hex editor or strings utility and search for AES-256 key patterns or readable key strings
    Affected if Hardcoded AES-256 encryption keys or salt values are found in any DLL or EXE files within the Eaglesoft installation
  5. Verify key storage exposure
    Open the identified data files (keybackup.data and Eaglesoft.Server.Configuration.data) in a text editor and check if encryption keys appear in plaintext rather than being referenced from an external secure key management system
    Affected if Encryption keys are stored in plaintext within these configuration files accessible to any user with file read permissions

If Eaglesoft 21.0 is installed and any configuration files contain plaintext AES-256 encryption keys that can be read without elevated privileges, the environment is affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace hardcoded encryption keys with dynamically generated keys managed through a secure key management system (KMS) or hardware security module (HSM). Implement proper key derivation functions and ensure keys are not stored in plaintext within application binaries.

Fix this in Eaglesoft Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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