{"answers":{"affected":"2 open source packages ship an affected version, including jose-node-esm-runtime. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-29445 in the wild and no public exploit code.","fix":"Upgrade jose-node-esm-runtime to 3.11.4 or later.","what":"CVE-2021-29445 is a medium-severity vulnerability in panva jose-node-esm-runtime, published on 16 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-29445 and fix it if it is affected.\n\nWhat it is: CVE-2021-29445 is a medium-severity vulnerability in panva jose-node-esm-runtime, published on 16 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-29445 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jose-node-esm-runtime (npm): affected all versions; fixed in 3.11.4\n- jose-node-esm-runtime (npm): affected all versions; fixed in 3.11.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-29445/ (Markdown: https://insights.sbomify.com/CVE-2021-29445/index.md)","id":"CVE-2021-29445","markdown":"https://insights.sbomify.com/CVE-2021-29445/index.md","name":"CVE-2021-29445","record":{"aliases":["GHSA-4v4g-726h-xvfv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js crypto library","requires_auth":"none","summary":"An attacker can decrypt data without the key by exploiting a timing side-channel in the AES-CBC-HMAC decryption process of this Node.js library.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jose-node-cjs-runtime","vendor":"jose-node-cjs-runtime_project"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"jose-node-esm-runtime is an npm package which provides a number of cryptographic functions. In versions prior to 3.11.4 the AES_CBC_HMAC_SHA2 Algorithm (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) decryption would always execute both HMAC tag verification and CBC decryption, if either failed `JWEDecryptionFailed` would be thrown. But a possibly observable difference in timing when padding error would occur while decrypting the ciphertext makes a padding oracle and an adversary might be able to make use of that oracle to decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). A patch was released which ensures the HMAC tag is verified before performing CBC decryption. The fixed versions are `\u003e=3.11.4`. Users should upgrade to `^3.11.4`.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Padding Oracle Attack due to Observable Timing Discrepancy in jose-node-esm-runtime","id":"CVE-2021-29445","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Padding Oracle Attack due to Observable Timing Discrepancy in jose-node-cjs-runtime","id":"CVE-2021-29446"},"packages":[{"ecosystem":"npm","fixed":["3.11.4"],"introduced":["0"],"last_affected":[],"package":"jose-node-esm-runtime","purl":null,"source":"GHSA-4v4g-726h-xvfv"},{"ecosystem":"npm","fixed":["3.11.4"],"introduced":["0"],"last_affected":[],"package":"jose-node-esm-runtime","purl":"pkg:npm/jose-node-esm-runtime","source":"GHSA-4v4g-726h-xvfv"}],"prev":{"headline":"Padding Oracle Attack due to Observable Timing Discrepancy in jose-browser-runtime","id":"CVE-2021-29444"},"products":["jose-node-esm-runtime"],"published":"2021-04-16","related":[{"cvss_score":5.9,"headline":"Padding Oracle Attack due to Observable Timing Discrepancy in jose-browser-runtime","id":"CVE-2021-29444","kev_date_added":null,"published":"2021-04-16"},{"cvss_score":5.9,"headline":"Padding Oracle Attack due to Observable Timing Discrepancy in jose-node-cjs-runtime","id":"CVE-2021-29446","kev_date_added":null,"published":"2021-04-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["panva"]},"summary":"An attacker can decrypt data without the key by exploiting a timing side-channel in the AES-CBC-HMAC decryption process of this Node.js library.","url":"https://insights.sbomify.com/CVE-2021-29445/"}