dbcve.org
InlongApplication · Apache

CVE-2023-35088

CRITICAL · 9.8 CVSS v3.1 Published 2023-07-25
Fix available
A fix is available. Upgrade to after 1.7.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
Improper Neutralization of Special Elements Used in an SQL Command ('SQL Injection') vulnerability in Apache Software Foundation Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.7.0.  In the toAuditCkSql method, the groupId, streamId, auditId, and dt are directly concatenated into the SQL query statement, which may lead to SQL injection attacks. Users are advised to upgrade to Apache InLong's 1.8.0 or cherry-pick [1] to solve it. [1] https://github.com/apache/inlong/pull/8198

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

SQL injection vulnerability in Apache InLong's toAuditCkSql method allows attackers to inject malicious SQL via unsanitized groupId, streamId, auditId, and dt parameters that are directly concatenated into SQL queries without proper parameterization.

MitigationUpgrade to Apache InLong 1.8.0 or apply the cherry-pick from PR #8198 which implements proper input sanitization/parameterization for the affected SQL queries.

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.7.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 installation and version
    Locate the InLong installation directory and check the version file or JAR manifest. Common locations include /opt/inlong or the deployed application's WEB-INF/lib directory. Run: find / -name 'inlong*' -type d 2>/dev/null | head -5, then check for version info in the directory.
    Affected if The installed version falls within range 1.4.0 to 1.7.0 inclusive
  2. Locate the toAuditCkSql method
    Search for files containing the toAuditCkSql method in the InLong codebase or deployed application. Use: grep -r 'toAuditCkSql' --include='*.java' .
    Affected if The method exists in the codebase, indicating the vulnerable code is present
  3. Verify audit/ClickHouse functionality is enabled
    Check InLong configuration files (typically in conf/ or config/ directory) for audit-related settings. Look for configurations enabling audit collection, particularly ClickHouse (Ck) audit sink configurations.
    Affected if Audit collection to ClickHouse is enabled and configured with the vulnerable endpoint accessible
  4. Check web/API exposure of the vulnerable endpoint
    Review the application's API routing configuration or web.xml to determine if endpoints utilizing toAuditCkSql are exposed via HTTP/HTTPS. Identify which REST controllers or API routes call this method.
    Affected if The audit-related API endpoints accepting groupId, streamId, auditId, and dt parameters are publicly or internally accessible

A user is affected if they are running Apache InLong version 1.4.0 through 1.7.0 with the audit/ClickHouse functionality enabled and the vulnerable toAuditCkSql endpoint exposed.

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.7.0
Interim mitigation

Upgrade to Apache InLong 1.8.0 or apply the cherry-pick from PR #8198 which implements proper input sanitization/parameterization for the affected SQL queries.

Recommended fix High confidence

1.8.0

  1. Backup your current InLong installation and database before upgrading
  2. Stop all InLong services to prevent data inconsistency during upgrade
  3. Upgrade Apache InLong from your current version (1.4.0-1.7.0) to version 1.8.0
  4. Start the upgraded InLong services and verify they are running correctly
  5. Verify that the SQL injection vulnerability is resolved by confirming the toAuditCkSql method no longer concatenates user inputs directly into SQL queries
Caveat Review the InLong 1.8.0 release notes for any breaking changes or migration requirements before upgrading

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

Fix this in Inlong Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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