{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1855 exists.","fix":"No fix has been published for CVE-2004-1855 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-1855 is a medium-severity vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2004-1855 and fix it if it is affected.\n\nWhat it is: CVE-2004-1855 is a medium-severity vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1855 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-1855/ (Markdown: https://insights.sbomify.com/CVE-2004-1855/index.md)","id":"CVE-2004-1855","markdown":"https://insights.sbomify.com/CVE-2004-1855/index.md","name":"CVE-2004-1855","record":{"aliases":["GHSA-9j26-f84r-gm28"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MMORPG game client","requires_auth":"none","summary":"Remote attackers can intercept sensitive data via man-in-the-middle attacks due to unsigned RSA public keys in the game client.","user_interaction":"required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dark_age_of_camelot","vendor":"mythic_entertainment"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"Dark Age of Camelot before 1.68 live patch does not sign the RSA public key, which could allow remote malicious servers to gain sensitive information via a man-in-the-middle attack.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2004-03-23","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2004-03-23","kind":"exploitdb","ref":"23873","stars":null,"title":"Mythic Entertainment Dark Age of Camelot 1.6x - Encryption Key Signing"}],"tier":"weaponised"},"has_fix":null,"headline":"Weak cryptography in n/a","id":"CVE-2004-1855","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2004"},"n_packages":0,"n_references":5,"next":{"headline":"File upload in n/a","id":"CVE-2004-1856"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2004-1854"},"products":["n/a"],"published":"2005-05-10","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 intercept sensitive data via man-in-the-middle attacks due to unsigned RSA public keys in the game client.","url":"https://insights.sbomify.com/CVE-2004-1855/"}