# CVE-2024-40239: Auth bypass in n/a

> A physically proximate attacker can bypass fingerprint authentication in the Life: Personal Diary Android app to escalate privileges and access private data.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 8 Nov 2024
- **Updated:** 13 Nov 2024
- **Also known as:** GHSA-mmxq-gq3m-xgpf

## What is CVE-2024-40239?

CVE-2024-40239 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An incorrect access control issue in Life: Personal Diary, Journal android app 17.5.0 allows a physically proximate attacker to escalate privileges via the fingerprint authentication function.

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

It affects 1 product.


Products: Hitbytes Life.

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

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

## Is CVE-2024-40239 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-40239 is a medium-severity authentication bypass vulnerability in n/a, published on 8 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-40239 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-2024-40239/ (Markdown: https://insights.sbomify.com/CVE-2024-40239/index.md)
```

## Sources

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

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