InlongApplication · Apache
CVE-2023-51784
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 Control of Generation of Code ('Code Injection') vulnerability in Apache InLong.This issue affects Apache InLong: from 1.5.0 through 1.9.0, which could lead to Remote Code Execution. Users are advised to upgrade to Apache InLong's 1.10.0 or cherry-pick [1] to solve it. [1] https://github.com/apache/inlong/pull/9329
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 confidenceApache InLong versions 1.5.0 through 1.9.0 contain a code injection vulnerability allowing remote code execution. The vulnerability stems from improper control of code generation, likely due to unsafe evaluation of user-supplied input. Attackers can exploit this to execute arbitrary commands on the affected system.
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.5.0, < 1.10.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.
-
Check if Apache InLong is installedLook for InLong installation directories (common paths: /opt/inlong, /usr/local/inlong, ~/inlong) or check for running InLong processes using 'ps aux | grep inlong' or 'jps -l' for Java processesAffected if Apache InLong process or installation directory is found on the system
-
Determine installed InLong versionCheck the version file in the InLong installation directory, typically found as 'VERSION' or 'inlong-version' file in the root installation folder, or run 'grep -r version [install_dir]' to locate version metadataAffected if Version file shows a version >= 1.5.0 and < 1.10.0
-
Check InLong manager service version via APIIf the InLong manager service is accessible, query the health endpoint or version endpoint (typically at /api/inlong/manager/api/version or /actuator/info) using curl or similar toolAffected if API response indicates version within the 1.5.0 to 1.9.0 range
-
Identify exposed InLong componentsReview network listeners and configuration for InLong components: manager, dataproxy, audit, and agent services. Check configuration files (manager.conf, dataproxy.conf) for binding addresses and portsAffected if InLong services are exposed on network interfaces accessible to untrusted users
-
Verify Java process command lineUse 'ps auxww' to inspect the full command line of running InLong Java processes, noting the JAR files or classpath indicating the InLong versionAffected if Java process shows InLong JARs or classes with version indicators in the 1.5.0-1.9.0 range
A user is affected if Apache InLong is installed and the version falls within 1.5.0 to 1.9.0, particularly if the manager service is network-accessible.
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 · scoped1.10.0
Upgrade Apache InLong to version 1.10.0 or apply the cherry-pick from PR #9329. Prioritize this critical fix given the CVSS 9.8 score and RCE capability.
1.10.0
- Upgrade Apache InLong to version 1.10.0 or later to remediate the code injection vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Inlong
Scoped from the published advisory
- Consultation6.0 h
- Implementation4.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,104.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51784 — 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-51784 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