CVE-2013-1895

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.2%, top 21% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The py-bcrypt module before 0.3 for Python does not properly handle concurrent memory access, which allows attackers to bypass authentication via multiple authentication requests, which trigger the password hash to be overwritten.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
85.0%
KEV
Not listed

Published

January 28, 2020

Last Modified

November 21, 2024

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
py-bcrypt0.1, 0.20.3

Frequently asked(5)

What is CVE-2013-1895?
CVE-2013-1895 is a high vulnerability published on January 28, 2020. The py-bcrypt module before 0.3 for Python does not properly handle concurrent memory access, which allows attackers to bypass authentication via multiple authentication requests, which trigger the password hash to be overwritten.
When was CVE-2013-1895 disclosed?
CVE-2013-1895 was first published in the National Vulnerability Database on January 28, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-1895 actively exploited?
CVE-2013-1895 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2013-1895?
CVE-2013-1895 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2013-1895?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-1895, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-1895

Explore →

Is Your Infrastructure Affected by CVE-2013-1895?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.