cve.bz

CVE-2022-1930 ethereum eth-account

7.5 highExploit referenceEPSS 0.9%Fix available

High (7.5) in ethereum eth-account. EPSS 0.9% estimated probability of exploitation activity in the next 30 days. Fixed in eth-account 0.5.9.

An exponential ReDoS (Regular Expression Denial of Service) can be triggered in the eth-account PyPI package, when an attacker is able to supply arbitrary input to the encode_structured_data method

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 62nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-1333 Inefficient Regular Expression Complexity
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-2022-1930 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-1930?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-1930?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-2022-1930 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 CNA's record in the CVE List.

ProductAffected
eth-accountbefore 0.5.9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v65g-f3cj-fjp4PyPIeth-account<0.5.90.5.9
PYSEC-2026-806PyPIeth-account<0.5.90.5.9

Attack patterns (CAPEC)

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

References

Check your stackJSON