InlongApplication · Apache
CVE-2023-31062
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 · uneditedImproper Privilege Management Vulnerabilities in Apache Software Foundation Apache InLong.This issue affects Apache InLong: from 1.2.0 through 1.6.0. When the attacker has access to a valid (but unprivileged) account, the exploit can be executed using Burp Suite by sending a login request and following it with a subsequent HTTP request using the returned cookie. 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 confidenceImproper privilege management in Apache InLong allows authenticated but unprivileged users to escalate privileges by reusing their session cookie for subsequent HTTP requests. The authentication mechanism returns a cookie that can be used to perform actions beyond the user's authorized permissions.
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
>= 1.2.0, <= 1.6.0CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache InLong installation and versionLocate the InLong installation directory and check the version file or build metadata. Common locations include /opt/inlong or the directory where the application was deployed. Look for version indicators in release notes, pom.xml, or version configuration files.Affected if The installed version is between 1.2.0 and 1.6.0 inclusive
-
Verify the version against affected rangeCompare your identified InLong version number to the affected range: versions 1.2.0 through 1.6.0 are vulnerable.Affected if The version falls within >= 1.2.0 and <= 1.6.0
-
Confirm authentication is enabledCheck the InLong configuration files (such as application.yml or inlong.conf) for authentication settings. Look for whether user authentication is configured and active.Affected if Authentication is enabled and users can log in to the system
-
Check for session handling configurationInspect the session management or security configuration in InLong to verify how session cookies are handled after authentication. Look for cookie-based authentication settings.Affected if Session cookies are used for authentication without proper post-authentication authorization checks
A user is affected if they are running Apache InLong version 1.2.0 through 1.6.0 with authentication enabled, where session cookies can be reused to perform actions beyond the user's authorized permissions.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Apache InLong to version 1.7.0 or cherry-pick the fix from GitHub PR #7836 to properly enforce authorization checks after authentication.
1.7.0
- 1. Back up your current Apache InLong configuration and data
- 2. Stop the running InLong 1.2.0-1.6.0 instance
- 3. Upgrade Apache InLong to version 1.7.0 or later by following the official upgrade documentation at https://inlong.apache.org/docs/next/quick_start/how-to-run
- 4. Restart the InLong service with the new version
- 5. Verify the upgrade by logging in and testing that unprivileged users cannot escalate privileges
- 6. Confirm all components are functioning correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Inlong
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-31062 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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