What is the severity of CVE-2018-15691?

CVE-2018-15691 is considered a high severity vulnerability due to its potential for arbitrary code execution.

How do I fix CVE-2018-15691?

To fix CVE-2018-15691, upgrade to CA Release Automation version 6.6 or later.

What systems are affected by CVE-2018-15691?

CVE-2018-15691 affects CA Release Automation versions 6.5 and earlier.

What type of vulnerability is CVE-2018-15691?

CVE-2018-15691 is classified as an insecure deserialization vulnerability.

Can CVE-2018-15691 lead to data breaches?

Yes, exploiting CVE-2018-15691 could potentially allow attackers to execute arbitrary code, leading to data breaches.

Vulnerability/
CVE-2018-15691

critical

9.8

CWE

502

30/8/2018

16/9/2024

CVE-2018-15691

First published: Thu Aug 30 2018(Updated: )

Insecure deserialization of a specially crafted serialized object, in CA Release Automation 6.5 and earlier, allows attackers to potentially execute arbitrary code.

Credit: vuln@ca.com

Affected Software	Affected Version	How to fix
Broadcom Release Automation	>=6.3<6.3.0.9945
Broadcom Release Automation	>=6.4<6.4.0.10119
Broadcom Release Automation	>=6.5<6.5.0.10080

Remedy

https://support.ca.com/us/product-content/recommended-reading/security-notices/ca20180829-03--security-notice-for-ca-release-automation.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-15691?
CVE-2018-15691 is considered a high severity vulnerability due to its potential for arbitrary code execution.
How do I fix CVE-2018-15691?
To fix CVE-2018-15691, upgrade to CA Release Automation version 6.6 or later.
What systems are affected by CVE-2018-15691?
CVE-2018-15691 affects CA Release Automation versions 6.5 and earlier.
What type of vulnerability is CVE-2018-15691?
CVE-2018-15691 is classified as an insecure deserialization vulnerability.
Can CVE-2018-15691 lead to data breaches?
Yes, exploiting CVE-2018-15691 could potentially allow attackers to execute arbitrary code, leading to data breaches.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
agent/weakness
agent/author
agent/remedy
agent/severity
agent/tags
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
vendor/broadcom
canonical/broadcom release automation
version/broadcom release automation/6.3
version/broadcom release automation/6.4
version/broadcom release automation/6.5

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2018-15691?
CVE-2018-15691 is considered a high severity vulnerability due to its potential for arbitrary code execution.
How do I fix CVE-2018-15691?
To fix CVE-2018-15691, upgrade to CA Release Automation version 6.6 or later.
What systems are affected by CVE-2018-15691?
CVE-2018-15691 affects CA Release Automation versions 6.5 and earlier.
What type of vulnerability is CVE-2018-15691?
CVE-2018-15691 is classified as an insecure deserialization vulnerability.
Can CVE-2018-15691 lead to data breaches?
Yes, exploiting CVE-2018-15691 could potentially allow attackers to execute arbitrary code, leading to data breaches.