{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1619 exists.","fix":"No fix has been published for CVE-2004-1619 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-1619 is a high-severity memory corruption vulnerability in n/a, published on 20 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2004-1619 and fix it if it is affected.\n\nWhat it is: CVE-2004-1619 is a high-severity memory corruption vulnerability in n/a, published on 20 Feb 2005. 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-2004-1619 exists.\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-2004-1619/ (Markdown: https://insights.sbomify.com/CVE-2004-1619/index.md)","id":"CVE-2004-1619","markdown":"https://insights.sbomify.com/CVE-2004-1619/index.md","name":"CVE-2004-1619","record":{"aliases":["GHSA-3v49-5224-w9p6"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Age of Sail II game","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via a buffer overflow triggered by a long nickname in Age of Sail II.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"privateers_bounty_age_of_sail_ii","vendor":"akella"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Buffer overflow in Privateer's Bounty: Age of Sail II allows remote attackers to execute arbitrary code via a long nickname.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2004-03-03","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2004-03-03","kind":"exploitdb","ref":"604","stars":null,"title":"Age of Sail II 1.04.151 - Remote Buffer Overflow"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2004-1619","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2004"},"n_packages":0,"n_references":4,"next":{"headline":"Other in n/a","id":"CVE-2004-1620"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2004-1618"},"products":["n/a"],"published":"2005-02-20","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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code via a buffer overflow triggered by a long nickname in Age of Sail II.","url":"https://insights.sbomify.com/CVE-2004-1619/"}