What is the severity of CVE-2024-51530?

CVE-2024-51530 is considered a high-severity vulnerability that may compromise service confidentiality.

How do I fix CVE-2024-51530?

To fix CVE-2024-51530, users should update to the patched versions provided by Huawei for affected devices.

Which devices are affected by CVE-2024-51530?

CVE-2024-51530 affects Huawei devices running Emui versions 12.0.0, 13.0.0, 14.0.0 and HarmonyOS versions 2.0.0 through 4.2.0.

What type of vulnerability is CVE-2024-51530?

CVE-2024-51530 is categorized as a LaunchAnywhere vulnerability in the account module.

What can happen if CVE-2024-51530 is exploited?

Exploitation of CVE-2024-51530 could lead to a breach of service confidentiality on affected devices.

Vulnerability/
CVE-2024-51530

medium

6.6

CWE

5/11/2024

7/11/2024

CVE-2024-51530: Input Validation

First published: Tue Nov 05 2024(Updated: )

LaunchAnywhere vulnerability in the account module Impact: Successful exploitation of this vulnerability may affect service confidentiality.

Credit: psirt@huawei.com

Affected Software	Affected Version	How to fix
Huawei Emui	=12.0.0
Huawei Emui	=13.0.0
Huawei Emui	=14.0.0
Huawei Harmonyos	=2.0.0
Huawei Harmonyos	=2.1.0
Huawei Harmonyos	=3.0.0
Huawei Harmonyos	=3.1.0
Huawei Harmonyos	=4.0.0
Huawei Harmonyos	=4.2.0

Never miss a vulnerability like this again

Reference Links

https://consumer.huawei.com/en/support/bulletin/2024/11/

Frequently Asked Questions

What is the severity of CVE-2024-51530?
CVE-2024-51530 is considered a high-severity vulnerability that may compromise service confidentiality.
How do I fix CVE-2024-51530?
To fix CVE-2024-51530, users should update to the patched versions provided by Huawei for affected devices.
Which devices are affected by CVE-2024-51530?
CVE-2024-51530 affects Huawei devices running Emui versions 12.0.0, 13.0.0, 14.0.0 and HarmonyOS versions 2.0.0 through 4.2.0.
What type of vulnerability is CVE-2024-51530?
CVE-2024-51530 is categorized as a LaunchAnywhere vulnerability in the account module.
What can happen if CVE-2024-51530 is exploited?
Exploitation of CVE-2024-51530 could lead to a breach of service confidentiality on affected devices.

agent/weakness
agent/references
agent/description
agent/type
agent/first-publish-date
agent/author
agent/event
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/last-modified-date
agent/severity
agent/softwarecombine
agent/tags
collector/mitre-cve
source/MITRE
agent/source
vendor/huawei
canonical/huawei emui
version/huawei emui/12.0.0
version/huawei emui/13.0.0
version/huawei emui/14.0.0
canonical/huawei harmonyos
version/huawei harmonyos/2.0.0
version/huawei harmonyos/2.1.0
version/huawei harmonyos/3.0.0
version/huawei harmonyos/3.1.0
version/huawei harmonyos/4.0.0
version/huawei harmonyos/4.2.0

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-2024-51530?
CVE-2024-51530 is considered a high-severity vulnerability that may compromise service confidentiality.
How do I fix CVE-2024-51530?
To fix CVE-2024-51530, users should update to the patched versions provided by Huawei for affected devices.
Which devices are affected by CVE-2024-51530?
CVE-2024-51530 affects Huawei devices running Emui versions 12.0.0, 13.0.0, 14.0.0 and HarmonyOS versions 2.0.0 through 4.2.0.
What type of vulnerability is CVE-2024-51530?
CVE-2024-51530 is categorized as a LaunchAnywhere vulnerability in the account module.
What can happen if CVE-2024-51530 is exploited?
Exploitation of CVE-2024-51530 could lead to a breach of service confidentiality on affected devices.