{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2005-4716 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-4716 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4716 is a medium-severity denial of service vulnerability in n/a, published on 15 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-4716 and fix it if it is affected.\n\nWhat it is: CVE-2005-4716 is a medium-severity denial of service vulnerability in n/a, published on 15 Feb 2006. 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-2005-4716 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-2005-4716/ (Markdown: https://insights.sbomify.com/CVE-2005-4716/index.md)","id":"CVE-2005-4716","markdown":"https://insights.sbomify.com/CVE-2005-4716/index.md","name":"CVE-2005-4716","record":{"aliases":["GHSA-qw54-4wxm-x2wr"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Hitachi TP1 Server","requires_auth":"none","summary":"Remote attackers can cause denial of service in Hitachi TP1/Server Base and TP1/NET/Library 2 on IBM AIX by sending invalid data to specific ports.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"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":"Hitachi TP1/Server Base and TP1/NET/Library 2 on IBM AIX allow remote attackers to (1) cause a denial of service (OpenTP1 system outage) via invalid data to a port used by a system-server process, and (2) cause a denial of service (process failure) via invalid data to a port used by any of certain other processes.","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-2005-4716","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2005"},"n_packages":0,"n_references":3,"next":{"headline":"Null dereference in n/a","id":"CVE-2005-4717"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2005-4715"},"products":["n/a"],"published":"2006-02-15","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-09-16","vendors":["n/a"]},"summary":"Remote attackers can cause denial of service in Hitachi TP1/Server Base and TP1/NET/Library 2 on IBM AIX by sending invalid data to specific ports.","url":"https://insights.sbomify.com/CVE-2005-4716/"}