dbcve.org
InlongApplication · Apache

CVE-2024-36268

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-02
Fix available
A fix is available. Upgrade to 1.13.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
Improper Control of Generation of Code ('Code Injection') vulnerability in Apache InLong. This issue affects Apache InLong: from 1.10.0 through 1.12.0, which could lead to Remote Code Execution. Users are advised to upgrade to Apache InLong's 1.13.0 or cherry-pick [1] to solve it. [1]  https://github.com/apache/inlong/pull/10251

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

Apache InLong versions 1.10.0 through 1.12.0 contain a code injection vulnerability that allows attackers to inject malicious code through improper control of code generation, leading to remote code execution (RCE) on the affected system.

MitigationUpgrade Apache InLong to version 1.13.0 or apply the cherry-pick from GitHub PR #10251 to remediate the code injection 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.10.0, < 1.13.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 installed Apache InLong version
    Check the version file or startup scripts in the InLong installation directory. Common locations include: version files in the root directory, docker image tags, or the InLong dashboard under 'System' > 'About' information.
    Affected if The version is 1.10.0, 1.10.1, 1.11.0, 1.11.1, 1.12.0, or any version >= 1.10.0 and < 1.13.0
  2. Check InLong Manager service version
    Query the InLong Manager REST API endpoint /api/inlong/manager/version or check the manager service logs for version information at startup.
    Affected if The manager service reports a version within the affected range 1.10.0 to < 1.13.0
  3. Verify InLong API endpoints availability
    Confirm the InLong API server is accessible and running. The vulnerability affects code generation functionality exposed through API endpoints.
    Affected if The API server is running and responds to requests, indicating the vulnerable code generation component is active
  4. Review code generation feature configuration
    Inspect InLong configuration files (inlong_manager.conf, common.properties) for code generation or dynamic class compilation settings. Look for properties related to script execution, template rendering, or dynamic code compilation.
    Affected if Code generation or dynamic compilation features are enabled in the configuration
  5. Check for unauthorized code execution indicators
    Review InLong service logs for suspicious code execution patterns, unexpected script invocations, or indicators of code injection attempts targeting code generation endpoints.
    Affected if Logs show unusual code generation requests, unexpected compilation activities, or evidence of injection attempts

The environment is affected if the installed Apache InLong version is >= 1.10.0 and < 1.13.0, with the vulnerable code generation component accessible and enabled.

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 1.13.0 or later
Fixed in 1.13.0
Interim mitigation

Upgrade Apache InLong to version 1.13.0 or apply the cherry-pick from GitHub PR #10251 to remediate the code injection vulnerability.

Recommended fix High confidence

1.13.0

  1. 1. Backup your current Apache InLong installation, configuration files, and database
  2. 2. Stop all running InLong services
  3. 3. Download Apache InLong version 1.13.0 from the official Apache repository
  4. 4. Upgrade InLong to version 1.13.0 following the upgrade documentation
  5. 5. Verify the upgrade by checking the version number in the system
  6. 6. Start InLong services and confirm they initialize correctly
  7. 7. Verify that workflows and data pipelines are functioning as expected
Caveat Review the 1.13.0 release notes for any configuration changes, API updates, or database schema modifications that may affect your deployment

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

Fix this in Inlong Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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