# CVE-2022-0732: Missing authorization in Copy9

> Attackers can access or modify other users' data via API requests due to missing authentication and authorization in mobile monitoring services.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 24 Feb 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-j85g-452w-9q39

## What is CVE-2022-0732?

CVE-2022-0732 is a high-severity missing authorization vulnerability in 1Byte Copy9, published on 24 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The backend infrastructure shared by multiple mobile device monitoring services does not adequately authenticate or authorize API requests, creating an IDOR (Insecure Direct Object Reference) vulnerability.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

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

It affects 9 products.


Products: 1byte Copy9, 1byte Exactspy, 1byte Fonetracker, 1byte Guestspy, 1byte Ispyoo, 1byte Mxspy, 1byte Secondclone, 1byte the Truth Spy, 1byte Thespyapp.

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

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

## Is CVE-2022-0732 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0732 is a high-severity missing authorization vulnerability in 1Byte Copy9, published on 24 Feb 2022. 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-2022-0732 in the wild and no public exploit code.

Affected product: 1Byte Copy9. 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-0732/ (Markdown: https://insights.sbomify.com/CVE-2022-0732/index.md)
```

## Sources

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

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