JDBC parameter-filter bypass via nested URL encoding
Published Feb 1, 2023 · Updated Mar 26, 2025
Insufficient URL decoding in Apache InLong 1.1.0 through 1.5.0 allows remote attackers to bypass MySQL JDBC parameter filtering. MySQLSinkDTO.filterSensitive decodes a submitted JDBC URL only once before checking sensitive parameter names, so nested percent-encoding hides them from the filter. The crafted URL must reach the InLong Manager MySQL sink path; published vendor material does not identify a narrower resulting attacker action.
Summary
What happened
Insufficient URL decoding in Apache InLong 1.1.0 through 1.5.0 allows remote attackers to bypass MySQL JDBC parameter filtering. MySQLSinkDTO.filterSensitive decodes a submitted JDBC URL only once before checking sensitive parameter names, so nested percent-encoding hides them from the filter. The crafted URL must reach the InLong Manager MySQL sink path; published vendor material does not identify a narrower resulting attacker action.
The record
- CVE
- CVE-2023-24997
- Published
- Feb 1, 2023
- Updated
- Mar 26, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache InLong
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 1, 2023CVE publishedPublication date reported by the CVE source.
- Mar 26, 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.1.0 <=1.5.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