CVE-2020-5220
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSylius 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: <1.3 || >=1.3.0 <=1.3.12 || >=1.4.0 <=1.4.5 || >=1.5.0 <=1.5.0 || >=1.6.0 <=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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSylius ResourceBundle's API controllers accept serialization groups via HTTP headers without validation, allowing an attacker to pass a more permissive group from a different API context (e.g., Admin API groups in Shop API) to expose sensitive data they should not have access to.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.3.0, <= 1.3.12>= 1.4.0, <= 1.4.5>= 1.6.0, <= 1.6.2= 1.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Sylius ResourceBundle installationCheck your project's composer.json file for "sylius/resource-bundle" in the require section, or inspect the vendor/sylius/resource-bundle directoryAffected if The package is not present in the project dependencies
-
Verify the installed versionRun `composer show sylius/resource-bundle` or check the version listed in composer.lockAffected if The installed version falls within any of these ranges: 1.3.0 to 1.3.12, 1.4.0 to 1.4.5, 1.5.0, or 1.6.0 to 1.6.2
-
Confirm API controllers are in useInspect your routing configuration (config/routes.yaml or annotations) for Sylius ResourceBundle API controller routes such as app_api_* or sylius_api_*Affected if API routes powered by Sylius ResourceBundle controllers are defined and accessible
-
Check for serialization group validationExamine your serialization configuration (serializer mapping files or Serialization groups in resource configuration) for code that validates or whitelists allowed serialization groups based on the API context (Admin vs Shop)Affected if No validation exists on HTTP headers controlling serialization groups, allowing groups from one API context to be used in another
-
Identify exposed API endpointsReview your API endpoint definitions to determine which accept serialization group parameters via HTTP headers (such as serialization_groups or _groups)Affected if API endpoints accept serialization group parameters through HTTP request headers without context-aware restrictions
You are affected if Sylius ResourceBundle version is 1.3.0-1.3.12, 1.4.0-1.4.5, 1.5.0, or 1.6.0-1.6.2 AND your API endpoints accept serialization groups via HTTP headers without validating that the group matches the current API context (Admin or Shop).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Sylius ResourceBundle to version 1.3.13, 1.4.6, 1.5.1, or 1.6.3 (or later) to receive the patch. For versions <1.3, consider implementing custom validation to whitelist allowed serialization groups per endpoint or API context.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5220 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-5220 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data