Skip to content

← Public intelligence

Maven package

org.eclipse.lemminx:lemminx-parent

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.5MavenPublished

    Exposure of Sensitive Information to an Unauthorized Actor in LemMinX

    CVE-2022-0672 · GHSA-hrxv-694f-22g3

    Affected
    • Maven org.eclipse.lemminx:lemminx-parent < 0.19.0
    Fixed in
    0.19.0· Vendor fix available
    Issue
    A flaw was found in LemMinX in versions prior to 0.19.0. Insecure redirect could allow unauthorized access to sensitive information locally if LemMinX is run under a privileged user.

    Recommended action: Upgrade to 0.19.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Critical, CVSS 9.1MavenPublished

    Server-Side Request Forgery and Uncontrolled Resource Consumption in LemMinX

    CVE-2022-0671 · GHSA-52vv-3vf7-f7wh

    Affected
    • Maven org.eclipse.lemminx:lemminx-parent < 0.19.0
    Fixed in
    0.19.0· Vendor fix available
    Issue
    A flaw was found in vscode-xml in versions prior to 0.19.0. Schema download could lead to blind SSRF or DoS via a large file.

    Recommended action: Upgrade to 0.19.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Medium, CVSS 6.5MavenPublished

    Path Traversal in LemMinX

    CVE-2022-0673 · GHSA-gggp-gh2p-996x

    Affected
    • Maven org.eclipse.lemminx:lemminx-parent < 0.19.0
    Fixed in
    0.19.0· Vendor fix available
    Issue
    A flaw was found in LemMinX in versions prior to 0.19.0. Cache poisoning of external schema files is possible due to directory traversal.

    Recommended action: Upgrade to 0.19.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →