dbcve.org
InlongApplication · Apache

CVE-2023-31101

MEDIUM · 6.5 CVSS v3.1 Published 2023-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Insecure Default Initialization of Resource Vulnerability in Apache Software Foundation Apache InLong.This issue affects Apache InLong: from 1.5.0 through 1.6.0. Users registered in InLong who joined later can see deleted users' data. Users are advised to upgrade to Apache InLong's 1.7.0 or cherry-pick https://github.com/apache/inlong/pull/7836 https://github.com/apache/inlong/pull/7836 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 insecure default initialization vulnerability in Apache InLong (versions 1.5.0-1.6.0) where improper resource initialization allows newly registered users to access data belonging to deleted users. The vulnerability stems from inadequate isolation between user accounts during the user registration and data lifecycle management processes.

MitigationUpgrade to Apache InLong 1.7.0 or apply the cherry-pick from GitHub PR #7836 to fix the improper resource initialization that causes data exposure of deleted users to new users.

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.5.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Identify installed Apache InLong version
    Check the InLong version file or API endpoint that reports the product version, such as checking the build artifacts, configuration files, or the /api/inlong/manager/api/version endpoint if available
    Affected if The installed version is 1.5.0 or 1.6.0, as these are the affected versions listed in the CVE
  2. Verify if user registration functionality exists
    Check if the user registration endpoint or interface is accessible and functional in the InLong deployment
    Affected if User registration is enabled and operational, allowing new users to be created in the system
  3. Check for presence of deleted user data
    Review system logs, audit records, or database entries for evidence of previously deleted users who may have left behind data resources (such as streams, groups, or pipelines)
    Affected if There are records of deleted users whose data resources still exist in the system after deletion
  4. Test user data isolation
    Register a new test user and attempt to access resources that belonged to a deleted user, if such deleted user data exists in the system
    Affected if The new user can access, list, or modify data resources that were created by or assigned to a previously deleted user, indicating improper isolation

You are affected if you are running Apache InLong version 1.5.0 or 1.6.0 and your system has deleted users whose data resources may be accessible to newly registered users due to improper resource initialization.

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.7.0 or apply the cherry-pick from GitHub PR #7836 to fix the improper resource initialization that causes data exposure of deleted users to new users.

Recommended fix High confidence

1.7.0

  1. Back up your current InLong installation and database before starting the upgrade process
  2. Stop all running InLong services to prevent data inconsistency during upgrade
  3. Upgrade Apache InLong to version 1.7.0 by following the official upgrade documentation for your deployment method
  4. Start the InLong services after the upgrade is complete
  5. Verify that the upgrade was successful by logging in and confirming that new users can no longer see deleted users' data

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

Fix this in Inlong Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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