Security
Headlines
HeadlinesLatestCVEs

Headline

CVE-2023-40180: [CVE-2023-40180] Add protection against recursive queries (#558) · silverstripe/silverstripe-graphql@f6d5976

silverstripe-graphql is a package which serves Silverstripe data in GraphQL representations. 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. This issue has been addressed in versions 3.8.2, 4.1.3, 4.2.5, 4.3.4, and 5.0.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.

CVE
#vulnerability#web#mac#ddos#dos

Expand Up @@ -5,14 +5,20 @@
use GraphQL\Error\Error; use GraphQL\Error\SyntaxError; use GraphQL\Error\UserError; use GraphQL\Executor\ExecutionResult; use GraphQL\GraphQL; use GraphQL\Language\AST\DocumentNode; use GraphQL\Language\AST\NodeKind; use GraphQL\Language\Lexer; use GraphQL\Language\Parser; use GraphQL\Language\Source; use GraphQL\Language\SourceLocation; use GraphQL\Language\Token; use GraphQL\Type\Schema as GraphQLSchema; use GraphQL\Validator\DocumentValidator; use GraphQL\Validator\Rules\QueryComplexity; use GraphQL\Validator\Rules\QueryDepth; use SilverStripe\Control\Director; use SilverStripe\Core\Config\Configurable; use SilverStripe\Core\Extensible; Expand All @@ -24,6 +30,7 @@ use SilverStripe\GraphQL\PersistedQuery\PersistedQueryProvider; use SilverStripe\GraphQL\Schema\Interfaces\ContextProvider; use SilverStripe\GraphQL\Schema\Schema; use SilverStripe\GraphQL\Schema\SchemaConfig; use SilverStripe\ORM\ValidationException;
/** Expand Down Expand Up @@ -99,12 +106,61 @@ public function queryAndReturnResult(GraphQLSchema $schema, $query, ?array $vars } $context = $this->getContext(); $last = function ($schema, $query, $context, $vars) { return GraphQL::executeQuery($schema, $query, null, $context, $vars); if (is_string($query)) { $this->validateQueryBeforeParsing($query, $context); }
$validationRules = DocumentValidator::allRules(); if (isset($context[SchemaConfigProvider::KEY])) { /** @var SchemaConfig $config */ $config = $context[SchemaConfigProvider::KEY]; $maxDepth = $config->get(‘max_query_depth’); $maxComplexity = $config->get(‘max_query_complexity’); if ($maxDepth) { $validationRules[QueryDepth::class] = new QueryDepth($maxDepth); } if ($maxComplexity) { $validationRules[QueryComplexity::class] = new QueryComplexity($maxComplexity); } } return GraphQL::executeQuery($schema, $query, null, $context, $vars, null, null, $validationRules); };
return $this->callMiddleware($schema, $query, $context, $vars ?? [], $last); }
/** * Validate a query before parsing it in case there are issues we can catch early. */ public function validateQueryBeforeParsing(string $query, array $context): void { if (!isset($context[SchemaConfigProvider::KEY])) { return; }
/** @var SchemaConfig $config */ $config = $context[SchemaConfigProvider::KEY]; $maxNodes = $config->get(‘max_query_nodes’); if (!$maxNodes) { return; }
$lexer = new Lexer(new Source($query)); $numNodes = 0;
// Check how many nodes there are in this query do { $next = $lexer->advance(); if ($next->kind === Token::NAME) { $numNodes++; } } while ($next->kind !== Token::EOF && $numNodes <= $maxNodes);
// Throw a UserError if there are too many nodes if ($numNodes > $maxNodes) { throw new UserError(“GraphQL query body must not be longer than $maxNodes nodes.”); } }
/** * get query from persisted id, return null if not found Expand Down

Related news

GHSA-v23w-pppm-jh66: Silverstripe GraphQL has DDOS Vulnerability due to lack of protection against recursive queries

### 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](https://github.com/silverstripe/silverstripe-graphql/releases/tag/3.8.2), [4.1.3](https://github.com/silverstripe/silverstripe-graphql/releases/tag/4.1.3), [4.2.5](https://github.com/silverstripe/silverstripe-graphql/releases/tag/4.2.5), [4.3.4](https://github.com/silverstripe/silverstripe-graphql/releases/...

CVE: Latest News

CVE-2023-50976: Transactions API Authorization by oleiman · Pull Request #14969 · redpanda-data/redpanda
CVE-2023-6905
CVE-2023-6903
CVE-2023-6904
CVE-2023-3907