dbcve.org
InlongApplication · Apache

CVE-2023-43668

CRITICAL · 9.8 CVSS v3.1 Published 2023-10-16
Fix available
A fix is available. Upgrade to after 1.8.0 or later.
See remediation →
100/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
Authorization Bypass Through User-Controlled Key vulnerability in Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.8.0,  some sensitive params checks will be bypassed, like "autoDeserizalize","allowLoadLocalInfile".... .   Users are advised to upgrade to Apache InLong's 1.9.0 or cherry-pick [1] to solve it. [1]  https://github.com/apache/inlong/pull/8604

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 InLong versions 1.4.0-1.8.0 contain an authorization bypass vulnerability where user-controlled keys can bypass security checks on sensitive parameters including 'autoDeserialize' and 'allowLoadLocalInfile'. These parameters, when not properly validated, could allow attackers to enable dangerous deserialization behaviors or load local files, leading to potential remote code execution.

MitigationUpgrade to Apache InLong version 1.9.0 or apply the cherry-pick from GitHub PR #8604 to enforce proper validation of sensitive parameters and prevent authorization bypass.

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
InlongApplication
Affected:>= 1.4.0, <= 1.8.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
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 Apache InLong version
    Check the installed Apache InLong version in your environment (typically found in release files, logs, or admin interface) and compare it against the affected range: 1.4.0 to 1.8.0
    Affected if Installed version falls within 1.4.0-1.8.0 inclusive
  2. Locate MySQL or database connector configuration
    Search for configuration files or code that handle database connections, specifically looking for MySQL connector/J settings where user-controlled keys may be processed
    Affected if Database connector configs accept user-supplied parameter keys without validation
  3. Inspect autoDeserialize parameter exposure
    Review your InLong configuration and API endpoints to determine if users can control or influence the 'autoDeserialize' parameter value
    Affected if Users can set or influence autoDeserialize without proper authorization checks
  4. Inspect allowLoadLocalInfile parameter exposure
    Review your InLong configuration and API endpoints to determine if users can control or influence the 'allowLoadLocalInfile' parameter value
    Affected if Users can set or influence allowLoadLocalInfile without proper authorization checks
  5. Verify parameter validation logic
    Examine the code or configuration that processes sensitive database parameters (autoDeserialize, allowLoadLocalInfile) to confirm whether proper validation and authorization checks are enforced before use
    Affected if Sensitive parameters can bypass security validation when supplied by users

Your environment is affected if Apache InLong version 1.4.0-1.8.0 is running AND users can influence the autoDeserialize or allowLoadLocalInfile parameters without proper authorization validation.

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 a release after 1.8.0
Interim mitigation

Upgrade to Apache InLong version 1.9.0 or apply the cherry-pick from GitHub PR #8604 to enforce proper validation of sensitive parameters and prevent authorization bypass.

Recommended fix High confidence

Apache InLong 1.9.0

  1. 1. Back up your current Apache InLong installation, including all configuration files and databases
  2. 2. Stop the running InLong service
  3. 3. Download Apache InLong version 1.9.0 from the official Apache repository (https://inlong.apache.org/download/)
  4. 4. Install version 1.9.0 following the standard upgrade procedure in the Apache InLong documentation
  5. 5. Restore your configuration files, ensuring any new required configurations are added
  6. 6. Start the upgraded InLong service
  7. 7. Verify the service is running correctly and that the vulnerable endpoints are no longer exposed

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

Fix this in Inlong Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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