dbcve.org
InlongApplication · Apache

CVE-2023-31103

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
Exposure of Resource to Wrong Sphere Vulnerability in Apache Software Foundation Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.6.0.  Attackers can change the immutable name and type of cluster of InLong. Users are advised to upgrade to Apache InLong's 1.7.0 or cherry-pick https://github.com/apache/inlong/pull/7891 https://github.com/apache/inlong/pull/7891 to solve it.

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

This is an authorization bypass vulnerability where authenticated attackers can modify the immutable name and type properties of InLong clusters. The issue stems from insufficient access control checks on cluster configuration endpoints, allowing users to alter cluster attributes that should be read-only after creation.

MitigationUpgrade to Apache InLong 1.7.0 or apply the cherry-pick from GitHub PR #7891 to implement proper authorization checks on cluster management 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.4.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. Identify InLong installation version
    Locate the InLong version file or check the pom.xml, MANIFEST.MF, or version.properties in the deployed InLong installation directory. Alternatively, check the InLong dashboard footer or admin interface for the version number.
    Affected if The installed version is between 1.4.0 and 1.6.0 inclusive.
  2. Verify cluster management API is accessible
    Confirm the InLong manager service API endpoint is reachable. Check if the /api/inlong/manager/cluster or similar cluster management REST endpoints are exposed and accessible to authenticated users.
    Affected if The cluster management API is exposed and responds to authenticated requests.
  3. Check if multi-user authentication is enforced
    Review the InLong authentication configuration files (application.yml or manager.conf) to determine if proper access control and multi-user authentication are enabled for cluster operations.
    Affected if Multi-user or role-based access control is not properly configured, allowing any authenticated user to modify cluster properties.
  4. Inspect cluster modification audit logs
    Review InLong audit or audit logs for any POST/PUT requests to cluster modification endpoints that altered the name or type fields of existing clusters after their initial creation.
    Affected if There are records of cluster name or type modifications occurring after cluster creation, indicating the vulnerability may have been exploited.

A user is affected if Apache InLong version 1.4.0 through 1.6.0 is installed and the cluster management interface is accessible to authenticated users without proper authorization checks on immutable cluster properties.

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 apply the cherry-pick from GitHub PR #7891 to implement proper authorization checks on cluster management operations.

Recommended fix High confidence

1.7.0

  1. Plan for downtime and backup your InLong data and configuration
  2. Stop all InLong services
  3. Upgrade InLong to version 1.7.0 following the standard upgrade process
  4. Start InLong services and verify cluster functionality
  5. Confirm the vulnerability is resolved by verifying that non-admin users cannot modify cluster name and type

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

Fix this in Inlong Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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