{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-5433 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-5433 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-5433 is a medium-severity vulnerability in n/a, published on 12 Aug 2014. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-5433 and fix it if it is affected.\n\nWhat it is: CVE-2013-5433 is a medium-severity vulnerability in n/a, published on 12 Aug 2014. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2013-5433 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-2013-5433/ (Markdown: https://insights.sbomify.com/CVE-2013-5433/index.md)","id":"CVE-2013-5433","markdown":"https://insights.sbomify.com/CVE-2013-5433/index.md","name":"CVE-2013-5433","record":{"aliases":["GHSA-74gp-p893-qhq9"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM InfoSphere Optim","requires_auth":"low_privilege","summary":"Hardcoded database credentials in IBM InfoSphere Optim allow authenticated users to access sensitive information via XML fields.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"infosphere_optim_data_growth_solution_for_siebel_crm","vendor":"ibm"}],"cvss":{"score":4,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-255","name":null}],"description":"The Data Growth Solution for JD Edwards EnterpriseOne in IBM InfoSphere Optim 3.0 through 9.1 has hardcoded database credentials, which allows remote authenticated users to obtain sensitive information by reading an unspecified field in an XML document.","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":"Hardcoded credentials in n/a","id":"CVE-2013-5433","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2013"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2013-5438"},"packages":[],"prev":{"headline":"Open redirect in n/a","id":"CVE-2013-5431"},"products":["n/a"],"published":"2014-08-12","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":"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":"Hardcoded database credentials in IBM InfoSphere Optim allow authenticated users to access sensitive information via XML fields.","url":"https://insights.sbomify.com/CVE-2013-5433/"}