jose-node-cjs-runtime vulnerabilities

Registry
npm
Latest
5.10.0
License
MIT

3 known advisories

The latest version, 5.10.0, is not affected by any of them. Projects on older versions may be.

Update to the latest version:npm install jose-node-cjs-runtime@5.10.0

Security advisories for jose-node-cjs-runtime

  • MediumGHSA-hhhv-q57g-882q7 Mar 2024

    jose vulnerable to resource exhaustion via specifically crafted JWE with compressed plaintext

    Affected
    <4.15.5
    Fixed in
    4.15.5
  • MediumGHSA-jv3g-j58f-9mq916 Sept 2022

    JOSE vulnerable to resource exhaustion via specifically crafted JWE

    Affected
    >=3.0.0 <3.20.4 · >=4.0.0 <4.9.2
    Fixed in
    3.20.4, 4.9.2
  • MediumGHSA-rvcw-f68w-8h8h19 Apr 2021

    Padding Oracle Attack due to Observable Timing Discrepancy in jose-node-cjs-runtime

    Affected
    <3.11.4
    Fixed in
    3.11.4

Which of your client projects still run an old jose-node-cjs-runtime?

NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other npm packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.