dbcve.org
InlongApplication · Apache

CVE-2023-30465

MEDIUM · 5.3 CVSS v3.1 Published 2023-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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.5.0. By manipulating the "orderType" parameter and the ordering of the returned content using an SQL injection attack, an attacker can extract the username of the   user with ID 1 from the "user" table, one character at a time.  Users are advised to upgrade to Apache InLong's 1.6.0 or cherry-pick [1] to solve it. https://programmer.help/blogs/jdbc-deserialization-vulnerability-learning.html [1] https://github.com/apache/inlong/issues/7529 https://github.com/apache/inlong/issues/7529

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 through 1.5.0 contain a SQL injection vulnerability in the 'orderType' parameter. This is a blind SQL injection allowing attackers to extract sensitive data (e.g., usernames) from the user table by manipulating query logic and observing behavioral differences based on true/false conditions.

MitigationUpgrade to Apache InLong 1.6.0 or apply the cherry-pick fix from the upstream repository to remediate this vulnerability.

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.5.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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Confirm Apache InLong is deployed
    Identify if Apache InLong services are running in your environment by checking for Java processes with 'inlong' in the command line, or by scanning your asset inventory for Apache InLong installations.
    Affected if Apache InLong is not present in your environment.
  2. Determine the installed InLong version
    Check the version of Apache InLong by examining the release manifest, the filename of the deployed JAR/WAR artifacts, or the version reported by the application's startup logs.
    Affected if The installed version is 1.4.0 or 1.5.0.
  3. Identify if the user list API is exposed
    Locate the web interface or API endpoint that provides user management functionality. This typically involves the /manager or /api/user endpoints based on InLong's architecture.
    Affected if The user management API is accessible without authentication or with low-privilege user access.
  4. Inspect access logs for suspicious orderType values
    Review the HTTP access logs or application logs for requests to the user API that contain unusual string values in an 'orderType' parameter, especially those with SQL operators, quoted strings, or boolean logic patterns.
    Affected if Log entries show SQL injection patterns in the orderType parameter from external sources.

Your environment is affected if Apache InLong version 1.4.0 or 1.5.0 is running and the user management API with the orderType parameter is network-accessible.

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

Upgrade to Apache InLong 1.6.0 or apply the cherry-pick fix from the upstream repository to remediate this vulnerability.

Recommended fix High confidence

1.6.0

  1. Backup your current InLong installation and database before proceeding with the upgrade.
  2. Upgrade Apache InLong from version 1.4.0 or 1.5.0 to version 1.6.0 following the official upgrade documentation.
  3. After upgrading, verify the application starts successfully and all services are operational.
  4. Test that the 'orderType' parameter is no longer vulnerable to SQL injection by attempting parameterized queries.
  5. Alternatively, if staying on the current version is necessary, cherry-pick the fix from GitHub issue #7529 (https://github.com/apache/inlong/issues/7529) and rebuild the affected component.
Caveat Review the InLong 1.6.0 release notes for any breaking changes or configuration changes required from 1.4.0/1.5.0

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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