dbcve.org
Release AutomationApplication · Broadcom

CVE-2015-8699

MEDIUM · 6.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 →
68/100
Remediation priority · Elevated
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
Multiple cross-site scripting (XSS) vulnerabilities in 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 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors.

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

Multiple reflected cross-site scripting (XSS) vulnerabilities exist in CA Release Automation web interface, allowing remote unauthenticated attackers to inject arbitrary JavaScript or HTML via unspecified input vectors. The vulnerabilities affect versions 5.0.2 prior to 5.0.2-227, 5.5.1 prior to 5.5.1-1616, 5.5.2 prior to 5.5.2-434, and 6.1.0 prior to 6.1.0-1026. Successful exploitation enables session hijacking, credential theft, or malicious actions in the context of authenticated users.

MitigationApply the vendor-supplied patches (5.0.2-227, 5.5.1-1616, 5.5.2-434, or 6.1.0-1026 or later) to all affected CA Release Automation installations, followed by input validation and output encoding review of custom plugins.

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 if CA Release Automation is installed
    Check common installation directories for CA Release Automation: Windows default is C:\Program Files\CA\ReleaseAutomation or C:\Program Files (x86)\CA\ReleaseAutomation. On Linux/Unix, look under /opt/CA/ or /opt/ releaseautomation. Also check for running processes named 'nolio' or 'ra' in task manager or process list.
    Affected if CA Release Automation software is present on the system
  2. Determine the installed version
    Locate the version file or About page. On Windows, check <install_dir>\server\conf\version.properties or similar. In the web interface, log in and navigate to Help > About or Administration > System Information. The version is typically displayed in format like 5.5.2-xxx or 6.1.0-xxx.
    Affected if The displayed version matches one of the affected ranges: 5.0.2 to 5.0.2-226, 5.5.1 to 5.5.1-1615, 5.5.2 to 5.5.2-433, or 6.1.0 to 6.1.0-1025
  3. Confirm the web interface is accessible
    Verify the Release Automation web interface is running and reachable. Default ports are 8080 or 8443. Access the login page via browser at http://<hostname>:8080/ or https://<hostname>:8443/. Check if the service is running via Windows Services or Linux service command.
    Affected if The web interface is exposed and accepts connections, making the XSS vector viable for attackers
  4. Check the applied patch level
    Review the full version string including the build/patch number. Compare against the fixed versions: 5.0.2-227 or higher, 5.5.1-1616 or higher, 5.5.2-434 or higher, 6.1.0-1026 or higher. This information appears in the version.properties file or the web UI About page.
    Affected if The version number is below these thresholds, indicating the XSS patches have not been applied

You are affected if CA Release Automation is installed and the version falls within any of the four vulnerable ranges without the corresponding patch number applied.

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

Apply the vendor-supplied patches (5.0.2-227, 5.5.1-1616, 5.5.2-434, or 6.1.0-1026 or later) to all affected CA Release Automation installations, followed by input validation and output encoding review of custom plugins.

Fix this in Release Automation Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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