CVE-2018-6324
First published: Fri Feb 16 2018(Updated: )
F-Secure Radar (on-premises) before 2018-02-15 has an Unvalidated Redirect via the ReturnUrl parameter that triggers upon a user login.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| F-Secure Radar | <=3.9.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-6324?
CVE-2018-6324 is classified as a medium severity vulnerability due to potential security risks associated with unvalidated redirects.
How do I fix CVE-2018-6324?
To fix CVE-2018-6324, update F-Secure Radar to version 3.9.2 or later, which addresses the unvalidated redirect issue.
What impact does CVE-2018-6324 have on user security?
CVE-2018-6324 can lead to phishing attacks by allowing attackers to redirect users to malicious sites after login.
Which versions of F-Secure Radar are affected by CVE-2018-6324?
F-Secure Radar versions prior to 3.9.2 are affected by CVE-2018-6324.
Who is at risk for CVE-2018-6324?
Organizations using versions of F-Secure Radar before 3.9.2 are at risk of exploitation through unvalidated redirects.
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/author
- agent/tags
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- vendor/f-secure
- canonical/f-secure radar
- version/f-secure radar/3.9.1