# CVE-2024-53701: Missing authorization in arrows N F-51C

> Attackers with physical access to an unlocked FCNT Android device can bypass authentication to view or alter privacy mode settings, exposing hidden applications.

- **Severity:** Low 3.1 (`CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Nov 2024
- **Updated:** 3 Dec 2024
- **Also known as:** GHSA-pvjp-3rj2-p4ww

## What is CVE-2024-53701?

CVE-2024-53701 is a low-severity missing authorization vulnerability in FCNT LLC arrows N F-51C, published on 29 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple FCNT Android devices provide the original security features such as "privacy mode" where arbitrary applications can be set not to be displayed, etc.
Under certain conditions, and when an attacker can directly operate the device which its screen is unlocked by a user, the provided security features' setting pages may be exposed and/or the settings may be altered, without authentication. For example, specific applications in the device configured to be hidden may be displayed and/or activated.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2024-53701?


## How do I fix CVE-2024-53701?

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

## Is CVE-2024-53701 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53701 and fix it if it is affected.

What it is: CVE-2024-53701 is a low-severity missing authorization vulnerability in FCNT LLC arrows N F-51C, published on 29 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53701 in the wild and no public exploit code.

Affected product: FCNT LLC arrows N F-51C. 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-2024-53701/ (Markdown: https://insights.sbomify.com/CVE-2024-53701/index.md)
```

## Sources

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

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