dbcve.org
Release AutomationApplication · Broadcom

CVE-2018-15691

CRITICAL · 9.8 CVSS v3.0 Published 2018-08-30
Fix available
A fix is available. Upgrade to 6.3.0.9945 / 6.4.0.10119 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
Insecure deserialization of a specially crafted serialized object, in CA Release Automation 6.5 and earlier, allows attackers to potentially execute arbitrary code.

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
How this class of weakness works · CWE-502

The application rebuilds objects from attacker-supplied serialized data, and the act of rebuilding can trigger dangerous code paths. In many runtimes this leads straight to remote code execution. The durable fix is to avoid deserializing untrusted input — or to use a strict, type-limited format with integrity checks.

General guidance for the deserialization of untrusted data class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Release AutomationApplication
Affected:>= 6.3, < 6.3.0.9945>= 6.4, < 6.4.0.10119>= 6.5, < 6.5.0.10080

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

dbcve · scoped
Upgrade available Upgrade to 6.3.0.9945 / 6.4.0.10119 / 6.5.0.10080 or later
Fixed in 6.3.0.99456.4.0.101196.5.0.10080
Vendor patch support.ca.com →
Recommended fix High confidence

6.3.0.9945 or later for 6.3.x; 6.4.0.10119 or later for 6.4.x; 6.5.0.10080 or later for 6.5.x

  1. 1. Identify the currently installed CA Release Automation version from the administration console or by checking the product version.
  2. 2. Determine which version branch your installation belongs to (6.3.x, 6.4.x, or 6.5.x).
  3. 3. For 6.3.x branch: Upgrade to version 6.3.0.9945 or later.
  4. 4. For 6.4.x branch: Upgrade to version 6.4.0.10119 or later.
  5. 5. For 6.5.x branch: Upgrade to version 6.5.0.10080 or later.
  6. 6. Obtain the update from CA Support or through the official vendor patch channel at https://support.ca.com/us/product-content/recommended-reading/security-notices/ca20180829-03--security-notice-for-ca-release-automation.html
  7. 7. Apply the upgrade following the standard CA Release Automation upgrade documentation.
  8. 8. After upgrade, verify the new version is installed and test critical workflows to ensure functionality.
Caveat Review CA Release Automation release notes for your specific version upgrade to check for any compatibility or configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,550. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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