dbcve.org
InlongApplication · Apache

CVE-2023-24997

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to after 1.5.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
Deserialization of Untrusted Data vulnerability in Apache Software Foundation Apache InLong.This issue affects Apache InLong: from 1.1.0 through 1.5.0. Users are advised to upgrade to Apache InLong's latest version or cherry-pick https://github.com/apache/inlong/pull/7223 https://github.com/apache/inlong/pull/7223  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

Deserialization of Untrusted Data vulnerability in Apache InLong (versions 1.1.0-1.5.0) allows attackers to potentially execute arbitrary code via malicious serialized data processed by the application. This is a critical severity flaw (CVSS 9.8) that could lead to complete system compromise if exploited.

MitigationUpgrade Apache InLong to the latest version or cherry-pick PR #7223 to address the insecure deserialization vulnerability. Prioritize patching for any internet-facing InLong instances.

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.1.0, <= 1.5.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Apache InLong is installed
    Search for InLong installation directories, running processes, or services. Common paths include /opt/inlong, /usr/local/inlong, or check for 'inlong' processes via 'ps aux | grep inlong' or service listings.
    Affected if Apache InLong is present on the system
  2. Determine the installed InLong version
    Locate version information in the installation directory. Check for VERSION files, pom.xml build files, startup scripts, or query the InLong admin API if accessible. The version is often displayed in log files at startup.
    Affected if The installed version is >= 1.1.0 and <= 1.5.0
  3. Verify if API or data ingestion endpoints are accessible
    Review network configurations and firewall rules to determine if InLong API servers, data ingestion ports, or admin interfaces are exposed to the network. Check for open ports commonly used by InLong.
    Affected if InLong services are network-accessible from untrusted sources

If Apache InLong version 1.1.0 through 1.5.0 is installed and its services are network-accessible, the environment is affected by this deserialization vulnerability.

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.5.0
Interim mitigation

Upgrade Apache InLong to the latest version or cherry-pick PR #7223 to address the insecure deserialization vulnerability. Prioritize patching for any internet-facing InLong instances.

Recommended fix Moderate confidence

latest version (1.6.0 or later)

  1. 1. Identify your current Apache InLong version by checking the application or documentation
  2. 2. Upgrade to the latest version of Apache InLong (version 1.6.0 or later) which contains the fix for this vulnerability
  3. 3. Alternatively, cherry-pick commit/PR #7223 (https://github.com/apache/inlong/pull/7223) if upgrading is not immediately feasible
  4. 4. After applying the fix, restart all InLong services to ensure the patch takes effect
  5. 5. Verify the vulnerability is resolved by testing deserialization processes and confirming the patch is active

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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