Skip to content

← Public intelligence

npm package

mixme

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. UnratednpmAmendedPublished

    Prototype Pollution in mixme

    GHSA-84p7-fh9c-6g8h

    Affected
    • npm mixme < 0.5.2
    Fixed in
    0.5.2· Vendor fix available
    Issue
    Impact When copying properties from a source object to a target object, the target object can gain access to certain properties of the source object and modify their content. Patches The problem was patch with a more agressive discovery of secured properties to filter out.

    Recommended action: Upgrade to 0.5.2 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. Critical, CVSS 9.1npmAmendedPublished

    Prototype Pollution in mixme

    CVE-2021-28860 · GHSA-79jw-6wg7-r9g4

    Affected
    • npm mixme < 0.5.1
    Fixed in
    0.5.1· Vendor fix available
    Issue
    Node.js mixme 0.5.0, an attacker can add or alter properties of an object via 'proto' through the mutate() and merge() functions. The polluted attribute will be directly assigned to every object in the program. This will put the availability of the program at risk causing a potential denial of service (DoS).

    Recommended action: Upgrade to 0.5.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)osv.dev (2)Source checked Evidence →