# GHSA-4h8f-c635-25p7: ibexa/post-install affected by Breach with Varnish VCL

> Attackers can extract secrets from HTTP responses via BREACH attack due to enabled compression in default Varnish and web server templates.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Dec 2024

## What is GHSA-4h8f-c635-25p7?

GHSA-4h8f-c635-25p7 is a vulnerability in ibexa/post-install, published on 2 Dec 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

### Impact
This is not a vulnerability in the code per se, but included platform.sh Varnish VCL templates and Apache/Nginx vhost templates enable compression of API and JSON messages. This is a potential case of the BREACH vulnerability, which affects HTTP compression, where secrets can be extracted through carefully crafted requests. The fix disables compression in these templates. Please make sure to make the same change in your configuration files, see the release notes for specific instructions.

### Patches
- See "Patched versions".
- v1.0: https://github.com/ibexa/post-install/commit/d91cc02623dd3263a99a94ace133c95e48909e5d
- v4.6: https://github.com/ibexa/post-install/commit/ae7c3c2081a862c75b90828f08bd74436ceb8fe8

### Workarounds
Make sure HTTP compression is disabled for REST API requests and other communication that might contain secrets.

### References
- Advisory: https://developers.ibexa.co/security-advisories/ibexa-sa-2024-006-vulnerabilities-in-content-name-pattern-commerce-shop-and-varnish-vhost-templates
- Release notes v3.3: https://doc.ibexa.co/en/latest/update_and_migration/from_3.3/update_from_3.3/#v3341
- Release notes v4.6: https://doc.ibexa.co/en/latest/update_and_migration/from_4.6/update_from_4.6/#v4614
- https://github.com/ezsystems/ezplatform-http-cache/security/advisories/GHSA-mgfg-7533-7jf6
- https://github.com/ibexa/http-cache/security/advisories/GHSA-fh7v-q458-7vmw
- https://www.breachattack.com/

## Which versions are affected by GHSA-4h8f-c635-25p7?

4 open source packages ship an affected version, including ibexa/post-install.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ibexa/post-install` | Packagist | From 1.0.0 | 1.0.16 |
| `ibexa/post-install` | Packagist | From 1.0.0 | 1.0.16 |
| `ibexa/post-install` | Packagist | From 4.6.0 | 4.6.14 |
| `ibexa/post-install` | Packagist | From 4.6.0 | 4.6.14 |

## How do I fix GHSA-4h8f-c635-25p7?

Upgrade ibexa/post-install to a fixed version for your release line: 1.0.16 or 4.6.14.

## Is GHSA-4h8f-c635-25p7 being exploited?

There is no known exploitation of GHSA-4h8f-c635-25p7 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4h8f-c635-25p7 and fix it if it is affected.

What it is: GHSA-4h8f-c635-25p7 is a vulnerability in ibexa/post-install, published on 2 Dec 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-4h8f-c635-25p7 in the wild and no public exploit code.

Affected packages and fixed versions:
- ibexa/post-install (Packagist): affected from 1.0.0; fixed in 1.0.16
- ibexa/post-install (Packagist): affected from 1.0.0; fixed in 1.0.16
- ibexa/post-install (Packagist): affected from 4.6.0; fixed in 4.6.14
- ibexa/post-install (Packagist): affected from 4.6.0; fixed in 4.6.14

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-4h8f-c635-25p7/ (Markdown: https://insights.sbomify.com/GHSA-4h8f-c635-25p7/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4h8f-c635-25p7

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4h8f-c635-25p7/
Summaries are generated and may contain mistakes; the official description above is the record.