# CVE-2022-24190: Missing authorization in n/a

> An attacker can bind their account to any user's picture frame and accept the request without authentication or user approval.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-r24r-7cxr-hmcp

## What is CVE-2022-24190?

CVE-2022-24190 is a high-severity missing authorization vulnerability in n/a, published on 28 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The /device/acceptBind end-point for Ourphoto App version 1.4.1 does not require authentication or authorization. The user_token header is not implemented or present on this end-point. An attacker can send a request to bind their account to any users picture frame, then send a POST request to accept their own bind request, without the end-users approval or interaction.

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

## Which versions are affected by CVE-2022-24190?

It affects 1 product.


Products: Sz-Fujia Ourphoto.

## How do I fix CVE-2022-24190?

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

## Is CVE-2022-24190 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24190 exists.

## Other vulnerabilities in n/a

- [CVE-2022-24187](https://insights.sbomify.com/CVE-2022-24187/): Information disclosure in n/a (high 7.5)
- [CVE-2022-24188](https://insights.sbomify.com/CVE-2022-24188/): Information disclosure in n/a (high 7.5)
- [CVE-2022-24189](https://insights.sbomify.com/CVE-2022-24189/): Auth bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24190 and fix it if it is affected.

What it is: CVE-2022-24190 is a high-severity missing authorization vulnerability in n/a, published on 28 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24190 exists.

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

## Sources

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

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