Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

cstring vulnerabilities and fixes

Recent CVEs affecting cstring, with upgrade or downgrade steps. 1 tracked.

cstring has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2018-05-15. Highest priority: CVE-2018-11097 (score 47/100).

FAQ

How do I fix cstring vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is cstring being exploited right now?

None of the tracked cstring CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which cstring CVE should I patch first?

CVE-2018-11097 currently ranks highest (47/100): An issue was discovered in cloudwu/cstring through 2016-11-09.

← Back to latest CVEs