dbcve.org
Messaging Apache Kafka Distribution Schema RepositoryWeb server / proxy · Tibco

CVE-2018-12413

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 Schema repository server (tibschemad) component of TIBCO Software Inc.'s TIBCO Messaging - Apache Kafka Distribution - Schema Repository - Community Edition, and TIBCO Messaging - Apache Kafka Distribution - Schema Repository - Enterprise Edition contains a vulnerability which may allow an attacker to perform cross-site request forgery (CSRF) attacks. Affected releases are TIBCO Software Inc. TIBCO Messaging - Apache Kafka Distribution - Schema Repository - Community Edition: 1.0.0, and TIBCO Messaging - Apache Kafka Distribution - Schema Repository - Enterprise Edition: 1.0.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 · moderate confidence

Cross-site request forgery (CSRF) vulnerability in the tibschemad schema repository server component of TIBCO Messaging - Apache Kafka Distribution. The flaw allows attackers to craft malicious requests that can be executed by authenticated users without their consent, potentially leading to unauthorized schema modifications or administrative actions.

MitigationImplement anti-CSRF tokens for state-changing operations, configure SameSite cookie attributes, and validate Origin/Referer headers to prevent cross-site request forgery attacks.

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
Messaging Apache Kafka Distribution Schema RepositoryWeb server / proxy
Affected:= 1.0.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. Verify TIBCO Messaging Apache Kafka Distribution is installed
    Locate the TIBCO Kafka installation directory and identify the Schema Repository component (tibschemad). Common paths include /opt/tibco or the installation directory specified during setup.
    Affected if The TIBCO Messaging Apache Kafka Distribution Schema Repository component is not present on the system.
  2. Determine the Schema Repository version
    Check the installed version of the tibschemad component. Look for version information in the product manifest, about dialog, or version file within the Schema Repository installation directory.
    Affected if The installed version is exactly 1.0.0.
  3. Confirm the tibschemad service is running
    Check if the tibschemad process or service is active. On Linux, use 'ps aux | grep tibschemad' or 'systemctl status tibschemad'. On Windows, check running services or the process list.
    Affected if The tibschemad schema repository server is not running or not installed.
  4. Inspect web interface for anti-CSRF protection
    Access the schema repository web interface (typically on port 8080 or 8443) and examine whether state-changing operations (adding/modifying schemas, admin actions) require anti-CSRF tokens. Check the HTML forms for hidden token fields or examine API requests for token headers.
    Affected if State-changing requests do not require anti-CSRF tokens and no Origin/Referer header validation is performed on requests.

You are affected if TIBCO Messaging Apache Kafka Distribution Schema Repository version 1.0.0 is running with the tibschemad component enabled and without anti-CSRF token protection on state-changing operations.

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

Implement anti-CSRF tokens for state-changing operations, configure SameSite cookie attributes, and validate Origin/Referer headers to prevent cross-site request forgery attacks.

Fix this in Messaging Apache Kafka Distribution Schema Repository Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-12413 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-12413 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