{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-4452 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-4452 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4452 is a medium-severity vulnerability in n/a, published on 21 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-4452 and fix it if it is affected.\n\nWhat it is: CVE-2005-4452 is a medium-severity vulnerability in n/a, published on 21 Dec 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-4452 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-4452/ (Markdown: https://insights.sbomify.com/CVE-2005-4452/index.md)","id":"CVE-2005-4452","markdown":"https://insights.sbomify.com/CVE-2005-4452/index.md","name":"CVE-2005-4452","record":{"aliases":["GHSA-r2mj-75fm-qmqh"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Information Call Center","requires_auth":"none","summary":"Remote attackers can access the CallCenterData.mdb database via the web root to steal sensitive credentials.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"information_call_center","vendor":"information_call_center"}],"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":"Information Call Center stores the CallCenterData.mdb database under the web root with insufficient access control, which allows remote attackers to obtain sensitive information such as usernames and passwords.","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":"Information disclosure in n/a","id":"CVE-2005-4452","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2005"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2005-4453"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2005-4451"},"products":["n/a"],"published":"2005-12-21","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-08-07","vendors":["n/a"]},"summary":"Remote attackers can access the CallCenterData.mdb database via the web root to steal sensitive credentials.","url":"https://insights.sbomify.com/CVE-2005-4452/"}