usn-3199-2
Vulnerability from osv_ubuntu
Published
2017-02-17 17:34
Modified
2026-02-10 04:41
Summary
Python Crypto regression
Details

USN-3199-1 fixed a vulnerability in the Python Cryptography Toolkit. Unfortunately, various programs depended on the original behavior of the Python Cryptography Toolkit which was altered when fixing the vulnerability. This update retains the fix for the vulnerability but issues a warning rather than throwing an exception. Code which produces this warning should be updated because future versions of the Python Cryptography Toolkit re-introduce the exception.

We apologize for the inconvenience.

Original advisory details:

It was discovered that the ALGnew function in block_template.c in the Python Cryptography Toolkit contained a heap-based buffer overflow vulnerability. A remote attacker could use this flaw to execute arbitrary code by using a crafted initialization vector parameter.

References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "cves_map": {
          "cves": [
            {
              "id": "CVE-2013-7459",
              "severity": [
                {
                  "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            }
          ],
          "ecosystem": "Ubuntu:14.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "python-crypto",
            "binary_version": "2.6.1-4ubuntu0.2"
          },
          {
            "binary_name": "python3-crypto",
            "binary_version": "2.6.1-4ubuntu0.2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:14.04:LTS",
        "name": "python-crypto",
        "purl": "pkg:deb/ubuntu/python-crypto@2.6.1-4ubuntu0.2?arch=source\u0026distro=trusty"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.6.1-4ubuntu0.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "2.6-5",
        "2.6.1-2",
        "2.6.1-2build1",
        "2.6.1-3",
        "2.6.1-4",
        "2.6.1-4build1",
        "2.6.1-4ubuntu0.1"
      ]
    },
    {
      "database_specific": {
        "cves_map": {
          "cves": [
            {
              "id": "CVE-2013-7459",
              "severity": [
                {
                  "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            }
          ],
          "ecosystem": "Ubuntu:16.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "python-crypto",
            "binary_version": "2.6.1-6ubuntu0.16.04.2"
          },
          {
            "binary_name": "python3-crypto",
            "binary_version": "2.6.1-6ubuntu0.16.04.2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:16.04:LTS",
        "name": "python-crypto",
        "purl": "pkg:deb/ubuntu/python-crypto@2.6.1-6ubuntu0.16.04.2?arch=source\u0026distro=xenial"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.6.1-6ubuntu0.16.04.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "2.6.1-5build1",
        "2.6.1-6",
        "2.6.1-6build1",
        "2.6.1-6ubuntu0.16.04.1"
      ]
    }
  ],
  "aliases": [],
  "details": "USN-3199-1 fixed a vulnerability in the Python Cryptography Toolkit.\nUnfortunately, various programs depended on the original behavior of the Python\nCryptography Toolkit which was altered when fixing the vulnerability. This\nupdate retains the fix for the vulnerability but issues a warning rather than\nthrowing an exception. Code which produces this warning should be updated\nbecause future versions of the Python Cryptography Toolkit re-introduce the\nexception.\n\nWe apologize for the inconvenience.\n\nOriginal advisory details:\n\n It was discovered that the ALGnew function in block_template.c in the Python\n Cryptography Toolkit contained a heap-based buffer overflow vulnerability.\n A remote attacker could use this flaw to execute arbitrary code by using\n a crafted initialization vector parameter.\n",
  "id": "USN-3199-2",
  "modified": "2026-02-10T04:41:05Z",
  "published": "2017-02-17T17:34:13Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-3199-2"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2013-7459"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "summary": "Python Crypto regression",
  "upstream": [
    "UBUNTU-CVE-2013-7459"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.