LiveActive security incident?Get immediate response
CVE Record

CVE-2021-43766: Odyssey passes to server unencrypted bytes from man-in-the-middle When Odyssey is configured to use certifi...

Odyssey passes to server unencrypted bytes from man-in-the-middle When Odyssey is configured to use certificate Common Name for client authentication, a man-in-the-middle attacker can inject arbitrary SQL queries when a connection is first established, despite the use of SSL certificate verification and encryption. This is similar to CVE-2021-23214 for PostgreSQL.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-43766 affects Odyssey 1.1 in a specific client-certificate authentication setup. A network attacker positioned between client and Odyssey could inject SQL during connection setup, even though SSL verification and encryption are used.

Executive priority

Prioritize review if Odyssey sits on production database paths or handles privileged database users. The business risk is unauthorized SQL execution, but urgency depends on whether the specific vulnerable authentication mode is enabled.

Technical view

When Odyssey uses certificate Common Name for client authentication, it can pass attacker-controlled unencrypted bytes from a man-in-the-middle to the server at initial connection establishment. The issue is categorized as CWE-89 and is described as similar to PostgreSQL CVE-2021-23214.

Likely exposure

Exposure is most likely where Odyssey 1.1 is deployed and configured to authenticate clients using certificate Common Name. The source bundle does not identify other affected versions or deployment modes.

Exploitation context

No active exploitation is cited, and the CVE is not listed as CISA KEV in the provided bundle. Exploitation requires a man-in-the-middle position and the vulnerable Odyssey certificate Common Name authentication configuration.

Researcher notes

The provided record lacks CVSS, patch details, and confirmed exploitation. Analysis should stay scoped to Odyssey 1.1 and the Common Name client-authentication condition until vendor issue details or release notes confirm broader impact or remediation.

Mitigation direction

  • Inventory Odyssey deployments and identify any Odyssey 1.1 instances.
  • Check whether client authentication uses certificate Common Name.
  • Review Odyssey vendor guidance or the referenced GitHub issue for fixed versions or workarounds.
  • Reduce exposure of Odyssey connection paths to trusted networks where feasible.
  • Monitor database activity for unexpected queries around new connection events.

Validation and detection

  • Confirm Odyssey version and authentication configuration on each deployment.
  • Verify whether certificate Common Name authentication is enabled.
  • Review TLS and client-certificate settings against vendor guidance.
  • Check logs for anomalous database activity during connection establishment.
  • Document whether each instance is affected, mitigated, or awaiting vendor guidance.
Prepared
Confidence
medium
Sources
4

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.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-43766 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aOdysseyOdyssey 1.1Listed
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.