dbcve.org
Release AutomationApplication · Broadcom

CVE-2014-8246

MEDIUM · 6.8 CVSS v2.0 Published 2014-12-16
Fix available
A fix is available. Upgrade to after 4.7.1 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges 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
Cross-site request forgery (CSRF) vulnerability in CA Release Automation (formerly iTKO LISA Release Automation) before 4.7.1 b448 allows remote attackers to hijack the authentication of unspecified victims via unknown 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

Cross-site request forgery (CSRF) vulnerability in CA Release Automation allows remote attackers to hijack authentication of unspecified victims. The vulnerability exists in versions prior to 4.7.1 b448, enabling attackers to trick authenticated users into executing unintended actions.

MitigationUpgrade CA Release Automation to version 4.7.1 b448 or later. Implement anti-CSRF tokens on all state-changing operations and validate the Origin/Referer headers.

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:<= 4.7.1

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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
    Check the application UI help/about section, or look in the installation directory for version metadata files, or query the management interface for build information
    Affected if Version is 4.7.1 or lower, or the build number is below b448
  2. Verify anti-CSRF token implementation
    Inspect the application's web form submissions and AJAX requests to see if a unique token is required for each state-changing operation (POST/PUT/DELETE requests)
    Affected if State-changing requests do not require a unique anti-CSRF token with each submission
  3. Check Origin/Referer header validation
    Review server-side code or configuration to determine if incoming requests are validated for proper Origin or Referer headers matching the expected domain
    Affected if The application does not validate Origin or Referer headers on state-changing operations

You are affected if your installed version is 4.7.1 b448 or lower AND your deployment lacks anti-CSRF tokens 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
Upgrade available Upgrade to a release after 4.7.1
Interim mitigation

Upgrade CA Release Automation to version 4.7.1 b448 or later. Implement anti-CSRF tokens on all state-changing operations and validate the Origin/Referer headers.

Fix this in Release Automation Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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