Apache Linkis vulnerable to Exposure of Sensitive Information
Published 31 Jan 2023 · Updated 8 Nov 2023
Is your project on an affected org.apache.linkis:linkis?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <1.3.1
- Fixed in
- 1.3.1
mvn versions:use-dep-version -Dincludes=org.apache.linkis:linkis -DdepVersion=1.3.1 -DforceVersion=trueDetails
In Apache Linkis <=1.3.0 when used with the MySQL Connector/J, an authenticated attacker could read arbitrary local file by connecting a rogue mysql server, By adding allowLoadLocalInfile to true in the jdbc parameter. Therefore, the parameters in the jdbc url should be blacklisted. Versions of Apache Linkis <= 1.3.0 will be affected. We recommend users upgrade the version of Linkis to version 1.3.1
Is GHSA-rx76-xw35-6rh8 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.linkis:linkis, and gives you the command that fixes it.
More advisories for org.apache.linkis:linkis
- HighCVE-2025-29847Apache Linkis: Arbitrary File Read via Double URL Encoding Bypass · 19 Jan 2026
- HighCVE-2024-27182Apache Linkis arbitrary file deletion vulnerability · 2 Aug 2024
- HighCVE-2024-27181Apache Linkis vulnerable to privilege escalation · 2 Aug 2024
- MediumCVE-2023-50740Apache Linkis DataSource: DataSource module Oracle SQL Database Password Logged · 6 Mar 2024
- CriticalCVE-2023-27987Apache Linkis Authentication Bypass vulnerability · 6 Jul 2023
- CriticalCVE-2023-27603Apache Linkis Zip Slip issue · 6 Jul 2023
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.