jtbc vulnerabilities and fixes
Recent CVEs affecting jtbc, with upgrade or downgrade steps. 1 tracked.
jtbc has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2019-03-07. Highest priority: CVE-2018-17429 (score 48/100).
- CVE-2018-17429 HIGH 8.8 DOWNGRADE /console/account/manage.php?type=action&action=add in JTBC v3.0(C) has CSRF for adding an administrator accoun
FAQ
How do I fix jtbc 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 jtbc being exploited right now?
None of the tracked jtbc CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which jtbc CVE should I patch first?
CVE-2018-17429 currently ranks highest (48/100): /console/account/manage.php?type=action&action=add in JTBC v3.0(C) has CSRF for adding an administrator accoun.