# CVE-2021-41847: Missing authorization in n/a

> Authorized users can bypass zone restrictions to view sensitive personal data and unlock doors or create accounts in unauthorized zones.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fhq9-p69r-3jq8

## What is CVE-2021-41847?

CVE-2021-41847 is a high-severity missing authorization vulnerability in n/a, published on 1 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in 3xLogic Infinias Access Control through 6.7.10708.0, affecting physical security. Users with login credentials assigned to a specific zone can send modified HTTP GET and POST requests, allowing them to view user data such as personal information and Prox card credentials. Also, an authorized user of one zone can send API requests to unlock electronic locks associated with zones they are unauthorized to have access to. They can also create new user logins for zones they were not authorized to access, including the root zone of the software.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: 3xlogic Infinias Access Control.

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

No fix has been published for CVE-2021-41847 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-41847 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-41847 is a high-severity missing authorization vulnerability in n/a, published on 1 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41847 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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