dbcve.org
OdysseyApplication · Odyssey Project

CVE-2021-43766

HIGH · 8.1 CVSS v3.1 Published 2022-08-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
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.

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 · moderate confidence

Odyssey connection pooler has a SQL injection vulnerability during initial connection establishment when using certificate Common Name for client authentication. A man-in-the-middle attacker can inject arbitrary SQL queries despite SSL certificate verification being enabled, similar to CVE-2021-23214 in PostgreSQL. The vulnerability stems from unencrypted bytes being passed to the server during the connection handshake phase.

MitigationReview Odyssey configuration and consider disabling CN-based certificate authentication until patched; implement additional network-level controls to prevent MITM 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
OdysseyApplication
Affected:= 1.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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 installed Odyssey version
    Run 'odyssey --version' or check the package manager for the installed odyssey package version
    Affected if The installed version is exactly 1.1 (Odyssey version 1.1)
  2. Locate Odyssey configuration file
    Find the odyssey configuration file (commonly at /etc/odyssey.conf or /etc/odyssey/odyssey.conf) and review the 'listen' and 'auth' directives
    Affected if A configuration file exists and Odyssey is configured to accept client connections
  3. Check client certificate authentication settings
    In the configuration file, look for 'auth' blocks and check if 'cert' or 'cert_verify' options are present and enabled
    Affected if Certificate-based client authentication is configured (cert or cert_verify is set)
  4. Verify if Common Name (CN) extraction is in use
    Look for configuration options that extract or use the certificate Common Name, such as 'cn' or 'cn_verify' in the auth block
    Affected if CN-based certificate authentication is enabled (cn or cn_verify options are present and set)
  5. Confirm SSL certificate verification is enabled
    Check for 'tls' or 'ssl' configuration options in the listen block, verify TLS/SSL is required for connections
    Affected if TLS/SSL is required for connections (tls mode is set to 'verify' or 'verify_ca')

A user is affected if they run Odyssey 1.1 with TLS/SSL enabled and have CN-based certificate authentication (cn or cn_verify) configured for client connections, allowing a man-in-the-middle attacker to inject SQL during the handshake.

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

Review Odyssey configuration and consider disabling CN-based certificate authentication until patched; implement additional network-level controls to prevent MITM attacks.

Recommended fix Moderate confidence

Odyssey 1.1.1 or later stable release

  1. 1. Identify the current Odyssey version in use by checking the installed package or binary version
  2. 2. Obtain the latest stable release of Odyssey from the official GitHub repository (github.com/yandex/odyssey)
  3. 3. Upgrade Odyssey to the latest version which contains the fix for the SQL injection vulnerability (version 1.1.1 or later)
  4. 4. After upgrading, verify that the configuration for certificate Common Name client authentication still functions correctly
  5. 5. Test SSL/TLS connections to ensure certificate verification and encryption are working as expected
  6. 6. Monitor logs for any unusual SQL query patterns that could indicate exploitation attempts
Caveat Review release notes for any configuration or behavioral changes between 1.1 and the target version

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

Fix this in Odyssey Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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