{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2008-4807 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2008-4807 yet. Limit exposure of the affected software until one is available.","what":"CVE-2008-4807 is a low-severity vulnerability in n/a, published on 31 Oct 2008. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2008-4807 and fix it if it is affected.\n\nWhat it is: CVE-2008-4807 is a low-severity vulnerability in n/a, published on 31 Oct 2008. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2008-4807 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-2008-4807/ (Markdown: https://insights.sbomify.com/CVE-2008-4807/index.md)","id":"CVE-2008-4807","markdown":"https://insights.sbomify.com/CVE-2008-4807/index.md","name":"CVE-2008-4807","record":{"aliases":["GHSA-wxhf-vrqv-h872"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM Lotus Connections","requires_auth":"none","summary":"Local attackers can read the administrative password from the trace.log file in IBM Lotus Connections, leading to sensitive information disclosure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lotus_connections","vendor":"ibm"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-255","name":null}],"description":"IBM Lotus Connections 2.x before 2.0.1 stores the password for the administrative user in the trace.log file, which allows local users to obtain sensitive information by reading this file.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.","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-2008-4807","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2008"},"n_packages":0,"n_references":4,"next":{"headline":"Information disclosure in n/a","id":"CVE-2008-4808"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2008-4806"},"products":["n/a"],"published":"2008-10-31","related":[{"cvss_score":10,"headline":"Multiple unspecified vulnerabilities in the Profiles search pages in IBM Lotus Connections 2.x before 2.0.1 have unknown impact and attack v","id":"CVE-2008-4809","kev_date_added":null,"published":"2008-10-31"},{"cvss_score":7.6,"headline":"Security feature bypass in n/a","id":"CVE-2010-2279","kev_date_added":null,"published":"2010-06-14"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2008-4806","kev_date_added":null,"published":"2008-10-31"},{"cvss_score":6.8,"headline":"Missing authorization in n/a","id":"CVE-2011-1032","kev_date_added":null,"published":"2011-02-14"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2008-4808","kev_date_added":null,"published":"2008-10-31"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2013-0503","kev_date_added":null,"published":"2013-04-23"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2011-1030","kev_date_added":null,"published":"2011-02-14"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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":"Local attackers can read the administrative password from the trace.log file in IBM Lotus Connections, leading to sensitive information disclosure.","url":"https://insights.sbomify.com/CVE-2008-4807/"}