# GHSA-q79m-c546-2g63: CakePHP vulnerable to Denial of Service attack through XML payloads > Attackers can cause denial of service in CakePHP applications by sending crafted XML payloads to the RequestHandlerComponent. - **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:** 20 Jan 2023 ## What is GHSA-q79m-c546-2g63? GHSA-q79m-c546-2g63 is a denial of service vulnerability in cakephp/cakephp, published on 20 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description RequestHandlerComponent had a vulnerability that would allow well crafted requests to create a denial of service attack. RequestHandlerComponent leverages `Xml::build()` which allows reading local files. We recommend that all applications using RequestHandlerComponent upgrade, or disable parsing XML payloads. ## Which versions are affected by GHSA-q79m-c546-2g63? 16 open source packages ship an affected version, including cakephp/cakephp. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `cakephp/cakephp` | Packagist | From 2.0.0 | 2.0.99 | | `cakephp/cakephp` | Packagist | From 2.0.0 | 2.0.99 | | `cakephp/cakephp` | Packagist | From 2.1.0 | 2.1.99 | | `cakephp/cakephp` | Packagist | From 2.1.0 | 2.1.99 | | `cakephp/cakephp` | Packagist | From 2.2.0 | 2.2.99 | | `cakephp/cakephp` | Packagist | From 2.2.0 | 2.2.99 | | `cakephp/cakephp` | Packagist | From 2.3.0 | 2.3.99 | | `cakephp/cakephp` | Packagist | From 2.3.0 | 2.3.99 | | `cakephp/cakephp` | Packagist | From 2.4.0 | 2.4.99 | | `cakephp/cakephp` | Packagist | From 2.4.0 | 2.4.99 | | `cakephp/cakephp` | Packagist | From 2.5.0 | 2.5.90 | | `cakephp/cakephp` | Packagist | From 2.5.0 | 2.5.90 | | `cakephp/cakephp` | Packagist | From 2.6.0 | 2.6.6 | | `cakephp/cakephp` | Packagist | From 2.6.0 | 2.6.6 | | `cakephp/cakephp` | Packagist | From 3.0.0 | 3.0.6 | | `cakephp/cakephp` | Packagist | From 3.0.0 | 3.0.6 | ## How do I fix GHSA-q79m-c546-2g63? Upgrade cakephp/cakephp to a fixed version for your release line: 2.0.99, 2.1.99, 2.2.99 or 2.3.99. ## Is GHSA-q79m-c546-2g63 being exploited? There is no known exploitation of GHSA-q79m-c546-2g63 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-q79m-c546-2g63 and fix it if it is affected. What it is: GHSA-q79m-c546-2g63 is a denial of service vulnerability in cakephp/cakephp, published on 20 Jan 2023. 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-q79m-c546-2g63 in the wild and no public exploit code. Affected packages and fixed versions: - cakephp/cakephp (Packagist): affected from 2.0.0; fixed in 2.0.99 - cakephp/cakephp (Packagist): affected from 2.0.0; fixed in 2.0.99 - cakephp/cakephp (Packagist): affected from 2.1.0; fixed in 2.1.99 - cakephp/cakephp (Packagist): affected from 2.1.0; fixed in 2.1.99 - cakephp/cakephp (Packagist): affected from 2.2.0; fixed in 2.2.99 - cakephp/cakephp (Packagist): affected from 2.2.0; fixed in 2.2.99 - cakephp/cakephp (Packagist): affected from 2.3.0; fixed in 2.3.99 - cakephp/cakephp (Packagist): affected from 2.3.0; fixed in 2.3.99 - cakephp/cakephp (Packagist): affected from 2.4.0; fixed in 2.4.99 - cakephp/cakephp (Packagist): affected from 2.4.0; fixed in 2.4.99 - cakephp/cakephp (Packagist): affected from 2.5.0; fixed in 2.5.90 - cakephp/cakephp (Packagist): affected from 2.5.0; fixed in 2.5.90 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-q79m-c546-2g63/ (Markdown: https://insights.sbomify.com/GHSA-q79m-c546-2g63/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-q79m-c546-2g63 --- From sbomify Insights: https://insights.sbomify.com/GHSA-q79m-c546-2g63/ Summaries are generated and may contain mistakes; the official description above is the record.