dbcve.org
CWE-329Weakness · CWE-329

CVE-2024-56141

MEDIUM · 5.0 CVSS v3.1 Published 2026-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Minosoft is an open-source, multi-version Minecraft Java Edition client written in Kotlin. Starting in commit f1ae30e2b046a490026a8413b075685deb795122, the CryptManager  encryption routine ( CryptManager.kt ) initializes its AES cipher using an initialization vector (IV) that is set equal to the secret key rather than to a sufficiently random value. Because the IV is not random and is derived directly from the key, the encryption is vulnerable to chosen-ciphertext/chosen-plaintext attacks: an attacker who can submit specific messages for encryption can recover the secret key. This affects all versions supporting Minecraft protocol 1.7 and later. No patched version is available, and no known workarounds are available.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The CryptManager.kt encryption routine uses an initialization vector (IV) that is set equal to the secret key rather than a random value. This violates AES encryption best practices and makes the encryption vulnerable to chosen-ciphertext/chosen-plaintext attacks where an attacker can recover the secret key by submitting specific messages for encryption.

MitigationReplace the static IV derivation with proper random IV generation using a cryptographically secure random number generator, and ensure the IV is transmitted with the ciphertext per Minecraft protocol specifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate CryptManager.kt
    Search the codebase for the file CryptManager.kt, typically found in authentication, crypto, or security-related packages
    Affected if The file exists in the codebase - this indicates the affected component is present
  2. Find the AES encryption routine
    Open CryptManager.kt and locate methods that perform AES encryption (look for Cipher.getInstance, AES, or similar encryption calls)
    Affected if AES encryption is used in this file - the vulnerable code path exists here
  3. Inspect the IV derivation
    Within the encryption method, examine how the Initialization Vector (IV) is created - look for variables named 'iv', 'IV', or parameter passing to the Cipher init method
    Affected if The code creates or derives an IV - proceed to check how it is set
  4. Check if IV equals the secret key
    Compare the IV value to the secret key value - look for assignments like 'iv = secretKey', 'iv = key', or similar logic where the key is used directly as the IV
    Affected if The IV is set equal to or derived directly from the secret key - this is the vulnerable condition
  5. Verify random IV is not used
    Confirm there is no call to a secure random number generator (SecureRandom, SecureRandom.nextBytes, etc.) for generating the IV, and no IV prepended to the ciphertext output
    Affected if No random IV generation is implemented - the vulnerability is confirmed

If the initialization vector in CryptManager.kt is set equal to the secret key rather than being randomly generated, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace the static IV derivation with proper random IV generation using a cryptographically secure random number generator, and ensure the IV is transmitted with the ciphertext per Minecraft protocol specifications.

Recommended fix High confidence
  1. No remediation steps are available for this vulnerability.
  2. The project maintainers have not released a patch or identified any workaround.
  3. Monitor the project's GitHub repository for future security updates.
  4. Consider using an alternative Minecraft client until a fix is available.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-56141 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-56141 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data