CVE-2018-6324
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedF-Secure Radar (on-premises) before 2018-02-15 has an Unvalidated Redirect via the ReturnUrl parameter that triggers upon a user login.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceF-Secure Radar on-premises has an unvalidated redirect vulnerability in the login functionality. The ReturnUrl parameter is not validated before use, allowing attackers to craft malicious URLs that redirect authenticated users to arbitrary external websites after login. This enables phishing attacks where victims believe they are on the legitimate site but are actually redirected to malicious pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 3.9.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify F-Secure Radar versionLocate the F-Secure Radar installation and check the version number displayed in the product UI, about page, or installation directory. Common ways: access the web interface and look for version info in Help > About, or check the installed software list on the server.Affected if The installed version is 3.9.1 or lower.
-
Verify login page accepts ReturnUrl parameterAccess the F-Secure Radar login page (typically /Account/Login or similar). Inspect whether the page accepts a ReturnUrl or similar query string parameter in the URL, such as ?ReturnUrl= or ?returnUrl=. Check the HTML form or URL handling for this parameter.Affected if The login page processes a ReturnUrl parameter without validation.
-
Test redirect behaviorAfter confirming the parameter exists, observe whether providing an external URL in the ReturnUrl parameter (such as ?ReturnUrl=https://example.com) results in a redirect to that external site after authentication.Affected if The application redirects to arbitrary external URLs after login rather than restricting redirects to internal or whitelisted paths.
You are affected if your F-Secure Radar version is 3.9.1 or lower and the login functionality processes a ReturnUrl parameter that allows redirects to external websites.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor patch released on 2018-02-15 or later. Additionally, implement strict validation of the ReturnUrl parameter to ensure only relative/internal URLs are allowed (whitelist approach).
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6324 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-6324 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data