{"answers":{"affected":"3 open source packages ship an affected version, including pyo. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41498 in the wild and no public exploit code.","fix":"Upgrade pyo to 1.0.4 or later.","what":"CVE-2021-41498 is a high-severity memory corruption vulnerability in n/a, published on 17 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-41498 and fix it if it is affected.\n\nWhat it is: CVE-2021-41498 is a high-severity memory corruption vulnerability in n/a, published on 17 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-41498 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pyo (PyPI): affected all versions; fixed in 1.0.4\n- pyo (PyPI): affected all versions; fixed in 1.0.4\n- pyo (PyPI): affected all versions; fixed in 1.0.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-41498/ (Markdown: https://insights.sbomify.com/CVE-2021-41498/index.md)","id":"CVE-2021-41498","markdown":"https://insights.sbomify.com/CVE-2021-41498/index.md","name":"CVE-2021-41498","record":{"aliases":["DEBIAN-CVE-2021-41498","GHSA-qj27-32wp-ghrg","PYSEC-2021-890","UBUNTU-CVE-2021-41498"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Pyo audio library","requires_auth":"none","summary":"Attackers can cause a denial of service in the Pyo audio library by sending an overlong server name, triggering a buffer overflow.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pyo","vendor":"pyo_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"Buffer overflow in ajaxsoundstudio.com Pyo \u0026lt and 1.03 in the Server_jack_init function. which allows attackers to conduct Denial of Service attacks by arbitrary constructing a overlong server name.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Pyo Buffer Overflow Vulnerability","id":"CVE-2021-41498","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":3,"n_references":1,"next":{"headline":"Classic Buffer Overflow in pyo","id":"CVE-2021-41499"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.4"],"introduced":["0"],"last_affected":[],"package":"pyo","purl":null,"source":"GHSA-qj27-32wp-ghrg"},{"ecosystem":"PyPI","fixed":["1.0.4"],"introduced":["0"],"last_affected":[],"package":"pyo","purl":"pkg:pypi/pyo","source":"GHSA-qj27-32wp-ghrg"},{"ecosystem":"PyPI","fixed":["1.0.4"],"introduced":["0"],"last_affected":[],"package":"pyo","purl":"pkg:pypi/pyo","source":"PYSEC-2021-890"}],"prev":{"headline":"bounter Null pointer reference","id":"CVE-2021-41497"},"products":["n/a"],"published":"2021-12-17","related":[{"cvss_score":7.5,"headline":"Classic Buffer Overflow in pyo","id":"CVE-2021-41499","kev_date_added":null,"published":"2021-12-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can cause a denial of service in the Pyo audio library by sending an overlong server name, triggering a buffer overflow.","url":"https://insights.sbomify.com/CVE-2021-41498/"}