CVE-2018-6189
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 XSS via vectors involving the Tags parameter in the JSON request body in an outbound request for the /api/latest/vulnerabilityscans/tags/batch resource, aka a "suggested metadata tags for assets" issue.
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 · moderate confidenceF-Secure Radar (on-premises) versions before the 2018-02-15 patch contain a stored Cross-Site Scripting (XSS) vulnerability. The vulnerability exists in the /api/latest/vulnerabilityscans/tags/batch API endpoint where the Tags parameter in a JSON request body is not properly sanitized before being stored and rendered. An unauthenticated attacker could inject malicious JavaScript code through this parameter that would execute when other users view the suggested metadata tags.
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 installed F-Secure Radar versionCheck the application version through the F-Secure Radar web interface (typically found in Help > About or the administrator dashboard), or inspect the installation directory for version metadata filesAffected if The installed version is 3.9.1 or lower (any version before the 2018-02-15 patch)
-
Verify API endpoint accessibilityConfirm that the /api/latest/vulnerabilityscans/tags/batch endpoint is reachable by attempting an authenticated request to this API path through the F-Secure Radar web interface or directly via HTTPAffected if The endpoint responds and accepts JSON requests with a Tags parameter
-
Inspect stored metadata tags for malicious contentQuery the F-Secure Radar database or use the API to retrieve all vulnerability scan tags and examine them for suspicious patterns such as <script>, javascript:, onerror=, or other HTML/JavaScript elementsAffected if Any Tags entries contain unescaped HTML or JavaScript code that could execute in a browser
-
Check input validation on the tags endpointReview any available web application firewall (WAF) logs, API gateway logs, or application logs for the /api/latest/vulnerabilityscans/tags/batch endpoint to see if input sanitization or validation is being applied to the Tags parameterAffected if No input validation or sanitization is visible in logs or configuration, and the application directly stores raw tag values
A user is affected if F-Secure Radar version is 3.9.1 or lower AND the vulnerable /api/latest/vulnerabilityscans/tags/batch endpoint is accessible and accepts input without sanitization, allowing stored XSS payloads to persist in the Tags data.
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 dataUpgrade F-Secure Radar to the 2018-02-15 patch or later. As an interim measure, implement web application firewall (WAF) rules to sanitize or block malicious patterns in the Tags parameter and ensure proper input validation on all API endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6189 — 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-6189 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