dbcve.org
Release AutomationApplication · Broadcom

CVE-2015-8698

HIGH · 7.1 CVSS v3.0 Published 2016-06-29
Fix available
A fix is available. Upgrade to 5.0.2-227 / 5.5.1-1616 or later.
See remediation →
73/100
Remediation priority · Elevated
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
CA Release Automation (formerly LISA Release Automation) 5.0.2 before 5.0.2-227, 5.5.1 before 5.5.1-1616, 5.5.2 before 5.5.2-434, and 6.1.0 before 6.1.0-1026 allows remote attackers to read arbitrary files or cause a denial of service via a request containing an XML external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.

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

CA Release Automation contains an XML External Entity (XXE) vulnerability allowing remote attackers to read arbitrary files from the server or cause denial of service by sending requests with specially crafted XML containing external entity declarations and entity references.

MitigationUpgrade to the fixed versions (5.0.2-227, 5.5.1-1616, 5.5.2-434, or 6.1.0-1026 or later) which patch the XXE vulnerability, or disable external entity processing in the XML parser configuration.

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
Release AutomationApplication
Affected:>= 5.0.2, < 5.0.2-227>= 5.5.1, < 5.5.1-1616>= 5.5.2, < 5.5.2-434>= 6.1.0, < 6.1.0-1026

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
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 the installed Release Automation version
    Locate the version information in the product's About page, installation directory, or version file (commonly found in the installation root or in product-specific metadata files). Compare the version string to the affected ranges: 5.0.2 through 5.0.2-226, 5.5.1 through 5.5.1-1615, 5.5.2 through 5.5.2-433, or 6.1.0 through 6.1.0-1025.
    Affected if The installed version falls within any of these ranges: >= 5.0.2 and < 5.0.2-227; >= 5.5.1 and < 5.5.1-1616; >= 5.5.2 and < 5.5.2-434; >= 6.1.0 and < 6.1.0-1026.
  2. Determine if XML import or integration features are enabled
    Review the application configuration and enabled modules to identify if XML import, web services, or integration endpoints that accept XML input are active.
    Affected if XML processing features, integration endpoints, or data import functions that handle XML documents are enabled and accessible.
  3. Verify XML parser configuration
    Inspect the XML parser or application server configuration files for settings related to external entity processing. Look for parser configurations that allow external entity resolution.
    Affected if The XML parser is configured to permit external entity processing or DTD processing is not explicitly disabled.
  4. Check for exposed XML-handling endpoints
    Identify web endpoints, APIs, or services that accept XML payloads. These typically include import functions, webhook receivers, or integration interfaces.
    Affected if Publicly or internally accessible endpoints accept XML input without documented XXE protections.

The environment is affected if the installed Release Automation version falls within any of the four vulnerable version ranges AND the application processes XML input through enabled features or endpoints.

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
Upgrade available Upgrade to 5.0.2-227 / 5.5.1-1616 / 5.5.2-434 or later
Fixed in 5.0.2-2275.5.1-16165.5.2-434
Interim mitigation

Upgrade to the fixed versions (5.0.2-227, 5.5.1-1616, 5.5.2-434, or 6.1.0-1026 or later) which patch the XXE vulnerability, or disable external entity processing in the XML parser configuration.

Fix this in Release Automation Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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