# CVE-2023-40040: Missing authorization in n/a

> Remote attackers can start the camera feed in the MyCrops HiGrade app on older Android versions lacking runtime permission checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 11 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-qcjm-2565-959w

## What is CVE-2023-40040?

CVE-2023-40040 is a medium-severity missing authorization vulnerability in n/a, published on 11 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the MyCrops HiGrade "THC Testing & Cannabi" application 1.0.337 for Android. A remote attacker can start the camera feed via the com.cordovaplugincamerapreview.CameraActivity component in some situations. NOTE: this is only exploitable on Android versions that lack runtime permission checks, and of those only Android SDK 5.1.1 API 22 is consistent with the manifest. Thus, this applies only to Android Lollipop, affecting less than five percent of Android devices as of 2023.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Mycrops Higrade.

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

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

## Is CVE-2023-40040 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-40040 is a medium-severity missing authorization vulnerability in n/a, published on 11 Sep 2023. 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-2023-40040 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-2023-40040/ (Markdown: https://insights.sbomify.com/CVE-2023-40040/index.md)
```

## Sources

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

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