LiveActive security incident?Get immediate response
CVE Record

CVE-2021-35193: Patterson Application Service in Patterson Eaglesoft 18 through 21 accepts the same certificate authenticat...

Patterson Application Service in Patterson Eaglesoft 18 through 21 accepts the same certificate authentication across different customers' installations (that have the same software version). This provides remote access to SQL database credentials. (In the normal use of the product, retrieving those credentials only occurs after a username/password authentication step; however, this authentication step is on the client side, and an attacker can develop their own client that skips this step.)

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Eaglesoft 18 through 21 reportedly reused certificate authentication across customer installations of the same software version. That could let a remote actor obtain SQL database credentials without completing the normal username and password check, because that check occurs client-side. The public bundle does not include a vendor advisory, CVSS score, or confirmed fix. Exposure is most likely where Patterson Eaglesoft versions 18 through 21 are deployed and the Patterson Application Service is reachable from untrusted networks or unmanaged endpoints. The bundle lists affected versions but does not provide CPEs, deployment defaults, ports, or fixed versions. Prioritize remediation for any internet-reachable or broadly reachable Eaglesoft deployment. The issue involves database credential exposure, but available public evidence lacks a CVSS score, vendor fix detail, and exploitation confirmation. Mitigation focus: Ask Patterson for supported fixed versions and configuration guidance.; Restrict Patterson Application Service access to trusted hosts or VPN only.; Upgrade or replace affected Eaglesoft 18 through 21 deployments when vendor guidance identifies a safe version..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-35193 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.