{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2012-3331 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2012-3331 yet. Limit exposure of the affected software until one is available.","what":"CVE-2012-3331 is a medium-severity vulnerability in n/a, published on 8 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2012-3331 and fix it if it is affected.\n\nWhat it is: CVE-2012-3331 is a medium-severity vulnerability in n/a, published on 8 Feb 2018. 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-2012-3331 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-2012-3331/ (Markdown: https://insights.sbomify.com/CVE-2012-3331/index.md)","id":"CVE-2012-3331","markdown":"https://insights.sbomify.com/CVE-2012-3331/index.md","name":"CVE-2012-3331","record":{"aliases":["GHSA-hwx7-hqj6-jp57"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Sametime","requires_auth":"none","summary":"Remote attackers can access sensitive data from the Sametime Log database by directly requesting a specific file, requiring IBM Sametime administrators to apply patches.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"sametime","vendor":"ibm"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"IBM Sametime allows remote attackers to obtain sensitive information from the Sametime Log database via a direct request to STLOG.NSF. IBM X-Force ID: 78048.","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-2012-3331","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2012"},"n_packages":0,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2012-3333"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2012-3330"},"products":["n/a"],"published":"2018-02-08","related":[{"cvss_score":7.8,"headline":"Information disclosure in Sametime","id":"CVE-2016-2972","kev_date_added":null,"published":"2017-08-29"},{"cvss_score":7.5,"headline":"Open redirect in n/a","id":"CVE-2013-3983","kev_date_added":null,"published":"2014-02-13"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2013-6742","kev_date_added":null,"published":"2014-02-13"},{"cvss_score":6.8,"headline":"Other in n/a","id":"CVE-2013-3988","kev_date_added":null,"published":"2014-02-13"},{"cvss_score":6.5,"headline":"Cross-site request forgery in Sametime","id":"CVE-2016-0355","kev_date_added":null,"published":"2017-08-29"},{"cvss_score":6.5,"headline":"Cross-site request forgery in Sametime","id":"CVE-2016-0356","kev_date_added":null,"published":"2017-08-29"},{"cvss_score":6.5,"headline":"Cross-site request forgery in Sametime","id":"CVE-2016-2965","kev_date_added":null,"published":"2017-08-29"}],"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-06","vendors":["n/a"]},"summary":"Remote attackers can access sensitive data from the Sametime Log database by directly requesting a specific file, requiring IBM Sametime administrators to apply patches.","url":"https://insights.sbomify.com/CVE-2012-3331/"}