PatchTheCVEtrape vulnerabilities and fixes
Recent CVEs affecting trape, with upgrade or downgrade steps. 4 tracked.
trape has 4 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 4. Most recent: 2019-07-10. Highest priority: CVE-2017-17713 (score 64/100).
- CVE-2019-13489 CRITICAL 9.8 UPGRADE Trape through 2019-05-08 has SQL injection via the data[2] variable in core/db.py, as demonstrated by the /bs
- CVE-2019-13488 MEDIUM 6.1 UPGRADE A cross-site scripting (XSS) vulnerability in static/js/trape.js in Trape through 2019-05-08 allows remote att
- CVE-2017-17714 MEDIUM 6.1 UPGRADE Trape before 2017-11-05 has XSS via the /nr red parameter, the /nr vId parameter, the /register User-Agent HTT
- CVE-2017-17713 CRITICAL 9.8 UPGRADE Trape before 2017-11-05 has SQL injection via the /nr red parameter, the /nr vId parameter, the /register User
FAQ
How do I fix trape 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 trape being exploited right now?
None of the tracked trape CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which trape CVE should I patch first?
CVE-2017-17713 currently ranks highest (64/100): Trape before 2017-11-05 has SQL injection via the /nr red parameter, the /nr vId parameter, the /register User.