What is CVE-2021-39182?

CVE-2021-39182 is a high-severity use of a broken or risky cryptographic algorithm vulnerability in enrocrypt (pip), affecting versions < 1.1.4. It is fixed in 1.1.4. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.

How severe is CVE-2021-39182?

CVE-2021-39182 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of enrocrypt are affected by CVE-2021-39182?

enrocrypt (pip) versions < 1.1.4 is affected.

Is there a fix for CVE-2021-39182?

Yes. CVE-2021-39182 is fixed in 1.1.4. Upgrade to this version or later.

Is CVE-2021-39182 exploitable, and should I be worried?

Whether CVE-2021-39182 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2021-39182 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2021-39182?

Upgrade enrocrypt to 1.1.4 or later.

CVE-2021-39182 in enrocrypt

Q: How severe is CVE-2021-39182?

CVE-2021-39182 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of enrocrypt are affected by CVE-2021-39182?

enrocrypt (pip) versions < 1.1.4 is affected.

Q: Is there a fix for CVE-2021-39182?

Yes. CVE-2021-39182 is fixed in 1.1.4. Upgrade to this version or later.

Q: Is CVE-2021-39182 exploitable, and should I be worried?

Whether CVE-2021-39182 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2021-39182 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2021-39182?

Upgrade enrocrypt to 1.1.4 or later.

Summary

Improper hashing in enrocrypt

Workarounds

If u specifically want a version and don't want to upgrade, you can remove the MD5 hashing function from the file hashing.py and this vulnerability will be gone

References

https://www.cybersecurity-help.cz/vdb/cwe/916/
https://www.cybersecurity-help.cz/vdb/cwe/327/
https://www.cybersecurity-help.cz/vdb/cwe/328/
https://www.section.io/engineering-education/what-is-md5/
https://www.johndcook.com/blog/2019/01/24/reversing-an-md5-hash/

For more information

If you have any questions or comments about this advisory:

Open an issue in Enrocrypt's Official Repo
Create a Discussion in Enrocrypt's Official Repo

Impact

The vulnerability is we used MD5 hashing Algorithm In our hashing file. If anyone who is a beginner(and doesn't know about hashes) can face problems as MD5 is considered a Insecure Hashing Algorithm.

The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES. Typical impact: compromised confidentiality or integrity of protected data.

CVE-2021-39182 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.1.4); upgrading removes the vulnerable code path.

Affected versions

enrocrypt (< 1.1.4)

Security releases

enrocrypt → 1.1.4 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The vulnerability is patched in v1.1.4 of the product, the users can upgrade to version 1.1.4.

Frequently Asked Questions

What is CVE-2021-39182? CVE-2021-39182 is a high-severity use of a broken or risky cryptographic algorithm vulnerability in enrocrypt (pip), affecting versions < 1.1.4. It is fixed in 1.1.4. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.
How severe is CVE-2021-39182? CVE-2021-39182 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of enrocrypt are affected by CVE-2021-39182? enrocrypt (pip) versions < 1.1.4 is affected.
Is there a fix for CVE-2021-39182? Yes. CVE-2021-39182 is fixed in 1.1.4. Upgrade to this version or later.
Is CVE-2021-39182 exploitable, and should I be worried? Whether CVE-2021-39182 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2021-39182 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2021-39182? Upgrade enrocrypt to 1.1.4 or later.