# CVE-2021-41096: Use of a Broken or Risky Cryptographic Algorithm in com.mayank.rucky

> An attacker can exploit weak RSA encryption in the Rucky Android app to potentially decrypt sensitive data or bypass security features.

- **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:** 27 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-32m7-456v-wgfw

## What is CVE-2021-41096?

CVE-2021-41096 is a high-severity vulnerability in mayankmetha Rucky, published on 27 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rucky is a USB HID Rubber Ducky Launch Pad for Android. Versions 2.2 and earlier for release builds and versions 425 and earlier for nightly builds suffer from use of a weak cryptographic algorithm (RSA/ECB/PKCS1Padding). The issue will be patched in v2.3 for release builds and 426 onwards for nightly builds. As a workaround, one may disable an advance security feature if not required.

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

## Which versions are affected by CVE-2021-41096?

It affects 1 product.


Products: Rucky Project Rucky.

## How do I fix CVE-2021-41096?

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

## Is CVE-2021-41096 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41096 and fix it if it is affected.

What it is: CVE-2021-41096 is a high-severity vulnerability in mayankmetha Rucky, published on 27 Sep 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-2021-41096 in the wild and no public exploit code.

Affected product: mayankmetha Rucky. 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-2021-41096/ (Markdown: https://insights.sbomify.com/CVE-2021-41096/index.md)
```

## Sources

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

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