{"answers":{"affected":"6 open source packages ship an affected version, including silverstripe/framework. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18049 in the wild and no public exploit code.","fix":"Upgrade silverstripe/framework to a fixed version for your release line: 3.5.6, 3.6.3 or 4.0.1.","what":"CVE-2017-18049 is a medium-severity code injection vulnerability in Silverstripe Silverstripe, published on 23 Jan 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-18049 and fix it if it is affected.\n\nWhat it is: CVE-2017-18049 is a medium-severity code injection vulnerability in Silverstripe Silverstripe, published on 23 Jan 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-18049 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/framework (Packagist): affected all versions; fixed in 3.5.6\n- silverstripe/framework (Packagist): affected all versions; fixed in 3.5.6\n- silverstripe/framework (Packagist): affected from 3.6.0; fixed in 3.6.3\n- silverstripe/framework (Packagist): affected from 3.6.0; fixed in 3.6.3\n- silverstripe/framework (Packagist): affected from 4.0.0; fixed in 4.0.1\n- silverstripe/framework (Packagist): affected from 4.0.0; fixed in 4.0.1\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-2017-18049/ (Markdown: https://insights.sbomify.com/CVE-2017-18049/index.md)","id":"CVE-2017-18049","markdown":"https://insights.sbomify.com/CVE-2017-18049/index.md","name":"CVE-2017-18049","record":{"aliases":["GHSA-2jvj-mhf2-g99w"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SilverStripe CMS","requires_auth":"none","summary":"Attackers can inject malicious macros or scripts into CSV exports, leading to code execution when victims import the file into applications like Microsoft Excel.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"silverstripe","vendor":"silverstripe"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"In the CSV export feature of SilverStripe before 3.5.6, 3.6.x before 3.6.3, and 4.x before 4.0.1, it's possible for the output to contain macros and scripts, which may be executed if imported without sanitization into common software (including Microsoft Excel). For example, the CSV data may contain untrusted user input from the \"First Name\" field of a user's /myprofile page.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"SilverStripe CSV Excel Macro Injection","id":"CVE-2017-18049","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"silverstripe:silverstripe","products":["silverstripe:silverstripe"],"type":"code_injection","year":"2017"},"n_packages":6,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2017-18050"},"packages":[{"ecosystem":"Packagist","fixed":["3.5.6"],"introduced":["0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-2jvj-mhf2-g99w"},{"ecosystem":"Packagist","fixed":["3.5.6"],"introduced":["0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-2jvj-mhf2-g99w"},{"ecosystem":"Packagist","fixed":["3.6.3"],"introduced":["3.6.0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-2jvj-mhf2-g99w"},{"ecosystem":"Packagist","fixed":["3.6.3"],"introduced":["3.6.0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-2jvj-mhf2-g99w"},{"ecosystem":"Packagist","fixed":["4.0.1"],"introduced":["4.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-2jvj-mhf2-g99w"},{"ecosystem":"Packagist","fixed":["4.0.1"],"introduced":["4.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-2jvj-mhf2-g99w"}],"prev":{"headline":"File upload in n/a","id":"CVE-2017-18048"},"products":["n/a"],"published":"2018-01-23","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2007-2321","kev_date_added":null,"published":"2007-04-27"},{"cvss_score":9.8,"headline":"Missing warning can lead to unauthenticated admin access in SilverStripe","id":"CVE-2019-12204","kev_date_added":null,"published":"2019-09-25"},{"cvss_score":9.8,"headline":"Silverstripe Framework SQLi Vulnerability","id":"CVE-2019-5715","kev_date_added":null,"published":"2019-04-11"},{"cvss_score":8.8,"headline":"Silverstripe CSRF Protection Bypass via GraphQL","id":"CVE-2019-12437","kev_date_added":null,"published":"2020-02-19"},{"cvss_score":7.5,"headline":"Silverstripe CMS information disclosure","id":"CVE-2020-6164","kev_date_added":null,"published":"2020-07-15"},{"cvss_score":7.5,"headline":"SilverStripe Folders migrated from 3.x may be unsafe to upload to","id":"CVE-2020-9280","kev_date_added":null,"published":"2020-04-15"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2011-4960","kev_date_added":null,"published":"2012-09-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-05","vendors":["n/a"]},"summary":"Attackers can inject malicious macros or scripts into CSV exports, leading to code execution when victims import the file into applications like Microsoft Excel.","url":"https://insights.sbomify.com/CVE-2017-18049/"}