{"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-2019-19326 in the wild and no public exploit code.","fix":"Upgrade silverstripe/framework to a fixed version for your release line: 3.7.5, 4.4.7 or 4.5.4.","what":"CVE-2019-19326 is a medium-severity vulnerability in Silverstripe Silverstripe, published on 15 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-19326 and fix it if it is affected.\n\nWhat it is: CVE-2019-19326 is a medium-severity vulnerability in Silverstripe Silverstripe, published on 15 Jul 2020. 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-2019-19326 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/framework (Packagist): affected from 3.0.0; fixed in 3.7.5\n- silverstripe/framework (Packagist): affected from 3.0.0; fixed in 3.7.5\n- silverstripe/framework (Packagist): affected from 4.0.0; fixed in 4.4.7\n- silverstripe/framework (Packagist): affected from 4.0.0; fixed in 4.4.7\n- silverstripe/framework (Packagist): affected from 4.5.0; fixed in 4.5.4\n- silverstripe/framework (Packagist): affected from 4.5.0; fixed in 4.5.4\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-2019-19326/ (Markdown: https://insights.sbomify.com/CVE-2019-19326/index.md)","id":"CVE-2019-19326","markdown":"https://insights.sbomify.com/CVE-2019-19326/index.md","name":"CVE-2019-19326","record":{"aliases":["GHSA-q9ff-3q93-fm8m"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Silverstripe CMS","requires_auth":"none","summary":"Attackers can poison web caches in Silverstripe CMS by manipulating specific headers, causing malicious responses to be served to other users.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"silverstripe","vendor":"silverstripe"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"Silverstripe CMS sites through 4.4.4 which have opted into HTTP Cache Headers on responses served by the framework's HTTP layer can be vulnerable to web cache poisoning. Through modifying the X-Original-Url and X-HTTP-Method-Override headers, responses with malicious HTTP headers can return unexpected responses to other consumers of this cached response. Most other headers associated with web cache poisoning are already disabled through request hostname forgery whitelists.","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 Web Cache Poisoning through HTTPRequestBuilder","id":"CVE-2019-19326","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"silverstripe:silverstripe","products":["silverstripe:silverstripe"],"type":"other","year":"2019"},"n_packages":6,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-19327"},"packages":[{"ecosystem":"Packagist","fixed":["3.7.5"],"introduced":["3.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-q9ff-3q93-fm8m"},{"ecosystem":"Packagist","fixed":["3.7.5"],"introduced":["3.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-q9ff-3q93-fm8m"},{"ecosystem":"Packagist","fixed":["4.4.7"],"introduced":["4.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-q9ff-3q93-fm8m"},{"ecosystem":"Packagist","fixed":["4.4.7"],"introduced":["4.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-q9ff-3q93-fm8m"},{"ecosystem":"Packagist","fixed":["4.5.4"],"introduced":["4.5.0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-q9ff-3q93-fm8m"},{"ecosystem":"Packagist","fixed":["4.5.4"],"introduced":["4.5.0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-q9ff-3q93-fm8m"}],"prev":{"headline":"Reflected XSS in SilverStripe","id":"CVE-2019-19325"},"products":["n/a"],"published":"2020-07-15","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 poison web caches in Silverstripe CMS by manipulating specific headers, causing malicious responses to be served to other users.","url":"https://insights.sbomify.com/CVE-2019-19326/"}