CVE-2017-8458: Medium severity brave browser vulnerability

Published May 3, 2017
·
Updated

Brave 0.12.4 has a URI Obfuscation issue in which a string such as https://safe.example.com@unsafe.example.com/ is displayed without a clear UI indication that it is not a resource on the safe.example.com web site.

Affected Software

1 affected component
Brave Brave=0.12.4

Event History

May 3, 2017
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-8458?

The severity of CVE-2017-8458 is considered moderate due to the potential for phishing attacks.

2

How do I fix CVE-2017-8458?

To fix CVE-2017-8458, users should upgrade to a version of Brave newer than 0.12.4 that addresses the URI obfuscation issue.

3

What type of vulnerability is CVE-2017-8458?

CVE-2017-8458 is classified as a URI obfuscation vulnerability.

4

Which version of Brave is affected by CVE-2017-8458?

Brave version 0.12.4 is the affected version for CVE-2017-8458.

5

What could happen if I don't address CVE-2017-8458?

If CVE-2017-8458 is not addressed, users may be susceptible to phishing scams due to misleading URL displays.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203