The Crypto.Random.atfork function in PyCrypto before 2.6.1 does not properly reseed the pseudo-random number generator (PRNG) before allowing a child process to access it, which makes it easier for context-dependent attackers to obtain sensitive information by leveraging a race condition in which a child process is created and accesses the PRNG within the same rate-limit period as another process.
Advisories
Source ID Title
Debian DSA Debian DSA DSA-2781-1 python-crypto security update
EUVD EUVD EUVD-2013-0027 The Crypto.Random.atfork function in PyCrypto before 2.6.1 does not properly reseed the pseudo-random number generator (PRNG) before allowing a child process to access it, which makes it easier for context-dependent attackers to obtain sensitive information by leveraging a race condition in which a child process is created and accesses the PRNG within the same rate-limit period as another process.
Github GHSA Github GHSA GHSA-x377-f64p-hf5j PyCrypto does not properly reseed PRNG before allowing access
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: debian

Published:

Updated: 2024-09-16T16:43:18.789Z

Reserved: 2013-01-26T00:00:00Z

Link: CVE-2013-1445

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2013-10-26T17:55:03.027

Modified: 2025-04-11T00:51:21.963

Link: CVE-2013-1445

cve-icon Redhat

Severity : Low

Publid Date: 2013-10-17T00:00:00Z

Links: CVE-2013-1445 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses