CVE-2020-6165: Silverstripe has Incorrect Default Permissions

CVE-2020-6165 · Severity: low · CVSS 3.1 · Published 2022-05-24

Silverstripe has Incorrect Default Permissions

Technologies: silverstripe/graphql (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2020-6165 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-6165 being exploited in the wild.
How severe is CVE-2020-6165?
Low severity, with a CVSS score of 3.1, published 24 May 2022.
Which products and versions are affected?
silverstripe/graphql (Packagist) ECOSYSTEM:introduced=3.2.0,fixed=3.2.4; silverstripe/recipe-cms (Packagist) ECOSYSTEM:introduced=4.5.0,fixed=4.5.3.
Is there a fix for CVE-2020-6165?
Yes. silverstripe/graphql (Packagist): upgrade to 3.2.4 or later; silverstripe/recipe-cms (Packagist): upgrade to 4.5.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-6165?
Check whether you run silverstripe/graphql (Packagist) or silverstripe/recipe-cms (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • silverstripe/graphql (Packagist): upgrade to 3.2.4 or later
    composer require silverstripe/graphql:^3.2.4
  • silverstripe/recipe-cms (Packagist): upgrade to 4.5.3 or later
    composer require silverstripe/recipe-cms:^4.5.3

Affected products

  • silverstripe/graphql (Packagist) ECOSYSTEM:introduced=3.2.0,fixed=3.2.4
  • silverstripe/recipe-cms (Packagist) ECOSYSTEM:introduced=4.5.0,fixed=4.5.3

Identifiers

  • CVE-2020-6165
  • GHSA-589q-75r3-mfq4

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.