LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Rucky for Android used a weak cryptographic mode in affected builds. The main business risk is exposure of protected information, not service outage or unauthorized modification. The public record names fixed release and nightly versions, but does not describe active exploitation.

Executive priority

Treat this as a targeted high-priority fix where Rucky is present. It is not broad enterprise infrastructure exposure, but affected devices may put confidential data at risk if left on vulnerable builds.

Technical view

CVE-2021-41096 is CWE-327 in com.mayank.rucky. Release builds 2.2 and earlier, and nightly builds 425 and earlier, used RSA/ECB/PKCS1Padding. CVSS 3.1 is 7.5 with network attack vector and high confidentiality impact only.

Likely exposure

Exposure is limited to environments where Rucky is installed on Android devices in release versions below 2.3 or nightly versions 425 and earlier. The source bundle provides no CPEs or enterprise deployment indicators.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The CVSS vector indicates low-complexity, unauthenticated network exposure, but source details are insufficient to describe a specific attack path.

Researcher notes

The public facts identify the weak algorithm and version boundaries, but not the protected data, precise feature flow, or exploit evidence. Review the advisory and patch commit for implementation context without assuming broader product impact.

Mitigation direction

  • Upgrade Rucky release builds to version 2.3 or later.
  • Upgrade Rucky nightly builds to build 426 or later.
  • If upgrade is delayed, disable the advanced security feature if not required.
  • Monitor the GitHub advisory for any revised vendor guidance.

Validation and detection

  • Inventory Android devices for installed Rucky versions.
  • Confirm release builds are version 2.3 or later.
  • Confirm nightly builds are build 426 or later.
  • Check whether the advanced security feature remains enabled on affected builds.
  • Record remediation against CVE-2021-41096 and GHSA-32m7-456v-wgfw.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-327: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-41096 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-41096Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
mayankmethaRucky< 2.3Listed
Weakness

CWE details

CWE-327

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-327 · source CWE mapping

Use of a Broken or Risky Cryptographic Algorithm

Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs