OESA-2024-2119 (CVE-2024-6923)

Vulnerability from osv_openeuler – Published: 2024-09-06 11:07 – Updated: 2026-08-06 11:07 – Source website
VLAI
Summary
python3 security update
Details

Python combines remarkable power with very clear syntax. It has modules, classes, exceptions, very high level dynamic data types, and dynamic typing. There are interfaces to many system calls and libraries, as well as to various windowing systems. New built-in modules are easily written in C or C++ (or other languages, depending on the chosen implementation). Python is also usable as an extension language for applications written in other languages that need easy-to-use scripting or automation interfaces.

Security Fix(es):

There is a MEDIUM severity vulnerability affecting CPython.

The email module didn’t properly quote newlines for email headers when serializing an email message allowing for header injection when an email is serialized.(CVE-2024-6923)

There is a LOW severity vulnerability affecting CPython, specifically the 'http.cookies' standard library module.

When parsing cookies that contained backslashes for quoted characters in the cookie value, the parser would use an algorithm with quadratic complexity, resulting in excess CPU resources being used while parsing the value.(CVE-2024-7592)

There is a HIGH severity vulnerability affecting the CPython "zipfile" module affecting "zipfile.Path". Note that the more common API "zipfile.ZipFile" class is unaffected.

When iterating over names of entries in a zip archive (for example, methods of "zipfile.Path" like "namelist()", "iterdir()", etc) the process can be put into an infinite loop with a maliciously crafted zip archive. This defect applies when reading only metadata or extracting the contents of the zip archive. Programs that are not handling user-controlled zip archives are not affected.(CVE-2024-8088)


{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "python3-3.9.9-35.oe2203sp4.aarch64.rpm",
          "python3-debug-3.9.9-35.oe2203sp4.aarch64.rpm",
          "python3-debuginfo-3.9.9-35.oe2203sp4.aarch64.rpm",
          "python3-debugsource-3.9.9-35.oe2203sp4.aarch64.rpm",
          "python3-devel-3.9.9-35.oe2203sp4.aarch64.rpm",
          "python3-unversioned-command-3.9.9-35.oe2203sp4.aarch64.rpm"
        ],
        "noarch": [
          "python3-help-3.9.9-35.oe2203sp4.noarch.rpm"
        ],
        "src": [
          "python3-3.9.9-35.oe2203sp4.src.rpm"
        ],
        "x86_64": [
          "python3-3.9.9-35.oe2203sp4.x86_64.rpm",
          "python3-debug-3.9.9-35.oe2203sp4.x86_64.rpm",
          "python3-debuginfo-3.9.9-35.oe2203sp4.x86_64.rpm",
          "python3-debugsource-3.9.9-35.oe2203sp4.x86_64.rpm",
          "python3-devel-3.9.9-35.oe2203sp4.x86_64.rpm",
          "python3-unversioned-command-3.9.9-35.oe2203sp4.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:22.03-LTS-SP4",
        "name": "python3",
        "purl": "pkg:rpm/openEuler/python3\u0026distro=openEuler-22.03-LTS-SP4"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.9.9-35.oe2203sp4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "High"
  },
  "details": "Python combines remarkable power with very clear syntax. It has modules, classes, exceptions, very high level dynamic data types, and dynamic typing. There are interfaces to many system calls and libraries, as well as to various windowing systems. New built-in modules are easily written in C or C++ (or other languages, depending on the chosen implementation). Python is also usable as an extension language for applications written in other languages that need easy-to-use scripting or automation interfaces.\r\n\r\nSecurity Fix(es):\r\n\r\nThere is a MEDIUM severity vulnerability affecting CPython.\r\n\r\nThe \nemail module didn\u2019t properly quote newlines for email headers when \nserializing an email message allowing for header injection when an email\n is serialized.(CVE-2024-6923)\r\n\r\nThere is a LOW severity vulnerability affecting CPython, specifically the\n\u0026apos;http.cookies\u0026apos; standard library module.\r\n\r\n\nWhen parsing cookies that contained backslashes for quoted characters in\nthe cookie value, the parser would use an algorithm with quadratic\ncomplexity, resulting in excess CPU resources being used while parsing the\nvalue.(CVE-2024-7592)\r\n\r\nThere is a HIGH severity vulnerability affecting the CPython \u0026quot;zipfile\u0026quot;\nmodule affecting \u0026quot;zipfile.Path\u0026quot;. Note that the more common API \u0026quot;zipfile.ZipFile\u0026quot; class is unaffected.\r\n\r\n\r\n\r\n\r\n\r\nWhen iterating over names of entries in a zip archive (for example, methods\nof \u0026quot;zipfile.Path\u0026quot; like \u0026quot;namelist()\u0026quot;, \u0026quot;iterdir()\u0026quot;, etc)\nthe process can be put into an infinite loop with a maliciously crafted\nzip archive. This defect applies when reading only metadata or extracting\nthe contents of the zip archive. Programs that are not handling\nuser-controlled zip archives are not affected.(CVE-2024-8088)",
  "id": "OESA-2024-2119",
  "modified": "2026-08-06T11:07:35Z",
  "published": "2024-09-06T11:07:35Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2119"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-6923"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-7592"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-8088"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "python3 security update",
  "upstream": [
    "CVE-2024-6923",
    "CVE-2024-7592",
    "CVE-2024-8088"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.