Past Incidents

We will update GitLab to version 11.2.3.

Start maintenance window: 04/09/2018 00:00 CEST
Stop maintenance window: 04/09/2018 02:00 CEST

We introduced options to define global nginx configurations on server and http level. See the documentation for details.

Closes #385

Several issues have been discovered in the MariaDB database server. The vulnerabilities are addressed by upgrading MariaDB to the new upstream version 10.0.36. Please see the MariaDB 10.0 Release Notes for further details: https://mariadb.com/kb/en/mariadb/mariadb-10036-release-notes/

We have updated mariadb to the latest version.

• mariadb-client/oldstable 10.0.36-0+deb8u1 all [upgradable from: 10.0.35-0+deb8u1]
• mariadb-client-10.0/oldstable 10.0.36-0+deb8u1 amd64 [upgradable from: 10.0.35-0+deb8u1]
• mariadb-client-core-10.0/oldstable 10.0.36-0+deb8u1 amd64 [upgradable from: 10.0.35-0+deb8u1]
• mariadb-common/oldstable 10.0.36-0+deb8u1 all [upgradable from: 10.0.35-0+deb8u1]
• mariadb-server/oldstable 10.0.36-0+deb8u1 all [upgradable from: 10.0.35-0+deb8u1]
• mariadb-server-10.0/oldstable 10.0.36-0+deb8u1 amd64 [upgradable from: 10.0.35-0+deb8u1]
• mariadb-server-core-10.0/oldstable 10.0.36-0+deb8u1 amd64 [upgradable from: 10.0.35-0+deb8u1]

Two security issues have been discovered in the Tomcat servlet and JSP engine. [DLA 1491-1]

We have updated tomcat8 to the latest version.

• libtomcat8-java/oldstable 8.0.14-1+deb8u13 all [upgradable from: 8.0.14-1+deb8u12]
• tomcat8/oldstable 8.0.14-1+deb8u13 all [upgradable from: 8.0.14-1+deb8u12]
• tomcat8-admin/oldstable 8.0.14-1+deb8u13 all [upgradable from: 8.0.14-1+deb8u12]
• tomcat8-common/oldstable 8.0.14-1+deb8u13 all [upgradable from: 8.0.14-1+deb8u12]

We have updated Matomo to the latest version.

• Version: Matomo 3.6.0
• Changelog: https://matomo.org/changelog/matomo-3-6-0/

Two vulnerabilities have been discovered in php5 [DLA 1490-1]

We have updated php5 to the latest version.

• php5-cli/oldstable 5.6.37+dfsg-0+deb8u1 amd64 [upgradable from: 5.6.36+dfsg-0+deb8u1]
• php5-common/oldstable 5.6.37+dfsg-0+deb8u1 amd64 [upgradable from: 5.6.36+dfsg-0+deb8u1]
• php5-curl/oldstable 5.6.37+dfsg-0+deb8u1 amd64 [upgradable from: 5.6.36+dfsg-0+deb8u1]
• php5-fpm/oldstable 5.6.37+dfsg-0+deb8u1 amd64 [upgradable from: 5.6.36+dfsg-0+deb8u1]
• php5-gd/oldstable 5.6.37+dfsg-0+deb8u1 amd64 [upgradable from: 5.6.36+dfsg-0+deb8u1]
• php5-imap/oldstable 5.6.37+dfsg-0+deb8u1 amd64 [upgradable from: 5.6.36+dfsg-0+deb8u1]
• php5-mysql/oldstable 5.6.37+dfsg-0+deb8u1 amd64 [upgradable from: 5.6.36+dfsg-0+deb8u1]
• php5-readline/oldstable 5.6.37+dfsg-0+deb8u1 amd64 [upgradable from: 5.6.36+dfsg-0+deb8u1]

Features

• Added new website types for generation 6 Servers
• Display IPv6 address in the servers network interfaces tab
• Remove ssh key from all servers and websites of a customer when user is removed from that customer
• Display Balance on the monthly invoice

Bugs

• ID's in HTML can not start with a number
• Different structure of the network interfaces for hiera
• Forbid test as website name
• Better parsing of EPP messages

To deny access to certain private files and directories like .git, we used some custom locations defined on each website. Those locations where defined directly within the vhost configuration, but after the custom configuration include to allow overrides for certain setups.

Due to the predefined nginx location block selection order, it is possible to override our security locations by mistake, especially when defining a own location for everything (like location ~* ^/), which will disable processing of any following regex locations used in our security configuration.

To avoid misconfigurations leading to open access to private files, we took the following precautions:

• security locations moved into their own file /etc/nginx/custom/security.conf, which can be included in custom locations as well
• warning to the corresponding documentation
• automatic check to find custom locations without included security configuration
• automatic check to scan for secret files over HTTP

Please include the new security configuration within affected locations like described within our updated documentation. Additionally, we will contact all customer with affected configurations over the next few days.

Closes #386