# CVE-2020-25493: Weak cryptography in n/a

> An attacker can eavesdrop on network traffic and decrypt data using a hardcoded XOR key in the Oclean mobile application.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2021
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-mf96-wwv9-c857

## What is CVE-2020-25493?

CVE-2020-25493 is a high-severity vulnerability in n/a, published on 11 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Oclean Mobile Application 2.1.2 communicates with an external website using HTTP so it is possible to eavesdrop the network traffic. The content of HTTP payload is encrypted using XOR with a hardcoded key, which allows for the possibility to decode the traffic.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Oclean Oclean.

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

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

## Is CVE-2020-25493 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25493 is a high-severity vulnerability in n/a, published on 11 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-25493 in the wild and no public exploit code.

Affected product: n/a. 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-25493/ (Markdown: https://insights.sbomify.com/CVE-2020-25493/index.md)
```

## Sources

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

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