{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-0809 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-0809 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-0809 is a high-severity vulnerability in n/a, published on 20 Mar 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-2005-0809 and fix it if it is affected.\n\nWhat it is: CVE-2005-0809 is a high-severity vulnerability in n/a, published on 20 Mar 2005. 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-0809 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-0809/ (Markdown: https://insights.sbomify.com/CVE-2005-0809/index.md)","id":"CVE-2005-0809","markdown":"https://insights.sbomify.com/CVE-2005-0809/index.md","name":"CVE-2005-0809","record":{"aliases":["GHSA-943v-gjf3-5w35"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"NotifyLink server","requires_auth":"none","summary":"Remote attackers can retrieve AES keys via a direct request and brute-force weak encryption, compromising data confidentiality.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"notifylink","vendor":"notify_technology"}],"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":"NotifyLink, when configured for client key retrieval, allows remote attackers to obtain AES keys via a direct request to /hwp/get.asp, then uses a weak encryption scheme (fixed byte reordering) to protect the key, which allows remote attackers to obtain the key via a brute force attack.","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":"Weak cryptography in n/a","id":"CVE-2005-0809","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2005"},"n_packages":0,"n_references":3,"next":{"headline":"SQL injection in n/a","id":"CVE-2005-0810"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2005-0808"},"products":["n/a"],"published":"2005-03-20","related":[{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-0810","kev_date_added":null,"published":"2005-03-20"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2005-0812","kev_date_added":null,"published":"2005-03-20"},{"cvss_score":4.6,"headline":"Missing authorization in n/a","id":"CVE-2005-0811","kev_date_added":null,"published":"2005-03-20"}],"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-07","vendors":["n/a"]},"summary":"Remote attackers can retrieve AES keys via a direct request and brute-force weak encryption, compromising data confidentiality.","url":"https://insights.sbomify.com/CVE-2005-0809/"}