{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-6284 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-6284 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-6284 is a high-severity code injection vulnerability in n/a, published on 26 Oct 2013."},"fix_prompt":"Check this codebase for CVE-2013-6284 and fix it if it is affected.\n\nWhat it is: CVE-2013-6284 is a high-severity code injection vulnerability in n/a, published on 26 Oct 2013. \nExploitation: There is no known exploitation of CVE-2013-6284 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-6284/ (Markdown: https://insights.sbomify.com/CVE-2013-6284/index.md)","id":"CVE-2013-6284","markdown":"https://insights.sbomify.com/CVE-2013-6284/index.md","name":"CVE-2013-6284","record":{"aliases":["GHSA-q577-j8xg-55j8"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"SAP ERP Financial Services","requires_auth":"unknown","summary":"Attackers can execute arbitrary code in the SAP ERP Financial Services module via a code injection vulnerability.","user_interaction":"unknown","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"erp_central_component","vendor":"sap"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Unspecified vulnerability in the Statutory Reporting for Insurance (FS_SR) component in the Financial Services module for SAP ERP Central Component (ECC) allows attackers to execute arbitrary code via unspecified vectors, related to a \"code injection vulnerability.\"","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":"Code injection in n/a","id":"CVE-2013-6284","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2013"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2013-6285"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2013-6283"},"products":["n/a"],"published":"2013-10-26","related":[{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2013-3061","kev_date_added":null,"published":"2013-05-01"},{"cvss_score":6,"headline":"Code injection in n/a","id":"CVE-2013-3244","kev_date_added":null,"published":"2013-10-24"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code in the SAP ERP Financial Services module via a code injection vulnerability.","url":"https://insights.sbomify.com/CVE-2013-6284/"}