Skip to content

← Public intelligence

npm package

mversion

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

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

  1. High, CVSS 7.8npmAmendedPublished

    OS Command Injection in mversion

    CVE-2020-7688 · GHSA-6m8p-4fxj-pgc2

    Affected
    • npm mversion <= 1.13.0
    Fixed in
    2.0.1· Vendor fix available
    Issue
    The issue occurs because tagName user input is formatted inside the exec function is executed without any checks.

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

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 7.3npmAmendedPublished

    Command injection in mversion

    CVE-2020-4059 · GHSA-qjg4-w4c6-f6c6

    Affected
    • npm mversion < 2.0.0
    Fixed in
    2.0.0· Vendor fix available
    Issue
    Impact This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. Patches Patched by version 2.0.0. Previous releases are deprecated in npm. Workarounds Make sure to escape git commit messages when using the commitMessage option for the update function.

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

    Sources:osv.dev (1)github.com (2)Source checked Evidence →