PatchTheCVEbanco vulnerabilities and fixes
Recent CVEs affecting banco, with upgrade or downgrade steps. 6 tracked.
banco has 6 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2018-08-03. Highest priority: CVE-2018-14925 (score 58/100).
- CVE-2018-14929 MEDIUM 6.1 DOWNGRADE Matera Banco 1.0.0 is vulnerable to multiple reflected XSS, as demonstrated by the /contingency/web/index.jsp
- CVE-2018-14928 HIGH 7.5 DOWNGRADE /contingency/servlet/ServletFileDownload executes as root and provides unauthenticated access to files via the
- CVE-2018-14927 MEDIUM 5.3 DOWNGRADE Matera Banco 1.0.0 is vulnerable to path traversal (allowing access to system files outside the default applic
- CVE-2018-14926 HIGH 8.8 DOWNGRADE Matera Banco 1.0.0 allows CSRF, as demonstrated by a /contingency/web/messageSend/messageSendHandler.jsp reque
- CVE-2018-14925 CRITICAL 9.8 DOWNGRADE Matera Banco 1.0.0 mishandles Java errors in the backend, as demonstrated by a stack trace revealing use of ne
- CVE-2018-14924 MEDIUM 6.1 DOWNGRADE Matera Banco 1.0.0 is vulnerable to multiple stored XSS, as demonstrated by the sca/privilegio/consultarUsuari
FAQ
How do I fix banco 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 banco being exploited right now?
None of the tracked banco CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which banco CVE should I patch first?
CVE-2018-14925 currently ranks highest (58/100): Matera Banco 1.0.0 mishandles Java errors in the backend, as demonstrated by a stack trace revealing use of ne.