Vulnerability in jose-node-esm-runtime (CVE-2021-29445)
Summary
Vulnerability in jose-node-esm-runtime (CVE-2021-29445). Confidential information can be exposed externally. Exploitable via JWEDecryptionFailed. Mitigation: upgrade to 3.11.4 or later.
Original description
The description as published by the source.
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 >=3.11.4. Users should upgrade to ^3.11.4.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-29445 has been found in jose-node-esm-runtime.
Attackers can target a specific entry point like JWEDecryptionFailed over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade jose-node-esm-runtime to 3.11.4 or later.
If unsure, ask your IT team or search "jose-node-esm-runtime CVE-2021-29445" on the vendor's site.
CVE-2021-29445 (jose-node-esm-runtime) — CWE-203
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: JWEDecryptionFailed
Patched: 3.11.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-203) exists in jose-node-esm-runtime. Attackers reach the vulnerable code path via JWEDecryptionFailed without authentication.
Check the vendor advisory for the affected versions of jose-node-esm-runtime. Attack surface: JWEDecryptionFailed.
Severity: ?. Confidential information can be exposed externally.
Update to 3.11.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'jose-node-esm-runtime' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'jose-node-esm-runtime' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
jose-node-esm-runtimeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade jose-node-esm-runtime to 3.11.4ステージング環境で 3.11.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory npmjs.com
- package github.com