Skip to content

← Public intelligence

npm package

yapi-vendor

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. Medium, CVSS 5.1npmAmendedPublished

    Weak JSON Web Token in yapi-vendor

    CVE-2021-27884 · GHSA-2h3h-vw8r-82rp

    Affected
    • npm yapi-vendor <= 1.9.2
    Fixed in
    1.9.3· Vendor fix available
    Issue
    Weak JSON Web Token (JWT) signing secret generation in YMFE YApi through 1.9.2 allows recreation of other users' JWT tokens. This occurs because Math.random in Node.js is used as a source of randomness in jwt signing. Math.random does not provide cryptographically secure random numbers. This has been patched in version 1.9.3.

    Recommended action: Upgrade to 1.9.3 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. Medium, CVSS 5.4npmAmendedPublished

    Cross-site Scripting in yapi-vendor

    CVE-2018-17574 · GHSA-5xgh-643p-cp2g

    Affected
    • npm yapi-vendor < 1.3.23
    Fixed in
    1.3.23· Vendor fix available
    Issue
    An issue was discovered in YMFE YApi 1.3.23. There is stored XSS in the name field of a project.

    Recommended action: Upgrade to 1.3.23 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 →