Anyone (Strapi developers, users, plugins) can make every attribute of a Content-Type public without knowing it.
When dealing with content-types inside a Strapi instance, we can extend those using the appropriate container:
strapi.container.get('content-types').extend(contentTypeUID, (contentType) => newContentType);
The vulnerability only affects the handling of content types by Strapi, not the actual content types themselves. Users can use plugins or modify their own content types without realizing that the privateAttributes getter is being removed, which can result in any attribute becoming public. This can lead to sensitive information being exposed or the entire system being taken control of by an attacker(having access to password hashes).
Extend any content type on runtime (like in the bootstrap functions) and do a copy of the content-type object.
strapi.container.get('content-types').extend(contentTypeUID, (contentType) => {
const newCT = { ... contentType, attributes: { ...contentType.attributes, newAttr: {} } };
return newCT;
});
This will have as effect to remove the getter and as we rely on it in sanitization, every attributes will be considered as public.
Everyone can be impacted. Depending on how people are using/extending content-types. If the users are mutating the content-type, they will not be affected.
| Score | Percentile |
|---|---|
| 0.08% | 22.52% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 4.8 | 3.1 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-chmr-rg2f-9jmf ↗ |
| CVE | CVE-2023-34093 ↗ |
| CWE id | Name |
|---|---|
| CWE-200 | Exposure of Sensitive Information to an Unauthorized Actor |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| npm | @strapi/strapi | < 4.10.8 | 4.10.8 | — |
| npm | @strapi/utils | < 4.10.8 | 4.10.8 | — |
| npm | @strapi/database | < 4.10.8 | 4.10.8 | — |