CVE-2022-40280
CVE-2022-40280 is a high-severity vulnerability in Samsung Tizenrt with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-772.
Key facts
- Severity: High (CVSS 3.x base score 7.5)
- EPSS exploit prediction: 1% (57th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-772
- Affected product: Samsung Tizenrt
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2022-40280?
- 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.
- How severe is CVE-2022-40280?
- CVE-2022-40280 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
- Is CVE-2022-40280 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (57th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2022-40280?
- CVE-2022-40280 primarily affects Samsung Tizenrt. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2022-40280?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2022-40280 published?
- CVE-2022-40280 was published on 2022-09-08 and last updated on 2026-06-17.
References
- https://github.com/Samsung/TizenRT/blob/f8f776dd183246ad8890422c1ee5e8f33ab2aaaf/external/iotivity/iotivity_1.2-rel/resource/csdk/security/provisioning/src/provisioningdatabasemanager.c#L100
- https://github.com/Samsung/TizenRT/issues/5627
- https://www.sqlite.org/c3ref/open.html
Affected products (4)
- cpe:2.3:o:samsung:tizenrt:1.0:m1:*:*:*:*:*:*
- cpe:2.3:o:samsung:tizenrt:1.1:-:*:*:*:*:*:*
- cpe:2.3:o:samsung:tizenrt:2.0:-:*:*:*:*:*:*
- cpe:2.3:o:samsung:tizenrt:3.0:gbm:*:*:*:*:*:*
More vulnerabilities in Samsung Tizenrt
- CVE-2022-40279 — High (CVSS 7.5): An issue was discovered in Samsung TizenRT through 3.0_GBM (and 3.1_PRE). l2_packet_receive_timeout in…
- CVE-2022-40278 — High (CVSS 7.5): An issue was discovered in Samsung TizenRT through 3.0_GBM (and 3.1_PRE). createDB in…
- CVE-2022-40281 — High (CVSS 7.5): An issue was discovered in Samsung TizenRT through 3.0_GBM (and 3.1_PRE). cyassl_connect_step2 in curl/vtls/cyassl.c…
- CVE-2021-22684 — High (CVSS 7.5): Tizen RT RTOS version 3.0.GBB is vulnerable to integer wrap-around in functions_calloc and mm_zalloc. This improper…
All CVEs affecting Samsung Tizenrt →
Other CWE-772 vulnerabilities
- CVE-2020-12134 — Critical (CVSS 9.8): Nanometrics Centaur through 4.3.23 and TitanSMA through 4.2.20 mishandle access control for the syslog log.
- CVE-2017-15032 — Critical (CVSS 9.8): ImageMagick version 7.0.7-2 contains a memory leak in ReadYCBCRImage in coders/ycbcr.c.
- CVE-2017-14138 — Critical (CVSS 9.8): ImageMagick 7.0.6-5 has a memory leak vulnerability in ReadWEBPImage in coders/webp.c because memory is not freed in…
- CVE-2017-11641 — Critical (CVSS 9.8): GraphicsMagick 1.3.26 has a Memory Leak in the PersistCache function in magick/pixel_cache.c during writing of Magick…
- CVE-2020-14339 — High (CVSS 8.8): A flaw was found in libvirt, where it leaked a file descriptor for `/dev/mapper/control` into the QEMU process. This…
- CVE-2018-19760 — High (CVSS 8.8): cfg_init in confuse.c in libConfuse 3.2.2 has a memory leak.