Skip to content
OpenAdvisories

Package · npm

devalue

25 known vulnerabilities.

14 results · Clear filters · Feed

  • High 7.5

    Devalue before 5.6.3 Denial of Service via Sparse Array Serialization

    The devalue package for npm before 5.6.3 can consume excessive CPU and memory when serializing sparse arrays with uneval or stringify. An attacker who manages to get a sparse array created on the server, which mainstream wire formats do not allow, and seriali…

  • High 7.5

    Devalue before 5.9.3 CPU Amplification Denial of Service via uneval

    Sveltejs devalue before 5.9.3 contains a denial of service vulnerability that allows attackers to cause CPU amplification by supplying sparse arrays to uneval. Attackers who influence sparse values passed to uneval can force synchronous work proportional to t…

  • High 7.5

    Devalue before 5.9.3 Quadratic Expansion Denial of Service via uneval

    Sveltejs devalue before 5.9.3 contains a resource exhaustion vulnerability where repeated primitive strings cause quadratic expansion in the uneval function. Attackers can supply a small crafted payload that is parsed and then passed to uneval, producing a ve…

  • High 7.5

    Sveltejs devalue before 5.9.3 Memory Exhaustion via uneval Sparse Arrays

    Sveltejs devalue from 1.0.0 before 5.9.3 contains a memory exhaustion flaw in uneval, whose generated code for sparse arrays allocates memory proportional to the array's declared length when evaluated. Attackers who can influence a very large sparse array ser…

  • High 7.5

    Devalue before 5.9.3 Typed-Array Allocation Validation Bypass via parse

    Devalue before 5.9.3 contains a validation bypass vulnerability that allows custom ArrayBuffer revivers to skip typed-array allocation checks in the parse function. Attackers can supply very small crafted input processed by a malformed ArrayBuffer reviver to …

  • High 7.5

    Devalue 5.8.0 before 5.9.3 Denial of Service via stringifyAsync Unhandled Rejection

    devalue (sveltejs/devalue) 5.8.0 before 5.9.3 contains an unhandled promise rejection in stringifyAsync: when serializing multiple promises, a later promise rejecting before an earlier one settles leaves an internal rejection unhandled, even if the caller cat…

  • High —

    devalue: Repeated primitive strings cause quadratic expansion in uneval

    Under very constrained circumstances, data that was `parse`d and then passed to `uneval` could turn a small payload into a very large serialized string.

  • High —

    devalue: Custom ArrayBuffer revivers can bypass typed-array allocation validation

    Under very specific circumstances, `parse` could create massive ArrayBuffers with very small input. This required a malformed `ArrayBuffer` custom reviver.

  • High —

    devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise

    When serializing multiple promises, a later promise can reject before an earlier one settles. An internal rejected promise remains unhandled even if the caller catches the returned `stringifyAsync` promise. Under Node's default unhandled-rejection behavior th…

  • High 7.5

    devalue: Cross-request process memory disclosure in devalue when `stringify` / `uneval` serialize Node Buffers

    Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. In versions 5.1.0 through 5.9.2, stringify and uneval functions serialize a typed array by emitting its entire backing ArrayBuffer rat…

  • High 7.5

    Svelte devalue: DoS via sparse array deserialization

    Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From version 5.6.3 to before version 5.8.1, devalue.parse could, due to quirks in some JavaScript engines, be convinced to allocate mu…

  • High 7.5

    devalue vulnerable to denial of service due to memory/CPU exhaustion in devalue.parse

    Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From 5.1.0 to 5.6.1, certain inputs can cause devalue.parse to consume excessive CPU time and/or memory, potentially leading to denial…

  • High 7.5

    devalue vulnerable to denial of service due to memory exhaustion in devalue.parse

    Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From 5.3.0 to 5.6.1, certain inputs can cause devalue.parse to consume excessive CPU time and/or memory, potentially leading to denial…

  • High 7.9

    Svelte devalue vulnerable to prototype pollution

    Svelte devalue is a utility library. Prior to version 5.3.2, a string passed to devalue.parse could represent an object with a __proto__ property and devalue.parse does not check that an index is numeric. This could result in assigning prototypes to objects a…