Authenticated JNDI injection via unfiltered DB2 parameters
Published Jul 15, 2024 · Updated Mar 27, 2025
JNDI injection in Apache Linkis DataSource before 1.6.0 allows remote authenticated users to trigger JNDI lookups through DB2 parameters. The DataSource Manager places user-controlled DB2 properties into a JDBC URL without rejecting dangerous JNDI parameters. Exploitation requires an authorized Linkis account; the advisory does not disclose the post-lookup payload or a more specific consequence.
Summary
What happened
JNDI injection in Apache Linkis DataSource before 1.6.0 allows remote authenticated users to trigger JNDI lookups through DB2 parameters. The DataSource Manager places user-controlled DB2 properties into a JDBC URL without rejecting dangerous JNDI parameters. Exploitation requires an authorized Linkis account; the advisory does not disclose the post-lookup payload or a more specific consequence.
The record
- CVE
- CVE-2023-49566
- Published
- Jul 15, 2024
- Updated
- Mar 27, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Linkis DataSource
- Classifications
- CWE-502
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 15, 2024CVE publishedPublication date reported by the CVE source.
- Mar 27, 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.6.0
What conditions does exploitation require?
What is affected?
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