# CVE-2020-1826: Weak cryptography in Honor Magic2

> An attacker with root permissions can exploit weak encryption to leak information from Huawei Honor Magic2 devices.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-253g-4jm3-6p9v

## What is CVE-2020-1826?

CVE-2020-1826 is a medium-severity vulnerability in Huawei Honor Magic2, published on 9 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei Honor Magic2 mobile phones with versions earlier than 10.0.0.175(C00E59R2P11) have an information leak vulnerability. Due to a module using weak encryption tool, an attacker with the root permission may exploit the vulnerability to obtain some information.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2020-1826?

It affects 1 product.


Products: Huawei Honor Magic2 Firmware.

## How do I fix CVE-2020-1826?

No fix has been published for CVE-2020-1826 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-1826 being exploited?

There is no known exploitation of CVE-2020-1826 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1826 and fix it if it is affected.

What it is: CVE-2020-1826 is a medium-severity vulnerability in Huawei Honor Magic2, published on 9 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-1826 in the wild and no public exploit code.

Affected product: Huawei Honor Magic2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-1826/ (Markdown: https://insights.sbomify.com/CVE-2020-1826/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-1826
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-1826
- OSV: https://osv.dev/vulnerability/CVE-2020-1826

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-1826/
Summaries are generated and may contain mistakes; the official description above is the record.