{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-5220 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2020-5220 is a medium-severity vulnerability in SyliusResourceBundle, published on 27 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-5220 and fix it if it is affected.\n\nWhat it is: CVE-2020-5220 is a medium-severity vulnerability in SyliusResourceBundle, published on 27 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-5220 in the wild and no public exploit code.\n\nAffected product: SyliusResourceBundle. 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-2020-5220/ (Markdown: https://insights.sbomify.com/CVE-2020-5220/index.md)","id":"CVE-2020-5220","markdown":"https://insights.sbomify.com/CVE-2020-5220/index.md","name":"CVE-2020-5220","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Sylius ResourceBundle","requires_auth":"low_privilege","summary":"Attackers can expose sensitive data by manipulating HTTP headers to use unintended serialization groups in Sylius ResourceBundle APIs.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"syliusresourcebundle","vendor":"sylius"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"},{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"Sylius ResourceBundle accepts and uses any serialisation groups to be passed via a HTTP header. This might lead to data exposure by using an unintended serialisation group - for example it could make Shop API use a more permissive group from Admin API. Anyone exposing an API with ResourceBundle's controller is affected. The vulnerable versions are: \u003c1.3 || \u003e=1.3.0 \u003c=1.3.12 || \u003e=1.4.0 \u003c=1.4.5 || \u003e=1.5.0 \u003c=1.5.0 || \u003e=1.6.0 \u003c=1.6.2. The patch is provided for Sylius ResourceBundle 1.3.13, 1.4.6, 1.5.1 and 1.6.3, but not for any versions below 1.3.","ecosystems":[],"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":"Ability to expose data in Sylius by using an unintended serialisation group","id":"CVE-2020-5220","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Directory Traversal (Chroot Escape) vulnerability in uftpd","id":"CVE-2020-5221"},"packages":[],"prev":{"headline":"Remote Code Execution in Angular Expressions","id":"CVE-2020-5219"},"products":["SyliusResourceBundle"],"published":"2020-01-27","related":[{"cvss_score":9.6,"headline":"Remote Code Execution in SyliusResourceBundle","id":"CVE-2020-15146","kev_date_added":null,"published":"2020-08-19"},{"cvss_score":7.7,"headline":"Remote Code Execution in SyliusResourceBundle","id":"CVE-2020-15143","kev_date_added":null,"published":"2020-08-19"}],"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-04","vendors":["Sylius"]},"summary":"Attackers can expose sensitive data by manipulating HTTP headers to use unintended serialization groups in Sylius ResourceBundle APIs.","url":"https://insights.sbomify.com/CVE-2020-5220/"}