cve.bz

CVE-2023-49290 lestrrat-go jwx: Uncontrolled Resource Consumption

5.3 mediumExploit referenceEPSS 0.7%Fix available

Medium (5.3) in lestrrat-go jwx. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/lestrrat-go/jwx 1.2.27.

On this page
lestrrat-go/jwx is a Go module implementing various JWx (JWA/JWE/JWK/JWS/JWT, otherwise known as JOSE) technologies. A p2c parameter set too high in JWE's algorithm PBES2-* could lead to a denial of service. The JWE key management algorithms based on PBKDF2 require a JOSE Header Parameter called p2c (PBES2 Count). This parameter dictates the number of PBKDF2 iterations needed to derive a CEK wrapping key. Its primary purpose is to intentionally slow down the key derivation function, making password brute-force and dictionary attacks more resource- intensive. Therefore, if an attacker sets the p2c parameter in JWE to a very large number, it can cause a lot of computational consumption, resulting in a denial of service. This vulnerability has been addressed in commit `64f2a229b` which has been included in release version 1.2.27 and 2.0.18. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2025-05-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-49290 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-49290?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-49290?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-49290 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
lestrrat-go:jwxbefore 1.2.27
lestrrat-go:jwxfrom 2.0.0 before 2.0.18

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7f9x-gw85-8grfGogithub.com/lestrrat-go/jwx<1.2.271.2.27
GHSA-7f9x-gw85-8grfGogithub.com/lestrrat-go/jwx/v2<2.0.182.0.18
GO-2023-2379Gogithub.com/lestrrat-go/jwx<1.2.271.2.27
GO-2023-2379Gogithub.com/lestrrat-go/jwx/v2<2.0.182.0.18

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
OpenShift Service Mesh 2openshift-service-mesh/istio-cni-rhel8Will not fix
OpenShift Service Mesh 2openshift-service-mesh/pilot-rhel8Will not fix
OpenShift Service Mesh 2openshift-service-mesh/proxyv2-rhel8Will not fix
Red Hat Openshift Data Foundation 4odf4/ocs-must-gather-rhel8Not affected
Red Hat Openshift Data Foundation 4odf4/ocs-rhel9-operatorNot affected
Red Hat Openshift Data Foundation 4odf4/odf-rhel9-operatorNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-49290.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON