Menu

Star on GitHub · 3.2k

CVE-2019-5295

6.4 · MEDIUM

Huawei Honor V10 smartphones versions earlier than Berkeley-AL20 9.0.0.125(C00E125R2P14T8) have an authorization bypass vulnerability.

Published Jun 6, 2019EPSS 0.22%

Overview

CVE-2019-5295 is a medium-severity vulnerability. It was published on June 6, 2019 and has a CVSS 3.0 base score of 6.4 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 6.4, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

Huawei Honor V10 smartphones versions earlier than Berkeley-AL20 9.0.0.125(C00E125R2P14T8) have an authorization bypass vulnerability. Due to improper authorization implementation logic, attackers can bypass certain authorization scopes of smart phones by performing specific operations. This vulnerability can be exploited to perform operations beyond the scope of authorization.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2019-5295?

CVE-2019-5295 is a medium-severity vulnerability. It was published on June 6, 2019 and has a CVSS 3.0 base score of 6.4 (MEDIUM).

How severe is CVE-2019-5295?

This vulnerability has a CVSS 3.0 base score of 6.4, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2019-5295?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2019-5295?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2019-5295 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2019

View all