CVE-2022-36083
A public proof of concept exists; no exploitation attested.
- Published2022-09-07
- Fixed in4.9.2 · 3.20.4 · 2.0.6 · 1.28.2
- WeaknessCWE-400 · CWE-834
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
JOSE is "JSON Web Almost Everything" - JWA, JWS, JWE, JWT, JWK, JWKS with no dependencies using runtime's native crypto in Node.js, Browser, Cloudflare Workers, Electron, and Deno. The PBKDF2-based JWE key management algorithms expect a JOSE Header Parameter named `p2c` PBES2 Count, which determines how many PBKDF2 iterations must be executed in order to derive a CEK wrapping key. The purpose of this parameter is to intentionally slow down the key derivation function in order to make password brute-force and dictionary attacks more expensive. This makes the PBES2 algorithms unsuitable for situations where the JWE is coming from an untrusted source: an adversary can intentionally pick an extremely high PBES2 Count value, that will initiate a CPU-bound computation that may take an unreasonable amount of time to finish. Under certain conditions, it is possible to have the user's environment consume unreasonable amount of CPU time. The impact is limited only to users utilizing the JWE decryption APIs with symmetric secrets to decrypt JWEs from untrusted parties who do not limit the accepted JWE Key Management Algorithms (`alg` Header Parameter) using the `keyManagementAlgorithms` (or `algorithms` in v1.x) decryption option or through other means. The `v1.28.2`, `v2.0.6`, `v3.20.4`, and `v4.9.2` releases limit the maximum PBKDF2 iteration count to `10000` by default. It is possible to adjust this limit with a newly introduced `maxPBES2Count` decryption option. If users are unable to upgrade their required library version, they have two options depending on whether they expect to receive JWEs using any of the three PBKDF2-based JWE key management algorithms. They can use the `keyManagementAlgorithms` decryption option to disable accepting PBKDF2 altogether, or they can inspect the JOSE Header prior to using the decryption API and limit the PBKDF2 iteration count (`p2c` Header Parameter).
Timeline
dates in UTC- 2022-09-0722:15CVE publishedNVD
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.x | ≥ 4.0.0, < 4.9.2 | 4.9.2 | NVD · OSV |
| 3.x | ≥ 3.0.0, < 3.20.4 | 3.20.4 | NVD · OSV |
| 2.0 | ≥ 2.0.0, < 2.0.6 | 2.0.6 | NVD · OSV |
| 1.x | ≥ 1.0.0, < 1.28.2 | 1.28.2 | NVD · OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- panva joseAffected
- = >= 1.0, < 1.28.2no fix stated
- = >= 2.0, < 2.0.6no fix stated
- = >= 3.0, < 3.20.4no fix stated
- = >= 4.0, < 4.9.2no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2022-09-07
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- joseUbuntu:26.10all versions · no fixed version listed
- joseUbuntu:26.04:LTSall versions · no fixed version listed
- joseUbuntu:25.10all versions · no fixed version listed
- joseUbuntu:24.04:LTSall versions · no fixed version listed
- node-joseUbuntu:22.04:LTSall versions · no fixed version listed
- node-joseDebian:13all versions · fixed in 4.9.2-1
- node-joseDebian:12all versions · fixed in 4.9.2-1
Fix
- Update Panva jose to 4.9.2 · 3.20.4 · 2.0.6 · 1.28.2
Advisories and patches
- github.comPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- CISA-ADP (SSVC)PoC stated2025-04-22
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- CISA-ADPSSVC decisionpoc2025-04-22
- CNACVSS 3.15.3known since 2026-10-23
- NVDCVSS 3.15.3read 2026-10-23
- CNAweakness (CWE)CWE-400known since 2026-10-23
- NVDweakness (CWE)CWE-834read 2026-10-23
- FIRST EPSSEPSS score1.6 %2026-11-18
- OSVaffected packages—
- GitHub AdvisoriesadvisoryMODERATE2022-09-16
Identifiers
- EUVD-2022-6862same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-jv3g-j58f-9mq9same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- Published
- 2022-09-07
- Last Modified
- 2026-06-22
- NVD status
- Modified
- GitHub Advisory
- GHSA-jv3g-j58f-9mq9
Frequently asked questions
What is CVE-2022-36083?
Is CVE-2022-36083 actively exploited?
What is the CVSS score for CVE-2022-36083?
Running jose? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-jv3g-j58f-9mq9
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- CISA Vulnrichment · CC0-1.0