ActivespacesApplication · Tibco

CVE-2018-12411

HIGH · 8.8 CVSS v3.0 Published 2018-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
The administrative daemon (tibdgadmind) of TIBCO Software Inc.'s TIBCO ActiveSpaces - Community Edition, TIBCO ActiveSpaces - Developer Edition, and TIBCO ActiveSpaces - Enterprise Edition contains a vulnerability which may allow an attacker to perform cross-site request forgery (CSRF) attacks. Affected releases are TIBCO Software Inc.'s TIBCO ActiveSpaces - Community Edition: 3.3.0; 3.4.0; 3.5.0, TIBCO ActiveSpaces - Developer Edition: 3.0.0; 3.1.0; 3.3.0; 3.4.0; 3.5.0, and TIBCO ActiveSpaces - Enterprise Edition: 3.0.0; 3.1.0; 3.2.0; 3.3.0; 3.4.0; 3.5.0.

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 confidence

TIBCO ActiveSpaces administrative daemon (tibdgadmind) contains a cross-site request forgery (CSRF) vulnerability that allows attackers to trick authenticated administrators into unknowingly executing malicious administrative actions. The high CVSS score (8.8) reflects the potential for full compromise of administrative functions.

MitigationApply vendor-provided patches for affected ActiveSpaces versions. Until patched, administrators should avoid the web administrative interface and consider network isolation of the administrative daemon.

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
ActivespacesApplication
Affected:= 3.0.0= 3.1.0= 3.2.0= 3.3.0= 3.4.0= 3.5.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed TIBCO ActiveSpaces version
    Locate the ActiveSpaces installation directory and check the version. Common locations include /opt/tibco/as or C:\tibco\as. Look for version files or use tibdgadmind -version if available.
    Affected if Installed version is 3.0.0, 3.1.0, 3.2.0, 3.3.0, 3.4.0, or 3.5.0
  2. Verify administrative daemon (tibdgadmind) is running
    Check for running processes: on Linux use 'ps -ef | grep tibdgadmind', on Windows use Task Manager or 'tasklist | findstr tibdgadmind'. Also check if the daemon listens on network ports (default admin port is 8080 or 8443).
    Affected if The tibdgadmind process is running and accessible on a network port
  3. Confirm web administrative interface is enabled
    Examine the tibdgadmind configuration file (typically tibdgadmind.xml or admind.cfg in the config directory) for web server settings. Look for HTTP/HTTPS listener configurations.
    Affected if Web administrative interface is enabled and exposed (not limited to localhost)
  4. Check for active administrative sessions
    Review access logs for the administrative daemon web interface if accessible. Look for unusual request patterns that may indicate CSRF exploitation.
    Affected if Administrative actions can be triggered via web requests while administrator is authenticated

A user is affected if they have TIBCO ActiveSpaces version 3.0.0 through 3.5.0 running with the tibdgadmind web administrative interface accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches for affected ActiveSpaces versions. Until patched, administrators should avoid the web administrative interface and consider network isolation of the administrative daemon.

Fix this in Activespaces Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-12411 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-12411 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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