dbcve.org
TizenrtOperating system · Samsung

CVE-2022-40280

HIGH · 7.5 CVSS v3.1 Published 2022-09-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Samsung TizenRT through 3.0_GBM and 3.1_PRE, the createDB function in security/provisioning/src/provisioningdatabasemanager.c opens a SQLite database using sqlite3_open_v2 but never calls sqlite3_close to release resources. This resource leak can exhaust file descriptors and memory, leading to denial of service.

MitigationAdd sqlite3_close calls to properly release the database handle after use or upon error conditions in the createDB function to prevent resource exhaustion.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TizenrtOperating system
Affected:= 1.0= 1.1= 2.0= 3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the vulnerable source file
    Search the TizenRT codebase for the file security/provisioning/src/provisioningdatabasemanager.c. This file contains the createDB function with the resource leak.
    Affected if The file exists in the build and the provisioning feature is included in the firmware.
  2. Verify the provisioning feature is enabled
    Check the build configuration or Kconfig settings to determine if CONFIG_PROVISIONING or similar provisioning support is enabled in the TizenRT image.
    Affected if Provisioning support is compiled into the firmware.
  3. Inspect the createDB function for sqlite3_close
    Open provisioningdatabasemanager.c and locate the createDB function. Examine whether sqlite3_close is called anywhere within this function, either in success paths or error handling paths.
    Affected if The function calls sqlite3_open_v2 but does NOT call sqlite3_close anywhere, leaving the database handle open.
  4. Check for resource exhaustion symptoms
    Monitor the system for file descriptor exhaustion errors or memory growth over time, particularly when the provisioning database is created repeatedly.
    Affected if The system exhibits file descriptor leaks or abnormal memory growth tied to provisioning operations.

A user is affected if the TizenRT firmware includes the provisioning feature with the vulnerable createDB function that lacks sqlite3_close calls, causing resource leaks during database creation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add sqlite3_close calls to properly release the database handle after use or upon error conditions in the createDB function to prevent resource exhaustion.

Recommended fix Moderate confidence
  1. Locate the source file security/provisioning/src/provisioningdatabasemanager.c in the TizenRT repository
  2. Open the file and find the createDB function
  3. Identify all return points in the function, especially after successful sqlite3_open_v2
  4. Add a call to sqlite3_close(db) before each return statement to ensure the database handle is released
  5. Ensure that error handling paths also close the database handle before returning an error code
  6. Rebuild the TizenRT firmware and verify that the resource leak is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tizenrt Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40280 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-40280 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data