silverstripe/graphql

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

An attacker could use a specially crafted graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed and particularly large/complex graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this will likely further mitigate the risk.

Upgrade to silverstripe/graphql 4.2.3 or 4.1.2 or above to remedy the vulnerability.

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

An attacker could use a specially crafted graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed and particularly large/complex graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this will likely further mitigate the risk.

Upgrade to silverstripe/graphql 4.2.3 or 4.1.2 or above to remedy the vulnerability.

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Impact

canView permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page.

Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se.

This has been fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.

This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.

You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.

Note that this vulnerability does not affect version 3.x.

Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson

References

https://www.silverstripe.org/download/security-releases/CVE-2023-44401

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

• CVE-2023-40180 on silverstripe.org
• Documentation about protection against recursive or complex queries for silverstripe/graphql 4.x/5.x
• Documentation about protection against recursive or complex queries for silverstripe/graphql 3.x

Reported by

Jason Nguyen from phew (https://phew.co.nz/)