org.apache.inlong:manager-web vulnerabilities
- Registry
- Maven
- Latest
- 2.4.0
7 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-web -DdepVersion=2.4.0 -DforceVersion=trueIs your project on an affected org.apache.inlong:manager-web?
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-web
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 Files or Directories Accessible to External Parties in Apache InLong
- 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 Incorrect Permission Assignment for Critical Resource Vulnerability
- Affected
- >=1.2.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
User data exposure in Apache InLong
- Affected
- >=1.5.0 <1.7.0
- Fixed in
- 1.7.0
Is your org.apache.inlong:manager-web version vulnerable?
- org.apache.inlong:manager-web 2.4No known advisories in 2.4.0
- org.apache.inlong:manager-web 2.3No known advisories in 2.3.0
- org.apache.inlong:manager-web 2.2No known advisories in 2.2.0
- org.apache.inlong:manager-web 2.1No known advisories in 2.1.0
- org.apache.inlong:manager-web 2.0No known advisories in 2.0.0
- org.apache.inlong:manager-web 1.13No known advisories in 1.13.0
- org.apache.inlong:manager-web 1.12No known advisories in 1.12.0
- org.apache.inlong:manager-web 1.11No known advisories in 1.11.0
- org.apache.inlong:manager-web 1.10No known advisories in 1.10.0
- org.apache.inlong:manager-web 1.9No known advisories in 1.9.0
- org.apache.inlong:manager-web 1.8No known advisories in 1.8.0
Which of your client projects still run an old org.apache.inlong:manager-web?
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.