dbcve.org
InlongApplication · Apache

CVE-2023-31454

HIGH · 7.5 CVSS v3.1 Published 2023-05-22
Fix available
A fix is available. Upgrade to after 1.6.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
Incorrect Permission Assignment for Critical Resource Vulnerability in Apache Software Foundation Apache InLong.This issue affects Apache InLong: from 1.2.0 through 1.6.0.  The attacker can bind any cluster, even if he is not the cluster owner. Users are advised to upgrade to Apache InLong's 1.7.0 or cherry-pick [1] to solve it.[1] https://github.com/apache/inlong/pull/7947 https://github.com/apache/inlong/pull/7947

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.2.0 through 1.6.0 have an Incorrect Permission Assignment vulnerability where authenticated users can bind to any cluster regardless of ownership. This is a broken access control issue allowing unauthorized cluster binding by non-owner users.

MitigationUpgrade to Apache InLong 1.7.0 or cherry-pick the fix from PR #7947 to enforce proper cluster ownership validation before allowing binding operations.

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.2.0, <= 1.6.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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 version
    Locate and inspect the InLong installation to determine the exact version number (such as checking version files, startup logs, or admin UI about page)
    Affected if The installed version falls within >= 1.2.0 and <= 1.6.0
  2. Identify cluster configuration
    Access the InLong admin interface or configuration files to list existing clusters and their ownership metadata
    Affected if Clusters exist in the system and at least one cluster is owned by a different user than the current user
  3. Test cluster binding permission
    Using an authenticated user account that does not own a particular cluster, attempt to bind to that cluster through the InLong API or UI
    Affected if The binding operation succeeds without ownership validation failing - indicating the broken access control is present
  4. Verify cluster ownership validation
    Review server-side logs or audit records when a non-owner attempts cluster binding to confirm whether ownership checks are enforced
    Affected if No ownership validation occurs or the binding succeeds for non-owner users

A user is affected if Apache InLong version 1.2.0 through 1.6.0 is installed and authenticated users can bind to clusters they do not own without receiving a permission denial.

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

Upgrade to Apache InLong 1.7.0 or cherry-pick the fix from PR #7947 to enforce proper cluster ownership validation before allowing binding operations.

Recommended fix High confidence

Apache InLong 1.7.0

  1. 1. Backup your current InLong installation including database and configuration files
  2. 2. Review the Apache InLong 1.7.0 release notes and upgrade documentation for any migration requirements
  3. 3. Download Apache InLong version 1.7.0 from the official Apache distribution mirrors
  4. 4. Stop the currently running InLong services
  5. 5. Run database migration scripts if provided in the 1.7.0 release notes
  6. 6. Upgrade all InLong components (inlong-manager, inlong-dataproxy, inlong-audit, inlong-tubemq-manager, etc.) to version 1.7.0
  7. 7. Start the upgraded InLong services
  8. 8. Verify that users can no longer bind to clusters they do not own - test that cluster ownership permissions are correctly enforced
Caveat Review 1.7.0 release notes for any breaking changes between your current version and 1.7.0; minor version upgrades typically have minimal breaking changes

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

Fix this in Inlong Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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