dbcve.org
Tidal Workload AutomationApplication · Dillonkane

CVE-2019-6689

HIGH · 7.8 CVSS v3.0 Published 2019-04-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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
An issue was discovered in Dillon Kane Tidal Workload Automation Agent 3.2.0.5 (formerly known as Cisco Workload Automation or CWA). The Enterprise Scheduler for AIX allows local users to gain privileges via Command Injection in crafted Tidal Job Buffers (TJB) parameters. NOTE: this vulnerability exists because the CVE-2014-3272 solution did not address AIX operating systems.

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

Command injection vulnerability in Dillon Kane Tidal Workload Automation Agent 3.2.0.5 (formerly Cisco Workload Automation) allows local users to escalate privileges by injecting commands through crafted Tidal Job Buffer (TJB) parameters in the Enterprise Scheduler for AIX. This vulnerability is a bypass of the CVE-2014-3272 fix, which only addressed non-AIX platforms.

MitigationImplement strict input validation and sanitization on all TJB parameters to prevent command injection, and apply any vendor-provided patches for this vulnerability. Restrict local user access to the scheduler following least-privilege principles.

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
Tidal Workload AutomationApplication
Affected:= 3.2.0.5

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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 Tidal Workload Automation Agent is installed
    Check for the presence of Tidal Workload Automation (formerly Cisco Workload Automation) on the system. Look for installation directories, services, or processes named 'tidal', 'twa', or 'cwa'. On AIX, check for files in /opt/tidal or similar installation paths.
    Affected if The product is not installed or is a different version.
  2. Confirm the exact version is 3.2.0.5
    Identify the installed version of the Tidal Workload Automation Agent. Check version files, executable version info, or use command-line tools such as 'lsattr -E -l agent_name' or 'rpm -qi tidal-agent' if using package management. Compare against the affected version 3.2.0.5.
    Affected if The installed version is not exactly 3.2.0.5.
  3. Confirm the platform is AIX running Enterprise Scheduler
    Verify the operating system is AIX and that the Enterprise Scheduler for AIX component is in use. Check OS version with 'oslevel' and confirm Tidal components are running on AIX infrastructure.
    Affected if The system is not running AIX or does not use Enterprise Scheduler for AIX.
  4. Check for Tidal Job Buffer (TJB) parameter accessibility
    Determine if users have the ability to submit or modify Tidal Job Buffer (TJB) parameters within the scheduler. Review job submission interfaces, configuration files, or API access that accepts TJB input.
    Affected if Users cannot access or modify TJB parameters in the scheduler.

A system is affected if it runs Tidal Workload Automation Agent version 3.2.0.5 on AIX with Enterprise Scheduler and users can submit or modify Tidal Job Buffer (TJB) parameters.

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 strict input validation and sanitization on all TJB parameters to prevent command injection, and apply any vendor-provided patches for this vulnerability. Restrict local user access to the scheduler following least-privilege principles.

Fix this in Tidal Workload Automation 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-2019-6689 — 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-2019-6689 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