{"answers":{"affected":"4 open source packages ship an affected version, including silverstripe/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-12849 in the wild and no public exploit code.","fix":"Upgrade silverstripe/cms to a fixed version for your release line: 3.5.5 or 3.6.1.","what":"CVE-2017-12849 is a medium-severity vulnerability in Silverstripe Silverstripe, published on 12 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-12849 and fix it if it is affected.\n\nWhat it is: CVE-2017-12849 is a medium-severity vulnerability in Silverstripe Silverstripe, published on 12 Oct 2017. 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-2017-12849 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/cms (Packagist): affected all versions; fixed in 3.5.5\n- silverstripe/cms (Packagist): affected all versions; fixed in 3.5.5\n- silverstripe/cms (Packagist): affected from 3.6; fixed in 3.6.1\n- silverstripe/cms (Packagist): affected from 3.6; fixed in 3.6.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-12849/ (Markdown: https://insights.sbomify.com/CVE-2017-12849/index.md)","id":"CVE-2017-12849","markdown":"https://insights.sbomify.com/CVE-2017-12849/index.md","name":"CVE-2017-12849","record":{"aliases":["GHSA-fwhr-g5r4-xgxf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SilverStripe CMS","requires_auth":"none","summary":"Remote attackers can enumerate valid users in SilverStripe CMS by analyzing timing discrepancies in login and password reset responses.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"silverstripe","vendor":"silverstripe"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Response discrepancy in the login and password reset forms in SilverStripe CMS before 3.5.5 and 3.6.x before 3.6.1 allows remote attackers to enumerate users via timing attacks.","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 CMS User Enumeration","id":"CVE-2017-12849","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"silverstripe:silverstripe","products":["silverstripe:silverstripe"],"type":"information_disclosure","year":"2017"},"n_packages":4,"n_references":1,"next":{"headline":"Business logic in n/a","id":"CVE-2017-12850"},"packages":[{"ecosystem":"Packagist","fixed":["3.5.5"],"introduced":["0"],"last_affected":[],"package":"silverstripe/cms","purl":null,"source":"GHSA-fwhr-g5r4-xgxf"},{"ecosystem":"Packagist","fixed":["3.5.5"],"introduced":["0"],"last_affected":[],"package":"silverstripe/cms","purl":"pkg:composer/silverstripe/cms","source":"GHSA-fwhr-g5r4-xgxf"},{"ecosystem":"Packagist","fixed":["3.6.1"],"introduced":["3.6"],"last_affected":[],"package":"silverstripe/cms","purl":null,"source":"GHSA-fwhr-g5r4-xgxf"},{"ecosystem":"Packagist","fixed":["3.6.1"],"introduced":["3.6"],"last_affected":[],"package":"silverstripe/cms","purl":"pkg:composer/silverstripe/cms","source":"GHSA-fwhr-g5r4-xgxf"}],"prev":{"headline":"Race condition in n/a","id":"CVE-2017-12847"},"products":["n/a"],"published":"2017-10-12","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":"Remote attackers can enumerate valid users in SilverStripe CMS by analyzing timing discrepancies in login and password reset responses.","url":"https://insights.sbomify.com/CVE-2017-12849/"}