{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2014-0894 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-0894 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-0894 is a low-severity vulnerability in n/a, published on 7 Jul 2014."},"fix_prompt":"Check this codebase for CVE-2014-0894 and fix it if it is affected.\n\nWhat it is: CVE-2014-0894 is a low-severity vulnerability in n/a, published on 7 Jul 2014. \nExploitation: There is no known exploitation of CVE-2014-0894 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-2014-0894/ (Markdown: https://insights.sbomify.com/CVE-2014-0894/index.md)","id":"CVE-2014-0894","markdown":"https://insights.sbomify.com/CVE-2014-0894/index.md","name":"CVE-2014-0894","record":{"aliases":["GHSA-wx6m-r4jc-mfvw"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"unknown","non_default_config":false,"product_category":"IBM Algo Credit Limits","requires_auth":"none","summary":"Attackers can discover database credentials by reading specific fields in an XML document within IBM Algo Credit Limits.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"algo_credit_limits","vendor":"ibm"},{"product":"algorithmics","vendor":"ibm"}],"cvss":{"score":3.5,"severity":"low","source":"nvd","vector":"AV:N/AC:M/Au:S/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"RICOS in IBM Algo Credit Limits (aka ACLM) 4.5.0 through 4.7.0 before 4.7.0.03 FP5 in IBM Algorithmics allows context-dependent attackers to discover database credentials by reading the DbUser and DbPass fields in an XML document.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2014-07-01","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2014-07-01","kind":"exploitdb","ref":"33942","stars":null,"title":"IBM Algorithmics RICOS 4.5.0 \u003c 4.7.0 - Multiple Vulnerabilities"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2014-0894","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2014"},"n_packages":0,"n_references":7,"next":{"headline":"Memory corruption in n/a","id":"CVE-2014-0895"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2014-0893"},"products":["n/a"],"published":"2014-07-07","related":[{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2014-0864","kev_date_added":null,"published":"2014-07-07"},{"cvss_score":5.8,"headline":"Other in n/a","id":"CVE-2014-0867","kev_date_added":null,"published":"2014-07-07"},{"cvss_score":4.9,"headline":"Deserialization in n/a","id":"CVE-2014-0865","kev_date_added":null,"published":"2014-07-07"},{"cvss_score":4.9,"headline":"Business logic in n/a","id":"CVE-2014-0868","kev_date_added":null,"published":"2014-07-07"},{"cvss_score":4.3,"headline":"Information disclosure in n/a","id":"CVE-2014-0866","kev_date_added":null,"published":"2014-07-07"},{"cvss_score":4.3,"headline":"Weak cryptography in n/a","id":"CVE-2014-0869","kev_date_added":null,"published":"2014-07-07"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2014-0870","kev_date_added":null,"published":"2014-07-07"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Attackers can discover database credentials by reading specific fields in an XML document within IBM Algo Credit Limits.","url":"https://insights.sbomify.com/CVE-2014-0894/"}