CVE-2022-40281
HIGHCVSS 7.5/10EPSS 0.51%
Last modified
CVE-2022-40281 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. An issue was discovered in Samsung TizenRT through 3.0_GBM (and 3.1_PRE). cyassl_connect_step2 in curl/vtls/cyassl.c has a missing X509_free after SSL_get_peer_certificate, leading to information disclosure.. EPSS estimates a 0.51% chance of exploitation in the next 30 days.
Description
An issue was discovered in Samsung TizenRT through 3.0_GBM (and 3.1_PRE). cyassl_connect_step2 in curl/vtls/cyassl.c has a missing X509_free after SSL_get_peer_certificate, leading to information disclosure.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Samsung | Tizenrt | 1.0 | M1 |
| Samsung | Tizenrt | 1.1 | — |
| Samsung | Tizenrt | 2.0 | — |
| Samsung | Tizenrt | 3.0 | Gbm |
References
- https://github.com/Samsung/TizenRT/issues/5626Issue Tracking, Third Party Advisory
- https://www.openssl.org/docs/man1.1.1/man3/SSL_get_peer_certificate.htmlThird Party Advisory
- https://github.com/Samsung/TizenRT/issues/5626Issue Tracking, Third Party Advisory
- https://www.openssl.org/docs/man1.1.1/man3/SSL_get_peer_certificate.htmlThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-40281?
An issue was discovered in Samsung TizenRT through 3.0_GBM (and 3.1_PRE). cyassl_connect_step2 in curl/vtls/cyassl.c has a missing X509_free after SSL_get_peer_certificate, leading to information disclosure.
How severe is CVE-2022-40281?
CVE-2022-40281 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 0.51% probability of exploitation in the next 30 days.
How do I fix CVE-2022-40281?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2022-40281?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
