# CVE-2023-29726: Denial of service in n/a

> An attacker can inject excessive data into the Call Blocker app database, causing an out-of-memory crash and persistent denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2023
- **Updated:** 13 Jan 2025
- **Also known as:** GHSA-4rxp-92f9-jpp2

## What is CVE-2023-29726?

CVE-2023-29726 is a high-severity denial of service vulnerability in n/a, published on 30 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Call Blocker application 6.6.3 for Android incorrectly opens a key component that an attacker can use to inject large amounts of dirty data into the application's database. When the application starts, it loads the data from the database into memory. Once the attacker injects too much data, the application triggers an OOM error and crashes, resulting in a persistent denial of service.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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

It affects 1 product.


Products: Applika Call Blocker.

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

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

## Is CVE-2023-29726 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-29727](https://insights.sbomify.com/CVE-2023-29727/): Missing authorization in n/a (critical 9.8)
- [CVE-2023-29728](https://insights.sbomify.com/CVE-2023-29728/): Missing authorization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-29726 is a high-severity denial of service vulnerability in n/a, published on 30 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29726 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-29726/ (Markdown: https://insights.sbomify.com/CVE-2023-29726/index.md)
```

## Sources

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

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