InlongApplication · Apache
CVE-2023-51785
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 · uneditedDeserialization of Untrusted Data vulnerability in Apache InLong.This issue affects Apache InLong: from 1.7.0 through 1.9.0, the attackers can make a arbitrary file read attack using mysql driver. 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/9331
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 confidenceThis is a deserialization vulnerability in Apache InLong where attackers can exploit the MySQL JDBC driver to perform arbitrary file reads on the system. The vulnerability exists in versions 1.7.0 through 1.9.0 and stems from unsafe deserialization of data passed through the MySQL connector.
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.7.0, <= 1.9.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache InLong versionLocate the InLong installation directory and check the version file or WAR/WEB-INF/lib jar manifest. Typical locations include the release artifacts, docker container labels, or the manage.py/VERSION file in the installation root.Affected if The installed version is between 1.7.0 and 1.9.0 inclusive.
-
Confirm MySQL connector is in useInspect the classpath or lib directory for mysql-connector-java.jar or mysql-connector-j.jar. Also check configuration files for MySQL datasource definitions.Affected if A MySQL JDBC driver is present in the InLong classpath.
-
Check for MySQL datasource configurationReview InLong configuration files (typically in conf/ or config/ directories) for MySQL connection settings, particularly those using the MySQL JDBC connector for data ingestion or storage.Affected if MySQL datasources are configured and actively used by InLong.
-
Inspect deserialization settingsCheck whether the MySQL JDBC connection parameters allow for arbitrary data deserialization, particularly in contexts where untrusted data may be processed through the connector.Affected if MySQL connector receives deserialized data from external or untrusted sources.
You are affected if Apache InLong version 1.7.0 through 1.9.0 is installed with a MySQL JDBC connector actively processing data that can be deserialized.
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.10.0 or cherry-pick the fix from GitHub PR #9331 to address the unsafe MySQL driver deserialization.
1.10.0
- Upgrade Apache InLong to version 1.10.0 or later
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
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 locallyCheck whether your project pulls in CVE-2023-51785 — 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-51785 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