{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4145 exists.","fix":"No fix has been published for CVE-2005-4145 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4145 is a medium-severity vulnerability in n/a, published on 10 Dec 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-4145 and fix it if it is affected.\n\nWhat it is: CVE-2005-4145 is a medium-severity vulnerability in n/a, published on 10 Dec 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-2005-4145 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-2005-4145/ (Markdown: https://insights.sbomify.com/CVE-2005-4145/index.md)","id":"CVE-2005-4145","markdown":"https://insights.sbomify.com/CVE-2005-4145/index.md","name":"CVE-2005-4145","record":{"aliases":["GHSA-857q-ccvw-898p"],"analysis":{"component_type":"database","fix_type":"configuration_change","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Lyris ListManager MSDE","requires_auth":"none","summary":"Remote attackers can brute-force the weak default database password to gain unauthorized access to the Lyris ListManager MSDE database.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"listmanager","vendor":"lyris_technologies_inc"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"The MSDE version of Lyris ListManager 5.0 through 8.9b configures the sa account in the database to use a password with a small search space (\"lyris\" and up to 5 digits, possibly from the process ID), which allows remote attackers to gain access via a brute force attack.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2005-12-08","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2005-12-08","kind":"metasploit","ref":"exploit/windows/mssql/lyris_listmanager_weak_pass","stars":null,"title":"Lyris ListManager MSDE Weak sa Password"},{"date":"2010-09-20","kind":"exploitdb","ref":"16397","stars":null,"title":"Lyris ListManager - MSDE Weak sa Password (Metasploit)"}],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2005-4145","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2005"},"n_packages":0,"n_references":6,"next":{"headline":"Information disclosure in n/a","id":"CVE-2005-4146"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2005-4144"},"products":["n/a"],"published":"2005-12-10","related":[{"cvss_score":7.5,"headline":"Command injection in n/a","id":"CVE-2005-4142","kev_date_added":null,"published":"2005-12-10"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2005-4147","kev_date_added":null,"published":"2005-12-10"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2005-4146","kev_date_added":null,"published":"2005-12-10"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2005-4148","kev_date_added":null,"published":"2005-12-10"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2005-4149","kev_date_added":null,"published":"2005-12-10"}],"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":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can brute-force the weak default database password to gain unauthorized access to the Lyris ListManager MSDE database.","url":"https://insights.sbomify.com/CVE-2005-4145/"}