Skip to content

← Public intelligence

PyPI package

pycrypto

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.7PyPIAmendedPublished

    PyCrypto does not properly reseed PRNG before allowing access

    CVE-2013-1445 · GHSA-x377-f64p-hf5j

    Affected
    • PyPI pycrypto < 2.6.1
    Fixed in
    2.6.1· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 2.6.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. Medium, CVSS 6.9PyPIAmendedPublished

    PyCrypto makes Use of Insufficiently Random Values

    CVE-2012-2417 · GHSA-v367-p58w-98h5

    Affected
    • PyPI pycrypto < 2.6
    Fixed in
    2.6· Vendor fix available
    Issue
    PyCrypto before 2.6 does not produce appropriate prime numbers when using an ElGamal scheme to generate a key, which reduces the signature space or public key space and makes it easier for attackers to conduct brute force attacks to obtain the private key.

    Recommended action: Upgrade to 2.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →