{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-4010 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-4010 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-4010 is a medium-severity vulnerability in n/a, published on 9 Jun 2014. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2014-4010 and fix it if it is affected.\n\nWhat it is: CVE-2014-4010 is a medium-severity vulnerability in n/a, published on 9 Jun 2014. 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-2014-4010 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-4010/ (Markdown: https://insights.sbomify.com/CVE-2014-4010/index.md)","id":"CVE-2014-4010","markdown":"https://insights.sbomify.com/CVE-2014-4010/index.md","name":"CVE-2014-4010","record":{"aliases":["GHSA-jv5x-m6xf-2jp5"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"SAP Transaction Data Pool","requires_auth":"none","summary":"Remote attackers can gain unauthorized access to SAP Transaction Data Pool due to hardcoded credentials.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"transaction_data_pool","vendor":"sap"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-255","name":null}],"description":"SAP Transaction Data Pool has hardcoded credentials, which makes it easier for remote attackers to obtain access via unspecified vectors.","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-2014-4010","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2014"},"n_packages":0,"n_references":4,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2014-4011"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2014-4009"},"products":["n/a"],"published":"2014-06-09","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":"Remote attackers can gain unauthorized access to SAP Transaction Data Pool due to hardcoded credentials.","url":"https://insights.sbomify.com/CVE-2014-4010/"}