dbcve.org
InlongApplication · Apache

CVE-2023-31065

CRITICAL · 9.1 CVSS v3.1 Published 2023-05-22
Fix available
A fix is available. Upgrade to after 1.6.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
Insufficient Session Expiration vulnerability in Apache Software Foundation Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.6.0.  An old session can be used by an attacker even after the user has been deleted or the password has been changed. 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 , https://github.com/apache/inlong/pull/7884 https://github.com/apache/inlong/pull/7884 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

Insufficient Session Expiration vulnerability in Apache InLong allows old sessions to remain valid even after user deletion or password change, enabling continued unauthorized access by attackers with compromised or stale session tokens.

MitigationUpgrade to Apache InLong 1.7.0 or cherry-pick the fixes from GitHub PRs #7836 and #7884 to implement proper session invalidation upon user deletion and password changes.

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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Apache InLong installed version
    Locate the InLong installation directory and check the version file or pom.xml, typically found in the root installation path or build configuration. Common locations include version.txt, pom.xml in the source, or check the WAR/JAR file manifests.
    Affected if The installed version is between 1.4.0 and 1.6.0 inclusive.
  2. Examine session storage for deleted users
    Query the session or token storage mechanism (typically a database table such as session_info, user_token, or similar) to list active sessions. Cross-reference the user IDs in active sessions against the current user directory or database to identify any sessions belonging to users who have been deleted.
    Affected if Active sessions exist for users that have been deleted from the user database.
  3. Verify session invalidation after password changes
    Identify a test user, record the timestamp of their last password change, then check the session storage to determine if any sessions created before that timestamp remain active for that user.
    Affected if Sessions created before a password change remain valid and active.
  4. Review session expiration configuration
    Check the InLong configuration files (typically in conf/ or config/ directories) for session.timeout, session.max.age, or token.expiry settings to understand the expected session lifecycle.
    Affected if Session timeout is configured to a very long duration or is unset, allowing stale sessions to persist indefinitely.

You are affected if Apache InLong version 1.4.0 through 1.6.0 is running and active sessions exist for deleted users or persist after password changes.

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 fixes from GitHub PRs #7836 and #7884 to implement proper session invalidation upon user deletion and password changes.

Recommended fix High confidence

1.7.0

  1. Backup your current Apache InLong data and configuration before upgrading.
  2. Stop the InLong services running version 1.4.0 through 1.6.0.
  3. Upgrade Apache InLong to version 1.7.0 following the official upgrade documentation.
  4. Start the InLong 1.7.0 services.
  5. Verify that sessions are properly invalidated when users are deleted or passwords are changed.

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

Fix this in Inlong Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA1.0 h
12.0 hours of engineering $2,110
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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