Log forgery via unencoded Manager messages
Published Oct 16, 2023 · Updated Jun 16, 2025
Log injection in Apache InLong Manager 1.4.0 through 1.8.0 allows remote attackers to forge log records through crafted requests. The Manager's Log4j2 pattern writes message text without CRLF encoding, while data-node and cluster testConnection controllers accepted request bodies without validation. Network access to either endpoint is sufficient, and forged entries can obscure auditing and malicious-activity tracing.
Summary
What happened
Log injection in Apache InLong Manager 1.4.0 through 1.8.0 allows remote attackers to forge log records through crafted requests. The Manager's Log4j2 pattern writes message text without CRLF encoding, while data-node and cluster testConnection controllers accepted request bodies without validation. Network access to either endpoint is sufficient, and forged entries can obscure auditing and malicious-activity tracing.
The record
- CVE
- CVE-2023-43667
- Published
- Oct 16, 2023
- Updated
- Jun 16, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache InLong
- Classifications
- CWE-74, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2023CVE publishedPublication date reported by the CVE source.
- Jun 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.4.0 <=1.8.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo