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.

Update to the latest version:mvn versions:use-dep-version -Dincludes=org.apache.inlong:manager-web -DdepVersion=2.4.0 -DforceVersion=true

Is your project on an affected org.apache.inlong:manager-web?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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

  • CriticalCVE-2023-31065GHSA-757p-7hp5-pqmr6 Jul 2023

    Apache InLong Insufficient Session Expiration vulnerability

    Affected
    >=1.4.0 <1.7.0
    Fixed in
    1.7.0
  • CriticalCVE-2023-31062GHSA-q5p5-xg93-2jqc6 Jul 2023

    Apache InLong Improper Privilege Management vulnerability

    Affected
    >=1.2.0 <1.7.0
    Fixed in
    1.7.0
  • CriticalCVE-2023-31066GHSA-wx79-r3q8-fq9h6 Jul 2023

    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
  • HighCVE-2023-31103GHSA-7mhc-76hf-3jp96 Jul 2023

    Apache InLong Exposure of Resource to Wrong Sphere vulnerability

    Affected
    >=1.4.0 <1.7.0
    Fixed in
    1.7.0
  • HighCVE-2023-31453GHSA-8rjh-3mhm-966q6 Jul 2023

    Apache InLong Incorrect Permission Assignment for Critical Resource Vulnerability

    Affected
    >=1.2.0 <1.7.0
    Fixed in
    1.7.0
  • HighCVE-2023-31206GHSA-f475-jgg3-3jwc6 Jul 2023

    Apache InLong Exposure of Resource to Wrong Sphere vulnerability

    Affected
    >=1.4.0 <1.7.0
    Fixed in
    1.7.0
  • MediumCVE-2023-31101GHSA-h79m-5cm2-278c22 May 2023

    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?

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.