Skip to content

GHSA-2ccx-2gf3-8xvv CVE-2020-26253

Kirby .dev domains and some reverse proxy setups were treated as local

Medium Packagist
Severity
6.8 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.57%
Chance of exploitation in the next 30 days. Higher than 47.07% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-346 Origin Validation Error
Fix
Available
2 packages have a fixed version

Description

Impact

About our registration block

In order to protect new installations on public servers that don't have an admin account for the Panel yet, we block account registration there by default. This is a security feature, which we implemented years ago in Kirby 2. It helps to avoid that you forget registering your first admin account on a public server.

In this case – without our security block – someone else might theoretically be able to find your site, find out it's running on Kirby, find the Panel and then register the account first. It's an unlikely situation, but it's still a certain risk.

To be able to register the first Panel account on a public server, you have to enforce the installer via a config setting. This helps to push all users to the best practice of registering your first Panel account on your local machine and upload it together with the rest of the site.

The issue

As noted by Jukka Rautanen, this installation block implementation in Kirby versions before 3.3.6 still assumed that .dev domains are local domains, which is no longer true. In the meantime, those domains became publicly available. This means that our installation block is no longer working as expected if you use a .dev domain for your Kirby site.

In fixing this issue, we've also found out that the local installation check may also fail if your site is behind a reverse proxy.

Am I affected?

You are only affected if:

  1. you use a .dev domain or your site is behind a reverse proxy &
  2. you have not yet registered your first Panel account on the public server &
  3. someone finds your site and tries to login at yourdomain.dev/panel before you register your first account.

You are not affected if you have already created one or multiple Panel accounts (no matter if on a .dev domain or behind a reverse proxy).

Patches

The problem has been patched in Kirby 2.5.14 and Kirby 3.3.6. Please update to one of these or a later version to fix the vulnerability.

Note: Kirby 2 reaches end of life on December 31, 2020. We therefore recommend to upgrade your Kirby 2 sites to Kirby 3. If you cannot upgrade, we still recommend to update to Kirby 2.5.14.

Workarounds

Kirby 2 sites on older releases can also be patched by applying the changes from this commit.

Affected versions

Packagist

PackageVulnerableFixed in
getkirby/cms
>= 3.0.0, < 3.3.6
3.3.6
getkirby/panel
< 2.5.14
2.5.14

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

getkirby/cms Packagist → 3.3.6

composer
composer require getkirby/cms:^3.3.6

getkirby/panel Packagist → 2.5.14

composer
composer require getkirby/panel:^2.5.14

Severity breakdown

CVSS 3.1 6.8

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

Weakness

CWE-346: Origin Validation Error

The product does not properly verify that the source of data or communication is valid.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-9vx2-j98c-p72w
Kirby: Access to image files and limited access to JSON files outside of the site root via path traversal in the media handling
High Also affects getkirby/cms
GHSA-6j4c-mgqr-qv76
Kirby: Access to image files outside of the site root via path traversal in the media handling
Medium Also affects getkirby/cms
GHSA-67mx-6wf2-92xp
Kirby: File upload permissions are not checked during processing of chunk data
High Also affects getkirby/cms
GHSA-rf2p-vh74-7vvh
Kirby: System path exposure from error messages in the REST API
Medium Also affects getkirby/cms
GHSA-r3w8-2c5r-h9j9
Kirby: `pages.access` permission is not checked in the `site/find` REST API route
High Also affects getkirby/cms
GHSA-89cp-7p28-jffg
Kirby: Access to files of top-level drafts is not protected by permissions
Medium Also affects getkirby/cms
GHSA-whxw-24jc-cwmv
Kirby: External Initialization of the Panel on reverse proxy setups with the `Forwarded` header
Critical Also affects getkirby/cms
GHSA-wr9h-4r83-f4v6
Kirby: Cross-site scripting (XSS) from incomplete HTML/XML sanitization in `Dom::sanitize()`
High Also affects getkirby/cms
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor