{"answers":{"affected":"3 open source packages ship an affected version, including zodb3. It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-3495 in the wild and no public exploit code.","fix":"Upgrade zodb3 to a fixed version for your release line: 3.10.0a1 or 3.10.0a2.","what":"CVE-2010-3495 is a medium-severity vulnerability in n/a, published on 19 Oct 2010. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2010-3495 and fix it if it is affected.\n\nWhat it is: CVE-2010-3495 is a medium-severity vulnerability in n/a, published on 19 Oct 2010. 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-2010-3495 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- zodb3 (PyPI): affected all versions; fixed in 3.10.0a1\n- zodb3 (PyPI): affected all versions; fixed in 3.10.0a2\n- zodb3 (PyPI): affected all versions; fixed in 3.10.0a2\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-2010-3495/ (Markdown: https://insights.sbomify.com/CVE-2010-3495/index.md)","id":"CVE-2010-3495","markdown":"https://insights.sbomify.com/CVE-2010-3495/index.md","name":"CVE-2010-3495","record":{"aliases":["GHSA-j6m4-frxh-p4x8","PYSEC-2010-27"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"ZODB database","requires_auth":"none","summary":"Remote attackers can cause a denial of service in ZODB by exploiting a race condition during TCP connection handling, crashing the daemon.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"zodb","vendor":"zope"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"Race condition in ZEO/StorageServer.py in Zope Object Database (ZODB) before 3.10.0 allows remote attackers to cause a denial of service (daemon outage) by establishing and then immediately closing a TCP connection, leading to the accept function having an unexpected return value of None, an unexpected value of None for the address, or an ECONNABORTED, EAGAIN, or EWOULDBLOCK error, a related issue to CVE-2010-3492.","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":"Zope Object Database Denial of Service vulnerability","id":"CVE-2010-3495","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"race_condition","year":"2010"},"n_packages":3,"n_references":9,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2010-3496"},"packages":[{"ecosystem":"PyPI","fixed":["3.10.0a1"],"introduced":["0"],"last_affected":[],"package":"zodb3","purl":"pkg:pypi/zodb3","source":"PYSEC-2010-27"},{"ecosystem":"PyPI","fixed":["3.10.0a2"],"introduced":["0"],"last_affected":[],"package":"zodb3","purl":null,"source":"GHSA-j6m4-frxh-p4x8"},{"ecosystem":"PyPI","fixed":["3.10.0a2"],"introduced":["0"],"last_affected":[],"package":"zodb3","purl":"pkg:pypi/zodb3","source":"GHSA-j6m4-frxh-p4x8"}],"prev":{"headline":"Concurrent Execution using Shared Resource with Improper Synchronization in pyftpdlib","id":"CVE-2010-3494"},"products":["n/a"],"published":"2010-10-19","related":[{"cvss_score":7.5,"headline":"Zope Object Database (ZODB) Authentication bypass in ZEO storage servers","id":"CVE-2009-0669","kev_date_added":null,"published":"2009-08-07"},{"cvss_score":6.5,"headline":"Zope Object Database (ZODB) vulnerable to arbitrary Python code execution in ZEO storage servers","id":"CVE-2009-0668","kev_date_added":null,"published":"2009-08-07"},{"cvss_score":6,"headline":"Zope Object Database (ZODB) Arbitrary files reading and deletion","id":"CVE-2009-2701","kev_date_added":null,"published":"2009-09-08"}],"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-07","vendors":["n/a"]},"summary":"Remote attackers can cause a denial of service in ZODB by exploiting a race condition during TCP connection handling, crashing the daemon.","url":"https://insights.sbomify.com/CVE-2010-3495/"}