# CVE-2021-43996: Incorrect Access Control in Ignition

> The Laravel Ignition component's variable name fixing feature can lead to incorrect access control, allowing unauthorized access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vhrp-8qx4-vr6c

## What is CVE-2021-43996?

CVE-2021-43996 is a critical missing authorization vulnerability in n/a, published on 17 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Ignition component before 1.16.15, and 2.0.x before 2.0.6, for Laravel has a "fix variable names" feature that can lead to incorrect access control.

## Which versions are affected by CVE-2021-43996?

4 open source packages ship an affected version, including facade/ignition. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `facade/ignition` | Packagist | All versions | 1.16.15 |
| `facade/ignition` | Packagist | All versions | 1.16.15 |
| `facade/ignition` | Packagist | From 2.0.0 | 2.0.6 |
| `facade/ignition` | Packagist | From 2.0.0 | 2.0.6 |

Products: Facade Ignition.

## How do I fix CVE-2021-43996?

Upgrade facade/ignition to a fixed version for your release line: 1.16.15 or 2.0.6.

## Is CVE-2021-43996 being exploited?

There is no known exploitation of CVE-2021-43996 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-3129](https://insights.sbomify.com/CVE-2021-3129/): Laravel Ignition File Upload (critical 9.8, exploited in the wild)
- [CVE-2020-13909](https://insights.sbomify.com/CVE-2020-13909/): Critical severity vulnerability in Ignition (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43996 and fix it if it is affected.

What it is: CVE-2021-43996 is a critical missing authorization vulnerability in n/a, published on 17 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-43996 in the wild and no public exploit code.

Affected packages and fixed versions:
- facade/ignition (Packagist): affected all versions; fixed in 1.16.15
- facade/ignition (Packagist): affected all versions; fixed in 1.16.15
- facade/ignition (Packagist): affected from 2.0.0; fixed in 2.0.6
- facade/ignition (Packagist): affected from 2.0.0; fixed in 2.0.6

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/CVE-2021-43996/ (Markdown: https://insights.sbomify.com/CVE-2021-43996/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-43996
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-43996
- OSV: https://osv.dev/vulnerability/CVE-2021-43996

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-43996/
Summaries are generated and may contain mistakes; the official description above is the record.