dbcve.org
DorisApplication · Apache

CVE-2022-23942

HIGH · 7.5 CVSS v3.1 Published 2022-04-26
Fix available
A fix is available. Upgrade to 1.0.0 or later.
See remediation →
84/100
Remediation priority · High
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
Apache Doris, prior to 1.0.0, used a hardcoded key and IV to initialize the cipher used for ldap password, which may lead to information disclosure.

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

Apache Doris prior to version 1.0.0 uses a hardcoded encryption key and initialization vector (IV) to initialize the cipher for encrypting LDAP passwords. Because the key and IV are embedded in the source code, anyone with access to the codebase can derive them and decrypt stored LDAP passwords, leading to credential disclosure.

MitigationUpgrade to Apache Doris 1.0.0 or later, which implements proper key management for LDAP password encryption.

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
DorisApplication
Affected:< 1.0.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 Apache Doris installation and version
    Run 'select version();' on the MySQL protocol port or check the fe/be conf files for version information
    Affected if The installed version is prior to 1.0.0
  2. Determine if LDAP authentication is configured
    Inspect the LDAP configuration files or fe.conf for LDAP-related settings such as ldap_authentication_enabled, ldap_user_info, or ldap_password
    Affected if LDAP authentication is enabled and LDAP credentials are stored in the system
  3. Locate LDAP password storage
    Check for LDAP password entries in the fe/conf directory or in configuration files that store encrypted LDAP credentials
    Affected if Encrypted LDAP passwords exist in configuration or database storage
  4. Inspect encryption configuration
    Look for hardcoded key or iv parameters in source code under encryption-related classes, or in fe/conf files for ldap authentication settings
    Affected if A hardcoded encryption key or IV is present in source code or configuration files used for LDAP password encryption
  5. Verify key management implementation
    Check if the Doris installation uses external key management or if encryption keys are sourced from environment variables or secure vaults rather than hardcoded values
    Affected if Encryption keys are embedded in source code rather than externally managed

You are affected if Apache Doris version is below 1.0.0 and LDAP authentication is configured with stored encrypted passwords using the built-in hardcoded encryption key.

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
Upgrade available Upgrade to 1.0.0 or later
Fixed in 1.0.0
Interim mitigation

Upgrade to Apache Doris 1.0.0 or later, which implements proper key management for LDAP password encryption.

Recommended fix High confidence

Apache Doris 1.0.0 or later

  1. Upgrade Apache Doris to version 1.0.0 or later to obtain the fixed encryption implementation
  2. After upgrade, verify that LDAP authentication is working correctly with the new cipher implementation
  3. If using custom LDAP integrations, test that password encryption/decryption works as expected with the new version

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

Fix this in Doris Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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