# CVE-2022-1716: Security feature bypass in Keep My Notes

> An attacker with physical access can bypass the password lock in Keep My Notes to access user data due to insufficient anti-tampering controls.

- **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:** 2 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-c93x-56c5-pf53

## What is CVE-2022-1716?

CVE-2022-1716 is a medium-severity vulnerability in Keep My Notes, published on 2 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Keep My Notes v1.80.147 allows an attacker with physical access to the victim's device to bypass the application's password/pin lock to access user data. This is possible due to lack of adequate security controls to prevent dynamic code manipulation.

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

It affects 1 product.


Products: Kitetech Keep My Notes.

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

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

## Is CVE-2022-1716 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1716 is a medium-severity vulnerability in Keep My Notes, published on 2 Jun 2022. 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-2022-1716 in the wild and no public exploit code.

Affected product: Keep My Notes. 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-1716/ (Markdown: https://insights.sbomify.com/CVE-2022-1716/index.md)
```

## Sources

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

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