CVE-2020-27146
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 · uneditedThe Core component of TIBCO Software Inc.'s TIBCO iProcess Workspace (Browser) contains a vulnerability that theoretically allows an unauthenticated attacker with network access to execute a Cross Site Request Forgery (CSRF) attack on the affected system. A successful attack using this vulnerability requires human interaction from an authenticated user other than the attacker. Affected releases are TIBCO Software Inc.'s TIBCO iProcess Workspace (Browser): versions 11.6.0 and below.
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 confidenceCSRF vulnerability in TIBCO iProcess Workspace (Browser) allows an unauthenticated attacker with network access to trick an authenticated user into executing unintended actions via malicious requests, exploiting the application's lack of proper CSRF token validation or SameSite cookie attributes.
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<= 11.6.0CVSS 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.1/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.
-
Identify installed version of TIBCO iProcess Workspace BrowserLocate the installed TIBCO iProcess Workspace Browser application and determine its exact version number through the product's about dialog, installation directory, or version reporting mechanismAffected if The installed version is 11.6.0 or any earlier version (versions <= 11.6.0)
-
Inspect SameSite cookie configurationUse browser developer tools or a proxy to intercept HTTP responses from the iProcess Workspace Browser application and examine Set-Cookie headers for the SameSite attributeAffected if Cookies sent by the application lack the SameSite attribute or have it set to a weak value such as 'None' without Secure flag, or the attribute is missing entirely
-
Verify CSRF token presence in state-changing requestsCapture a state-changing operation (such as form submissions or configuration changes) using a proxy or browser dev tools and inspect whether the request includes a CSRF token or anti-CSRF token parameterAffected if State-changing requests do not contain a valid CSRF token and rely only on session authentication without additional token validation
-
Confirm network accessibilityDetermine if the iProcess Workspace Browser interface is accessible over the network to unauthenticated attackersAffected if The application is exposed to network access without proper authentication barriers, allowing unauthenticated attackers to craft malicious requests
You are affected if your TIBCO iProcess Workspace Browser version is 11.6.0 or earlier AND the application lacks SameSite cookie attributes or proper CSRF token validation for state-changing operations.
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 for state-changing operations and configure SameSite cookie attributes; apply vendor patch when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27146 — 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-2020-27146 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