# GHSA-9wwx-c723-vm8x: eZ Platform REST API returns list of all SiteAccesses > Unauthenticated attackers can retrieve a list of all SiteAccess names via the REST API, exposing internal configuration details. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 May 2024 ## What is GHSA-9wwx-c723-vm8x? GHSA-9wwx-c723-vm8x is a vulnerability in ezsystems/ezpublish-kernel, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description This security advisory fixes a vulnerability in eZ Platform, and we recommend that you install it as soon as possible. The issue is that the REST API may be made to disclose the names of all available site accesses. The severity of this depends on your installation, please consider your response accordingly. To install, use Composer to update "ezsystems/ezpublish-kernel" to one of the "Resolving versions" mentioned above, or apply this patch manually: https://github.com/ezsystems/ezpublish-kernel/commit/1551723ec134878a4cb598bfc5d900ba6164117a ## Which versions are affected by GHSA-9wwx-c723-vm8x? 12 open source packages ship an affected version, including ezsystems/ezpublish-kernel. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ezsystems/ezpublish-kernel` | Packagist | From 5.3.0 | 5.3.12.1 | | `ezsystems/ezpublish-kernel` | Packagist | From 5.3.0 | 5.3.12.1 | | `ezsystems/ezpublish-kernel` | Packagist | From 5.4.0 | 5.4.13.1 | | `ezsystems/ezpublish-kernel` | Packagist | From 5.4.0 | 5.4.13.1 | | `ezsystems/ezpublish-kernel` | Packagist | From 6.0.0 | 6.7.9.1 | | `ezsystems/ezpublish-kernel` | Packagist | From 6.0.0 | 6.7.9.1 | | `ezsystems/ezpublish-kernel` | Packagist | From 6.8.0 | 6.13.5.1 | | `ezsystems/ezpublish-kernel` | Packagist | From 6.8.0 | 6.13.5.1 | | `ezsystems/ezpublish-kernel` | Packagist | From 7.0.0 | 7.2.4.1 | | `ezsystems/ezpublish-kernel` | Packagist | From 7.0.0 | 7.2.4.1 | | `ezsystems/ezpublish-kernel` | Packagist | From 7.3.0 | 7.3.2.1 | | `ezsystems/ezpublish-kernel` | Packagist | From 7.3.0 | 7.3.2.1 | ## How do I fix GHSA-9wwx-c723-vm8x? Upgrade ezsystems/ezpublish-kernel to a fixed version for your release line: 5.3.12.1, 5.4.13.1, 6.7.9.1 or 6.13.5.1. ## Is GHSA-9wwx-c723-vm8x being exploited? There is no known exploitation of GHSA-9wwx-c723-vm8x in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-9wwx-c723-vm8x and fix it if it is affected. What it is: GHSA-9wwx-c723-vm8x is a vulnerability in ezsystems/ezpublish-kernel, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of GHSA-9wwx-c723-vm8x in the wild and no public exploit code. Affected packages and fixed versions: - ezsystems/ezpublish-kernel (Packagist): affected from 5.3.0; fixed in 5.3.12.1 - ezsystems/ezpublish-kernel (Packagist): affected from 5.3.0; fixed in 5.3.12.1 - ezsystems/ezpublish-kernel (Packagist): affected from 5.4.0; fixed in 5.4.13.1 - ezsystems/ezpublish-kernel (Packagist): affected from 5.4.0; fixed in 5.4.13.1 - ezsystems/ezpublish-kernel (Packagist): affected from 6.0.0; fixed in 6.7.9.1 - ezsystems/ezpublish-kernel (Packagist): affected from 6.0.0; fixed in 6.7.9.1 - ezsystems/ezpublish-kernel (Packagist): affected from 6.8.0; fixed in 6.13.5.1 - ezsystems/ezpublish-kernel (Packagist): affected from 6.8.0; fixed in 6.13.5.1 - ezsystems/ezpublish-kernel (Packagist): affected from 7.0.0; fixed in 7.2.4.1 - ezsystems/ezpublish-kernel (Packagist): affected from 7.0.0; fixed in 7.2.4.1 - ezsystems/ezpublish-kernel (Packagist): affected from 7.3.0; fixed in 7.3.2.1 - ezsystems/ezpublish-kernel (Packagist): affected from 7.3.0; fixed in 7.3.2.1 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-9wwx-c723-vm8x/ (Markdown: https://insights.sbomify.com/GHSA-9wwx-c723-vm8x/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-9wwx-c723-vm8x --- From sbomify Insights: https://insights.sbomify.com/GHSA-9wwx-c723-vm8x/ Summaries are generated and may contain mistakes; the official description above is the record.