# CVE-2023-29738: Privilege escalation in n/a

> A local attacker can achieve code execution and privilege escalation in the Wave Animated Keyboard Emoji app via database files.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2023
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-3482-3whx-826m

## What is CVE-2023-29738?

CVE-2023-29738 is a high-severity vulnerability in n/a, published on 30 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue found in Wave Animated Keyboard Emoji v.1.70.7 for Android allows a local attacker to cause code execution and escalation of Privileges via the database files.

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

It affects 1 product.


Products: Wavekeyboard Wave Animated Keyboard Emoji.

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

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

## Is CVE-2023-29738 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-29737](https://insights.sbomify.com/CVE-2023-29737/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-29738 is a high-severity vulnerability in n/a, published on 30 May 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-29738 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-29738/ (Markdown: https://insights.sbomify.com/CVE-2023-29738/index.md)
```

## Sources

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

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