dbcve.org
InlongApplication · Apache

CVE-2023-24977

HIGH · 7.5 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to after 1.5.0 or later.
See remediation →
84/100
Remediation priority · High
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
Out-of-bounds Read 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/7214 https://github.com/apache/inlong/pull/7214  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

Out-of-bounds read vulnerability in Apache InLong versions 1.1.0 through 1.5.0. This memory safety issue allows reading data beyond allocated buffer boundaries, potentially leading to information disclosure or denial of service. The vulnerability is addressed via upgrade or cherry-pick of PR #7214.

MitigationUpgrade Apache InLong to the latest version or apply the cherry-pick from PR #7214 to resolve the out-of-bounds read vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Apache InLong installation version
    Locate the InLong version information from your installation. Common methods include: checking the about/version page in the InLong admin console, running 'grep -r "inlong.version"' or 'grep -r "version"' in the installation directory, checking the MANIFEST.MF file in the InLong jars, or reviewing your deployment configuration files that specify the version.
    Affected if The installed version is 1.1.0, 1.2.0, 1.3.0, 1.4.0, or 1.5.0 (any version from 1.1.0 through 1.5.0 inclusive).
  2. Confirm InLong service is running
    Verify that the Apache InLong service is actively running in your environment. Check running processes for InLong Java processes, or check if the InLong web portal or API endpoints are responding.
    Affected if InLong is running and the version falls within the affected range (1.1.0 to 1.5.0).
  3. Review application logs for crash or stability issues
    Examine InLong server logs for any out-of-bounds read errors, memory access violations, or unexpected crashes that may indicate exploitation of this vulnerability. Look for relevant exception patterns in log files.
    Affected if You observe memory safety errors, segmentation faults, or unexpected service instability in logs from an affected version.

You are affected if Apache InLong version 1.1.0 through 1.5.0 is installed and running in your environment.

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 apply the cherry-pick from PR #7214 to resolve the out-of-bounds read vulnerability.

Recommended fix High confidence

Apache InLong 1.6.0 or later (latest stable release)

  1. 1. Backup your current Apache InLong installation, database, and configuration files
  2. 2. Stop all InLong services to prevent data inconsistency during upgrade
  3. 3. Download Apache InLong version 1.6.0 or later from the official Apache InLong release page at https://inlong.apache.org/download/ or https://archive.apache.org/dist/inlong/
  4. 4. Upgrade the InLong backend database by running the migration scripts provided in the release (typically in the docker directory or sql directory)
  5. 5. Deploy the new InLong 1.6.0+ binaries or container images
  6. 6. Start InLong services and verify all components are running
  7. 7. Test core functionality (data ingestion, workflow, API endpoints) to confirm the upgrade was successful
  8. 8. Optionally, verify the fix is applied by confirming PR #7214 changes are present in the codebase
Caveat Review release notes for any configuration or API changes between 1.5.0 and 1.6.0; some deprecated features may require configuration updates

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

Fix this in Inlong Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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