bug tracking system vulnerabilities and fixes

Recent CVEs affecting bug tracking system, with upgrade or downgrade steps. 3 tracked.

Also searched as: bugtrackingsystem.

bug tracking system has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2007-03-07. Highest priority: CVE-2007-1291 (score 45/100).

• CVE-2007-1291 MEDIUM 5.8 DOWNGRADE Multiple cross-site scripting (XSS) vulnerabilities in Tyger Bug Tracking System (TygerBT) 1.1.3 allow remote
• CVE-2007-1290 HIGH 7.5 DOWNGRADE SQL injection vulnerability in ViewReport.php in Tyger Bug Tracking System (TygerBT) 1.1.3 allows remote attac
• CVE-2007-1289 MEDIUM 6.4 DOWNGRADE SQL injection vulnerability in ViewBugs.php in Tyger Bug Tracking System (TygerBT) 1.1.3 allows remote attacke

FAQ

How do I fix bug tracking system 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 bug tracking system being exploited right now?

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

Which bug tracking system CVE should I patch first?

CVE-2007-1291 currently ranks highest (45/100): Multiple cross-site scripting (XSS) vulnerabilities in Tyger Bug Tracking System (TygerBT) 1.1.3 allow remote .

RSS feed for bug tracking system · ← Back to latest CVEs