# CVE-2022-0227: Business Logic Errors in SilverStripe Framework


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 4 Feb 2022
- **Updated:** 4 Apr 2022
- **Also known as:** GHSA-32m2-9f76-4gv8

## What is CVE-2022-0227?

CVE-2022-0227 is a vulnerability in silverstripe/framework, published on 4 Feb 2022. 

### Official description

DO NOT USE THIS CANDIDATE NUMBER. Reason: This CVE has been rejected as it was incorrectly assigned. All references and descriptions in this candidate have been removed to prevent accidental usage

## Which versions are affected by CVE-2022-0227?

2 open source packages ship an affected version, including silverstripe/framework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | All versions | 4.10.1 |
| `silverstripe/framework` | Packagist | All versions | 4.10.1 |

## How do I fix CVE-2022-0227?

Upgrade silverstripe/framework to 4.10.1 or later.

## Is CVE-2022-0227 being exploited?

There is no known exploitation of CVE-2022-0227 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0227 and fix it if it is affected.

What it is: CVE-2022-0227 is a vulnerability in silverstripe/framework, published on 4 Feb 2022. 
Exploitation: There is no known exploitation of CVE-2022-0227 in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected all versions; fixed in 4.10.1
- silverstripe/framework (Packagist): affected all versions; fixed in 4.10.1

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-0227/ (Markdown: https://insights.sbomify.com/CVE-2022-0227/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0227
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0227
- OSV: https://osv.dev/vulnerability/CVE-2022-0227

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-0227/
Summaries are generated and may contain mistakes; the official description above is the record.