# CVE-2022-40280: Denial of service in n/a

> A resource leak in the provisioning database manager allows attackers to cause a denial of service in Samsung TizenRT.

- **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:** 8 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4g8m-w5fr-hw5h

## What is CVE-2022-40280?

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

### Official description

An issue was discovered in Samsung TizenRT through 3.0_GBM (and 3.1_PRE). createDB in security/provisioning/src/provisioningdatabasemanager.c has a missing sqlite3_close after sqlite3_open_v2, leading to a denial of service.

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime)

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

It affects 1 product.


Products: Samsung Tizenrt.

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

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

## Is CVE-2022-40280 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-40278](https://insights.sbomify.com/CVE-2022-40278/): Use after free in n/a (high 7.5)
- [CVE-2022-40279](https://insights.sbomify.com/CVE-2022-40279/): Denial of service in n/a (high 7.5)
- [CVE-2022-40281](https://insights.sbomify.com/CVE-2022-40281/): Memory corruption in n/a (high 7.5)
- [CVE-2021-22684](https://insights.sbomify.com/CVE-2021-22684/): Integer overflow in Tizen RT RTOS (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40280 is a high-severity denial of service vulnerability in n/a, published on 8 Sep 2022. 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-2022-40280 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-2022-40280/ (Markdown: https://insights.sbomify.com/CVE-2022-40280/index.md)
```

## Sources

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

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