- template for CCSAs, which prioritizes information relevant to an
operator
- example CCSA, borrowed from the pad we used during the first PHP
bug: https://pad.utaw.tech/kECUHWGoTRO76jVPPxQYOg)
- a couple links to the advisory
| [4get](https://git.coopcloud.tech/coop-cloud/4get) | Pending | 0.7.4+1.0.62 has been deployed. It's is unclear if it has [the fix](https://git.lolcat.ca/lolcat/4get/issues/99). Needs to be confirmed. |
| [akaunting](https://git.coopcloud.tech/coop-cloud/akaunting) | Unmaintained | There appears to be no owner to fix this. |
| [civicrm-backdrop](https://git.coopcloud.tech/coop-cloud/civicrm-backdrop) | Unmaintained | No updates in 2 years |
| [civicrm-wordpress](https://git.coopcloud.tech/coop-cloud/civicrm-wordpress) | Pending | No update since last year |
| [lichen-markdown](https://git.coopcloud.tech/coop-cloud/lichen-markdown) | Not Affected | Lichen is uses PHP to generate static pages, and thus is not affected by the vulnerabilites. |
| [rallly](https://git.coopcloud.tech/coop-cloud/rallly) | Not Affected | Rallley uses a PHP desrialization library in JavaScript. This may be identified as PHP, but it is in fact node.js |
| [renovate](https://git.coopcloud.tech/coop-cloud/renovate) | Not Affected | the image renovate/renovate:41-full from 1.0.1+41-full has the php-cli, however there don't appear to be php web components in the application. |
2. For each app, run `abra app run <APP_DOMAIN> app -- php -v` and compare to the recommended versions:
> ==PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35== fix two critical vulnerabilities that can allow unauthenticated remote code execution. All PHP users are strongly encouraged to update immediately.
Several of the upstream app updates have been released without changes in the Docker version ("tag") number — so unfortunately `abra app upgrade` might not be reliable for ensuring that these updates are applied.
**Please follow this alternative process, to make sure that these nontraditionally-versioned updates are applied**
Using the example of updating a Nextcloud instance, currently running `31.0.6`, on `cloud.example.com`:
1. Undeploy the app immediately! (Hopefully you did this already 🤞): `abra app undeploy cloud.example.com`
2. Consult the table above for whether to "upgrade" or "redeploy"
3. Check your last deployed version: `abra app labels cloud.example.com` -- note the upstream app version, the part after the `+` under "Recipe labels", e.g. in `coop-cloud.cloud_example_com.version 12.0.1+31.0.6-fpm`, we're looking for `31.0.6-fpm`.
4. If you are at any version below the latest (`15.0.0+34.0.5-fpm` in our example), you need to upgrade – see subsection below. **Otherwise, if you were already on the latest version**, and the table below says "redeploy", then deploying the app should get the new version:
5.`abra app deploy cloud.example.com -n`
6. Re-run step #2 of [Checking for affected apps](#check-if-your-deployment-is-affected).
### Applying prerequisite recipe upgrades
1. Read recipe and upstream release notes to plan a sequence of migrations, e.g. in this case:
1. From `12.0.1+31.0.6-fpm` to `13.2.0+32-fpm`
2. From `13.2.0+32-fpm` to `14.6.0+33-fpm`
3. From `14.6.0+33-fpm` to `15.0.0+34.0.5-fpm`
2.`abra app deploy cloud.example.com`
3.`abra app upgrade cloud.example.com`; choose the next version in the plan from #1
4. Wait for the instance to become available again
5. Run `abra app run -u www-data cloud.example.com app -- php occ app:update --all`
6. Repeat steps #3-5 until all updates in the plan are applied
5. Re-run step #2 of [Checking for affected apps](#check-if-your-deployment-is-affected).
## Automated checking with `cc-runall`
1. Download or `git clone` the [`cc-runall` script](https://git.coopcloud.tech/toolshed/cc-scripts/src/branch/main/cc-runall)
2. Download `jq` (either through distribution repositories, or [from the same repo](https://git.coopcloud.tech/toolshed/cc-scripts/src/branch/main/bin/jq))
3.`./cc-runall wordpress app "php -v"`
## Forensics
Exploiting these vulnerabilities would likely require multiple attempts. Each attempt has a good chance of crashing the worker it's executed against. This will show up in logs as 500's and 502's.
A successful attack may not leave these traces, so abcence of evidence is not evidence of absence. However, 500 and 502 spikes are evidence of aborant behavior and attacks are one common cause of such behavior.
!!! warning "Our security is a federated endeavor"
Maintaining security in Coop Cloud deployments is a federated endeavor. Please use these advisories as a starting point, but check for outdated software versions and vulnerabilities on your own deployments, too.
Please take your own steps to ensure your operations are protected, and reach out to us if we've missed anything!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.