cve.bz

CVE-2023-31065 apache inlong: Insufficient Session Expiration

9.1 criticalEPSS 1.2%Fix available

Critical (9.1) in apache inlong. EPSS 1.2% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.inlong:manager-pojo 1.7.0.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
1.2% (unchanged from 1.2% a week ago; 1.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 68th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2024-10-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-613 Insufficient Session Expiration deprecated by MITRE see CWE-1463, CWE-1464
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-31065 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-31065?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-31065?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-31065 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache InLongfrom 1.4.0 through 1.6.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-757p-7hp5-pqmrMavenorg.apache.inlong:manager-pojo>=1.4.0 <1.7.01.7.0
GHSA-757p-7hp5-pqmrMavenorg.apache.inlong:manager-dao>=1.4.0 <1.7.01.7.0
GHSA-757p-7hp5-pqmrMavenorg.apache.inlong:manager-web>=1.4.0 <1.7.01.7.0
GHSA-757p-7hp5-pqmrMavenorg.apache.inlong:manager-service>=1.4.0 <1.7.01.7.0

References

Check your stackJSON