{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-0790 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-0790 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-0790 is a medium-severity denial of service vulnerability in n/a, published on 12 Oct 2001. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2001-0790 and fix it if it is affected.\n\nWhat it is: CVE-2001-0790 is a medium-severity denial of service vulnerability in n/a, published on 12 Oct 2001. 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-2001-0790 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2001-0790/ (Markdown: https://insights.sbomify.com/CVE-2001-0790/index.md)","id":"CVE-2001-0790","markdown":"https://insights.sbomify.com/CVE-2001-0790/index.md","name":"CVE-2001-0790","record":{"aliases":["GHSA-87wq-w6qm-2mhm"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Intrusion Detection System","requires_auth":"none","summary":"Remote attackers can cause CPU exhaustion and denial of service in Specter IDS by triggering alert generation via port scans.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"specter_ids","vendor":"specter"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[],"description":"Specter IDS version 4.5 and 5.0 allows a remote attacker to cause a denial of service (CPU exhaustion) via a port scan, which causes the server to consume CPU while preparing alerts.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Denial of service in n/a","id":"CVE-2001-0790","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2001"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2001-0791"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2001-0789"},"products":["n/a"],"published":"2001-10-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can cause CPU exhaustion and denial of service in Specter IDS by triggering alert generation via port scans.","url":"https://insights.sbomify.com/CVE-2001-0790/"}