dbcve.org
InlongApplication · Apache

CVE-2023-43667

HIGH · 7.5 CVSS v3.1 Published 2023-10-16
Fix available
A fix is available. Upgrade to after 1.8.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
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.8.0, the attacker can create misleading or false log records, making it harder to audit and trace malicious activities. Users are advised to upgrade to Apache InLong's 1.9.0 or cherry-pick [1] to solve it. [1] https://github.com/apache/inlong/pull/8628

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

Log injection vulnerability in Apache InLong allows attackers to inject special characters (likely newlines or log formatting sequences) into log output, enabling creation of false or misleading log records that compromise audit trails and forensic analysis. This is an output injection flaw affecting the logging subsystem in versions 1.4.0 through 1.8.0.

MitigationUpgrade to Apache InLong 1.9.0 or apply the cherry-pick from GitHub PR #8628 which implements proper sanitization of special characters in log output to prevent injection.

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.4.0, <= 1.8.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache InLong installation
    Locate the InLong installation directory - common paths include /opt/inlong, /usr/local/inlong, or the deployed application directory. Look for the inlong-dist directory or inlong-manager webapp JAR files.
    Affected if Apache InLong is found installed on the system
  2. Determine installed InLong version
    Check for version files in the installation directory, such as VERSION files, or inspect the manifest files (MANIFEST.MF) within the deployed JAR/WAR files. The version may also be visible in the InLong dashboard or admin interface.
    Affected if The version is 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, or falls within this range (>=1.4.0 and <=1.8.0)
  3. Confirm logging subsystem is active
    Check if InLong services are running and producing logs. Verify the presence of log directories such as logs/ or log/ within the InLong installation, and confirm log files are being written (e.g., manager.log, audit.log, dataproxy.log).
    Affected if The logging subsystem is active and writing log output to files or console
  4. Verify log injection exposure
    Review the log configuration files (log4j.properties, logback.xml, or similar) in the InLong deployment to confirm logging outputs to files or systems that could accept injected content. Also check if audit logging is enabled, as this vulnerability specifically compromises audit trails.
    Affected if Logs or audit logs are written to file-based or external logging systems where injected entries would be stored and could mislead investigators

The environment is affected if Apache InLong version 1.4.0 through 1.8.0 is installed and the logging subsystem is actively writing logs, as the log injection flaw allows attackers to forge false log records.

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.8.0
Interim mitigation

Upgrade to Apache InLong 1.9.0 or apply the cherry-pick from GitHub PR #8628 which implements proper sanitization of special characters in log output to prevent injection.

Recommended fix High confidence

1.9.0

  1. 1. Back up your current InLong installation and database
  2. 2. Review the InLong 1.9.0 release notes and migration guide for any required configuration changes
  3. 3. Stop the running InLong 1.4.0-1.8.0 services
  4. 4. Upgrade to InLong version 1.9.0 following the standard upgrade procedure in the documentation
  5. 5. Verify that the Log4j2 log pattern layout has been updated to properly escape newline characters in log messages
  6. 6. Restart all InLong services
  7. 7. Test that log records are properly formatted and injection attempts result in escaped/newline-terminated entries rather than forged log lines

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

Fix this in Inlong Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
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,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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