CVE-2018-12354
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 · uneditedKnowage (formerly SpagoBI) 6.1.1 allows CSRF via every form, as demonstrated by a /knowage/restful-services/2.0/analyticalDrivers/ POST request.
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 confidenceKnowage 6.1.1 is vulnerable to Cross-Site Request Forgery (CSRF) across all application forms. The lack of anti-CSRF tokens or similar protections on endpoints like /knowage/restful-services/2.0/analyticalDrivers/ allows attackers to trick authenticated users into unknowingly submitting malicious requests that perform unintended actions within the application.
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= 6.1.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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Confirm Knowage versionCheck the installed Knowage version by accessing the application admin panel, about page, or examining the WAR file metadata (typically in MANIFEST.MF or version.properties within the deployed application)Affected if The installed version is exactly 6.1.1
-
Identify deployed application pathLocate the deployed Knowage web application directory or WAR file on the server (commonly found in application server directories like Tomcat's webapps/knowage or similar)Affected if The application is deployed at the /knowage context path
-
Test for CSRF protection on formsInspect HTML forms in the Knowage web interface (login, analytical drivers, and other forms) by viewing the page source. Check if each form includes a hidden CSRF token field or similar anti-CSRF mechanismAffected if Forms lack hidden CSRF token fields or any anti-CSRF token mechanism
-
Verify token validation on vulnerable endpointExamine the request/response behavior when sending requests to /knowage/restful-services/2.0/analyticalDrivers/ - check if the server validates any anti-CSRF token or origin/referer headerAffected if The endpoint accepts requests without requiring a valid anti-CSRF token or validating request origin headers
-
Check SameSite cookie configurationInspect the Set-Cookie headers and session cookie configuration in the Knowage application server settings or web.xml to see if SameSite attributes are configuredAffected if SameSite cookie attributes are not set or are set to 'None' without Secure flags
A user is affected if they are running Knowage version 6.1.1 AND the application forms lack anti-CSRF token protections AND the /knowage/restful-services/2.0/analyticalDrivers/ endpoint accepts requests without CSRF validation.
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 dataImplement anti-CSRF tokens on all forms and validate the Origin/Referer headers server-side. Additionally, configure SameSite cookie attributes to further mitigate CSRF risk.
- Consultation6.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,016.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12354 — 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-12354 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