{"answers":{"affected":"3 open source packages ship an affected version, including aim. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10110 exists.","fix":"No fix has been published for CVE-2024-10110 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-10110 is a high-severity denial of service vulnerability in aimhubio/aim, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-10110 and fix it if it is affected.\n\nWhat it is: CVE-2024-10110 is a high-severity denial of service vulnerability in aimhubio/aim, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10110 exists.\n\nAffected packages and fixed versions:\n- aim (PyPI): affected from 3.15.0 up to 3.23.0; no fix listed\n- aim (PyPI): affected from 3.15.0 up to 3.23.0; no fix listed\n- aim (PyPI): affected from 3.15.0 up to 3.23.0; no fix listed\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-2024-10110/ (Markdown: https://insights.sbomify.com/CVE-2024-10110/index.md)","id":"CVE-2024-10110","markdown":"https://insights.sbomify.com/CVE-2024-10110/index.md","name":"CVE-2024-10110","record":{"aliases":["GHSA-fx47-jpv9-7hxr","PYSEC-2026-1086"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"AIM tracking server","requires_auth":"none","summary":"An attacker can block the main thread of the AIM tracking server by instantiating a ScheduledStatusReporter, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"aim","vendor":"aimstack"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"In version 3.23.0 of aimhubio/aim, the ScheduledStatusReporter object can be instantiated to run on the main thread of the tracking server, leading to the main thread being blocked indefinitely. This results in a denial of service as the tracking server becomes unable to respond to other requests.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Denial of Service in aimhubio/aim","id":"CVE-2024-10110","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"OAuth Single Sign On – SSO (OAuth Client) \u003c= 6.26.3 - Authentication Bypass","id":"CVE-2024-10111"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["3.15.0"],"last_affected":["3.23.0"],"package":"aim","purl":null,"source":"GHSA-fx47-jpv9-7hxr"},{"ecosystem":"PyPI","fixed":[],"introduced":["3.15.0"],"last_affected":["3.23.0"],"package":"aim","purl":"pkg:pypi/aim","source":"GHSA-fx47-jpv9-7hxr"},{"ecosystem":"PyPI","fixed":[],"introduced":["3.15.0"],"last_affected":["3.23.0"],"package":"aim","purl":"pkg:pypi/aim","source":"PYSEC-2026-1086"}],"prev":{"headline":"Incorrect Authorization in mintplex-labs/anything-llm","id":"CVE-2024-10109"},"products":["aimhubio/aim"],"published":"2025-03-20","related":[{"cvss_score":9.8,"headline":"Arbitrary File Overwrite and Data Exfiltration in aimhubio/aim","id":"CVE-2024-6396","kev_date_added":null,"published":"2024-07-12"},{"cvss_score":9.8,"headline":"Remote Code Execution in aimhubio/aim","id":"CVE-2024-2195","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":9.1,"headline":"Arbitrary File Overwrite through tarfile-extraction in aimhubio/aim","id":"CVE-2024-6829","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":9.1,"headline":"Arbitrary File Deletion via Relative Path Traversal in aimhubio/aim","id":"CVE-2024-8769","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.8,"headline":"Aim vulnerable to Cross-site Scripting","id":"CVE-2025-51464","kev_date_added":null,"published":"2025-07-22"},{"cvss_score":8.8,"headline":"CSRF Vulnerability in aimhubio/aim","id":"CVE-2024-2196","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":8.6,"headline":"Arbitrary file reading vulnerability in Aim","id":"CVE-2021-43775","kev_date_added":null,"published":"2021-11-23"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-20","vendors":["aimhubio"]},"summary":"An attacker can block the main thread of the AIM tracking server by instantiating a ScheduledStatusReporter, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2024-10110/"}