How severe is GHSA-2mrj-435v-c2cr?

No CVSS score has been assigned to GHSA-2mrj-435v-c2cr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2mrj-435v-c2cr?

GHSA-2mrj-435v-c2cr affects the following packages: ecdsa (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-2mrj-435v-c2cr?

Update ecdsa to 0.13.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2mrj-435v-c2cr is resolved across your whole dependency graph.

How do I detect GHSA-2mrj-435v-c2cr in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ecdsa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2mrj-435v-c2cr if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-2mrj-435v-c2cr actively exploited in the wild?

No public exploit code has been indexed for GHSA-2mrj-435v-c2cr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2mrj-435v-c2cr?

GHSA-2mrj-435v-c2cr has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 84th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2mrj-435v-c2cr?

GHSA-2mrj-435v-c2cr is classified as CWE-391 (CWE-391), CWE-755 (CWE-755). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2mrj-435v-c2cr published, and has it been updated?

GHSA-2mrj-435v-c2cr was published on December 2, 2019 and was last updated on November 30, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Withdrawn — this advisory has been retracted

🐍 PyPI

Not in CISA KEV

Duplicate Advisory: possible DoS caused by malformed signature decoding in Pure-Python ECDSAGHSA-2mrj-435v-c2cr

GHSA-2mrj-435v-c2cr is a CWE-391 vulnerability in ecdsa. A fix is available for ecdsa — see the affected versions and patch details below.

Also known asCVE-2019-14853 GHSA-pwfw-mgfj-7g3gPYSEC-2019-177

Published

Dec 2, 2019

Updated

Nov 30, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍ecdsa

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

An error-handling flaw was found in python-ecdsa before version 0.13.3. During signature decoding, malformed DER signatures could raise unexpected exceptions (or no exceptions at all), which could lead to a denial of service.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ecdsa`	all versions	0.13.3`pip install --upgrade 'ecdsa==0.13.3'`

Affected Products

1 product · 1 configurations

Application

python-ecdsapython-ecdsa_project

< 0.13.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ecdsa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ecdsa to 0.13.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2mrj-435v-c2cr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Although Red Hat OpenStack Platform ships the flawed code, RHOSP does not actually use python-ecdsa's functionality. As such, Red Hat OpenStack Platform will not be providing a fix for python-ecdsa at this time. Current releases of Red Hat Virtualization Manager no longer includes python-ecdsa as a dependency. While…

Product	Fixed in	Advisory
Red Hat Satellite 6.10 for RHEL 7	`python-ecdsa-0:0.13.3-2.el7pc`	RHSA-2021:4702

Frequently Asked Questions

## Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-pwfw-mgfj-7g3g. This link is maintained to preserve external references.

O3 Security · Impact-Aware SCA

Is GHSA-2mrj-435v-c2cr in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works