What is the severity of CVE-2024-38499?

CVE-2024-38499 is classified as a high-severity vulnerability due to the risk of exposing critical encryption keys.

How do I fix CVE-2024-38499?

To fix CVE-2024-38499, ensure that only admin or root users are allowed to use the CAF CLI and SD_ACMD CLI for encryption.

Who is affected by CVE-2024-38499?

CVE-2024-38499 affects non-admin and non-root users of CA Client Automation who can access encryption functionalities.

What is the impact of CVE-2024-38499?

The impact of CVE-2024-38499 is that it allows unauthorized users to exploit stored credentials by accessing critical encryption keys.

Is there a workaround for CVE-2024-38499?

There is currently no documented workaround for CVE-2024-38499 other than applying the appropriate permissions to CLI access.

Vulnerability/
CVE-2024-38499

high

8.8

CWE

269 276

17/12/2024

19/12/2024

CVE-2024-38499: Improper Privilege Management Vulnerability in CA Client Automation 14.5

First published: Tue Dec 17 2024(Updated: )

CA Client Automation (ITCM) allows non-admin/non-root users to encrypt a string using CAF CLI and SD_ACMD CLI. This would allow the non admin user to access the critical encryption keys which further causes the exploitation of stored credentials. This fix doesn't allow a non-admin/non-root user to execute "caf encrypt"/"sd_acmd encrypt" commands.

Credit: secure@symantec.com

Affected Software	Affected Version	How to fix
Broadcom Client Automation

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2024-38499?
CVE-2024-38499 is classified as a high-severity vulnerability due to the risk of exposing critical encryption keys.
How do I fix CVE-2024-38499?
To fix CVE-2024-38499, ensure that only admin or root users are allowed to use the CAF CLI and SD_ACMD CLI for encryption.
Who is affected by CVE-2024-38499?
CVE-2024-38499 affects non-admin and non-root users of CA Client Automation who can access encryption functionalities.
What is the impact of CVE-2024-38499?
The impact of CVE-2024-38499 is that it allows unauthorized users to exploit stored credentials by accessing critical encryption keys.
Is there a workaround for CVE-2024-38499?
There is currently no documented workaround for CVE-2024-38499 other than applying the appropriate permissions to CLI access.

agent/title
agent/description
agent/type
agent/first-publish-date
agent/author
agent/event
agent/severity
agent/weakness
collector/nvd-api
source/NVD
agent/last-modified-date
agent/references
collector/mitre-cve
source/MITRE
agent/trending
agent/source
agent/softwarecombine
agent/tags
agent/guess-ai
agent/software-canonical-lookup
agent/software-canonical-lookup-request
vendor/ca
canonical/broadcom client automation

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.