org.apache.inlong:manager-pojo vulnerabilities
- Registry
- Maven
- Latest
- 2.4.0
17 known advisories
The latest version, 2.4.0, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.apache.inlong:manager-pojo -DdepVersion=2.4.0 -DforceVersion=trueIs your project on an affected org.apache.inlong:manager-pojo?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.apache.inlong:manager-pojo
Apache InLong: JDBC Vulnerability For URLEncode and backspace bypass
- Affected
- >=1.13.0 <2.2.0
- Fixed in
- 2.2.0
Apache InLong: JDBC Vulnerability for Invisible Character Bypass Leading to Arbitrary File Read
- Affected
- >=1.13.0 <2.2.0
- Fixed in
- 2.2.0
Apache InLong: JDBC Vulnerability during verification processing
- Affected
- >=1.13.0 <2.2.0
- Fixed in
- 2.2.0
Apache Inlong Deserialization of Untrusted Data vulnerability
- Affected
- >=1.7.0 <1.12.0
- Fixed in
- 1.12.0
Apache InLong Manager Remote Code Execution vulnerability
- Affected
- >=1.5.0 <1.10.0
- Fixed in
- 1.10.0
Apache InLong Manager Arbitrary File Read Vulnerability
- Affected
- >=1.5.0 <1.10.0
- Fixed in
- 1.10.0
Apache InLong Deserialization of Untrusted Data Vulnerability
- Affected
- >=1.4.0 <1.9.0
- Fixed in
- 1.9.0
Authorization Bypass in Apache InLong
- Affected
- >=1.4.0 <1.9.0
- Fixed in
- 1.9.0
JDBC URL bypassing by allowLoadLocalInfileInPath param
- Affected
- >=1.4.0 <1.8.0
- Fixed in
- 1.8.0
Apache InLong Insufficient Session Expiration vulnerability
- Affected
- >=1.4.0 <1.7.0
- Fixed in
- 1.7.0
Apache InLong Improper Privilege Management vulnerability
- Affected
- >=1.2.0 <1.7.0
- Fixed in
- 1.7.0
Apache InLong has Weak Password Requirements in Apache InLong
- Affected
- >=1.1.0 <1.47.0
- Fixed in
- 1.47.0
Apache InLong Exposure of Resource to Wrong Sphere vulnerability
- Affected
- >=1.4.0 <1.7.0
- Fixed in
- 1.7.0
Apache InLong Deserialization of Untrusted Data Vulnerability
- Affected
- >=1.4.0 <1.7.0
- Fixed in
- 1.7.0
Apache InLong Exposure of Resource to Wrong Sphere vulnerability
- Affected
- >=1.4.0 <1.7.0
- Fixed in
- 1.7.0
Apache InLong SQL Injection vulnerability
- Affected
- >=1.4.0 <1.6.0
- Fixed in
- 1.6.0
User data exposure in Apache InLong
- Affected
- >=1.5.0 <1.7.0
- Fixed in
- 1.7.0
Is your org.apache.inlong:manager-pojo version vulnerable?
- org.apache.inlong:manager-pojo 2.4No known advisories in 2.4.0
- org.apache.inlong:manager-pojo 2.3No known advisories in 2.3.0
- org.apache.inlong:manager-pojo 2.2No known advisories in 2.2.0
- org.apache.inlong:manager-pojo 2.13 advisories in 2.1.0
- org.apache.inlong:manager-pojo 2.03 advisories in 2.0.0
- org.apache.inlong:manager-pojo 1.134 advisories in 1.13.0
- org.apache.inlong:manager-pojo 1.121 advisory in 1.12.0
- org.apache.inlong:manager-pojo 1.112 advisories in 1.11.0
- org.apache.inlong:manager-pojo 1.102 advisories in 1.10.0
- org.apache.inlong:manager-pojo 1.94 advisories in 1.9.0
- org.apache.inlong:manager-pojo 1.86 advisories in 1.8.0
Which of your client projects still run an old org.apache.inlong:manager-pojo?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.