# CVE-2023-36620: Information disclosure in n/a

> Missing backup restriction in Boomerang Parental Control allows attackers to extract API tokens from device backups, enabling unauthorized access.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Nov 2023
- **Updated:** 5 Sep 2024
- **Also known as:** GHSA-jhc6-x647-xmhf

## What is CVE-2023-36620?

CVE-2023-36620 is a medium-severity vulnerability in n/a, published on 3 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in the Boomerang Parental Control application before 13.83 for Android. The app is missing the android:allowBackup="false" attribute in the manifest. This allows the user to backup the internal memory of the app to a PC. This gives the user access to the API token that is used to authenticate requests to the API.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2023-36620?

It affects 1 product.


Products: Nationaledtech Boomerang.

## How do I fix CVE-2023-36620?

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

## Is CVE-2023-36620 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-36621](https://insights.sbomify.com/CVE-2023-36621/): Security feature bypass in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-36620 and fix it if it is affected.

What it is: CVE-2023-36620 is a medium-severity vulnerability in n/a, published on 3 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-36620 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-2023-36620/ (Markdown: https://insights.sbomify.com/CVE-2023-36620/index.md)
```

## Sources

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

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