InlongApplication · Apache
CVE-2023-31058
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 Software Foundation Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.6.0. Attackers would bypass the 'autoDeserialize' option filtering by adding blanks. Users are advised to upgrade to Apache InLong's 1.7.0 or cherry-pick https://github.com/apache/inlong/pull/7674 https://github.com/apache/inlong/pull/7674 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 confidenceApache InLong versions 1.4.0-1.6.0 contain a deserialization vulnerability where attackers can bypass the autoDeserialize option filtering by inserting blank characters, allowing deserialization of untrusted data.
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.4.0, <= 1.6.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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 versionCheck the version file or startup logs. Common locations include the VERSION file in the installation root, the manager or agent service logs on startup, or the pom.xml if examining source code. Run: grep -r 'inlong.version' or check bin/init.sh for version info.Affected if The installed version falls within >= 1.4.0 and <= 1.6.0
-
Locate autoDeserialize configurationSearch for autoDeserialize settings in configuration files. Check inlong.conf, application.yml, or similar configuration files in the conf/ directory. Look for patterns: 'autoDeserialize', 'deserialization', or 'deserialize' settings.Affected if autoDeserialize is explicitly enabled or configured in any InLong component config
-
Identify deserialization endpointsReview API endpoints or data ingestion paths that accept serialized data. Check controller or listener classes that handle inbound data streams, particularly those processing JSON, XML, or Java object streams.Affected if The system exposes endpoints that accept and deserialize untrusted data without additional validation layers
-
Check for blank character filteringInspect the serialization/deserialization filter implementation. Look for validation logic that handles blank characters (spaces, tabs, newlines) in input data before deserialization occurs.Affected if No explicit filtering or validation of blank characters exists in the deserialization path
You are affected if Apache InLong version is between 1.4.0 and 1.6.0 inclusive AND the autoDeserialize feature is enabled or the system processes untrusted serialized data through InLong components.
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 to Apache InLong 1.7.0 or apply the cherry-pick from PR #7674 to address the autoDeserialize filtering bypass.
Apache InLong 1.7.0 or later
- 1. Backup the current InLong installation, configuration files, and database data before proceeding with the upgrade.
- 2. Stop all InLong services to prevent data inconsistency during the upgrade process.
- 3. Download Apache InLong version 1.7.0 or later from the official Apache InLong releases page (https://inlong.apache.org/download/).
- 4. Upgrade the InLong installation to version 1.7.0 by following the official upgrade guide at https://inlong.apache.org/docs/next/quick_start/upgrade/
- 5. After upgrade, verify that the autoDeserialize filtering now properly blocks attempts that use blank characters to bypass validation.
- 6. Test that InLong functionality remains operational after the upgrade.
- 7. Monitor logs for any deserialization-related errors or attempts to exploit this vulnerability.
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
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31058 — 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-31058 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