Home/CVE/EnroCrypt is a Python module for encryption and hashing. Prior to version 1.1.4, EnroCrypt used the MD5 hashing algorith
CVE
↯ PDF report

CVE-2021-391822

EnroCrypt is a Python module for encryption and hashing. Prior to version 1.1.4, EnroCrypt used the MD5 hashing algorith

EnroCrypt is a Python module for encryption and hashing. Prior to version 1.1.4, EnroCrypt used the MD5 hashing algorithm in the hashing file. Beginners who are unfamiliar with hashes can face problems as MD5 is considered an insecure hashing algorithm.

The vulnerability is patched in v1.1.4 of the product. As a workaround, users can remove the MD5 hashing function from the file hashing.py.

HIGH · CVSS 7.5 EPSS 0.00544
EPSS exploitation odds0.54% · top 58%
Act now
  • Public exploit or PoC is available
  • CVSS base score ≥ 7.0
No Sigma yet — build one → YARA rules0
Look this up elsewhere - one-click external pivots
NVDCVE.orgCISAExploit-DBGitHub PoCVulnCheck KEVGreyNoise
▸ How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2021-39182, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
▣

Severity & exploitation scoring

View on NVD →
CVSS base score
7.5
HIGHCVSS v3.1 · [email protected]
EPSS exploitation probability
0.54%
Top 58%odds of exploitation in the next 30 days
CVSS metric silhouette
VectorComplexityPrivilegesInteractionScopeConfidentialityIntegrityAvailability
shape grows toward worst-case
SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network Adjacent Local Physical
Attack Complexity
Low High
Privileges Required
None Low High
User Interaction
None Required
Scope
Unchanged Changed
Impact - what breaks
Confidentiality
None Low High
Integrity
None Low High
Availability
None Low High
VECTORCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Lifecycle
  1. 08 Nov 2021Published to NVD
  2. 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
→
⚠

Public Exploits & PoCs

2
These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users mark whether it works, rate 1-10, and can report malware with a required reason that becomes a public comment.
poc Public PoC (nvd-reference)↗ date unknown
⋮
Vote & rate
Report or claim
⚠ Report this PoC

Becomes a public comment attributed as First L. (never full last name). Don't include private info. Rate-limited: 5/hour.

Works? no reports yet
Rating -
poc github.com · e652d56ac60eadfc26489ab83927af13a9b9d8ce↗ github.com
⋮
Vote & rate
Report or claim
⚠ Report this PoC

Becomes a public comment attributed as First L. (never full last name). Don't include private info. Rate-limited: 5/hour.

Works? no reports yet
Rating -
◆

ATT&CK techniques

3

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.

T1110 · Brute Force2× T1110.002 · Password Cracking T1553.002 · Code Signing
▤ Build a SIEM detection for these techniques
▤

CAPEC attack patterns

12

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-112 · Brute Force CAPEC-CAPEC-192 · Protocol Analysis CAPEC-CAPEC-20 · Encryption Brute Forcing CAPEC-CAPEC-459 · Creating a Rogue Certification Authority Certificate CAPEC-CAPEC-461 · Web Services API Signature Forgery Leveraging Hash Function Extension Weakness CAPEC-CAPEC-473 · Signature Spoof CAPEC-CAPEC-475 · Signature Spoofing by Improper Validation CAPEC-CAPEC-55 · Rainbow Table Password Cracking CAPEC-CAPEC-608 · Cryptanalysis of Cellular Encryption CAPEC-CAPEC-614 · Rooting SIM Cards CAPEC-CAPEC-68 · Subvert Code-signing Facilities CAPEC-CAPEC-97 · Cryptanalysis
⬡

Weakness Classification

CWE-326Inadequate Encryption Strength
CWE-327Use of a Broken or Risky Cryptographic Algorithm
CWE-328Use of Weak Hash
CWE-916Use of Password Hash With Insufficient Computational Effort
▤

Affected Products & Versions

1
enrocrypt project enrocrypt< 1.1.4
▤

Affected Packages

1
Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
PyPI enrocrypt HIGH fixed in 1.1.4
▤

Related CVEs

8
CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.
CVE-2001-1546 Pathways Homecare 6.5 uses weak encryption for user names and passwords, which a... 1 same CWE-326 HIGH CVE-2002-1682 NewsReactor 1.0 uses a weak encryption scheme, which could allow local users to ... same CWE-326 MEDIUM CVE-2002-1697 Electronic Code Book (ECB) mode in VTun 2.0 through 2.5 uses a weak encryption a... same CWE-326 HIGH CVE-2002-1739 Alt-N Technologies Mdaemon 5.0 through 5.0.6 uses a weak encryption algorithm to... same CWE-326 MEDIUM CVE-1999-0007 Information from SSL-encrypted sessions via PKCS #1. same CWE-327 CVE-2002-2058 TeeKai Tracking Online 1.0 uses weak encryption of web usage statistics in data/... same CWE-327 HIGH CVE-2005-2946 The default configuration on OpenSSL before 0.9.8 uses MD5 for creating message ... same CWE-327 HIGH CVE-2005-4860 Spectrum Cash Receipting System before 6.504 uses weak cryptography (static subs... same CWE-327 HIGH
🔗

References & Sources

1
Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
https://github.com/Morgan-Phoenix/EnroCrypt/security/advisories/GHSA-35m5-8cvj-8783
Third Party Advisory
◈SOC and Response
◆Detection Engineering
◎Threat Hunting
▲Red Team and Pentest
■Compliance and GRC
◯About
threatengine.sh