Summary
Reversible One-Way Hash in io.github.javaezlib:JavaEZ
Workarounds
Currently there is no way to fix the issue without upgrading.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in our issue tracker
- Email us at [email protected]
Impact
This weakness allows the force decryption of locked text by hackers. The issue is NOT critical for non-secure applications, however may be critical in a situation where the highest levels of security are required. This issue ONLY affects v1.6 and does not affect anything pre-1.6. Upgrading to 1.7 is advised.
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-2022-29249 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.7); upgrading removes the vulnerable code path.
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
The vulnerability has been patched in release 1.7.
Frequently Asked Questions
- What is CVE-2022-29249? CVE-2022-29249 is a high-severity use of a broken or risky cryptographic algorithm vulnerability in io.github.javaezlib:JavaEZ (maven), affecting versions = 1.6. It is fixed in 1.7. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.
- How severe is CVE-2022-29249? CVE-2022-29249 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 io.github.javaezlib:JavaEZ are affected by CVE-2022-29249? io.github.javaezlib:JavaEZ (maven) versions = 1.6 is affected.
- Is there a fix for CVE-2022-29249? Yes. CVE-2022-29249 is fixed in 1.7. Upgrade to this version or later.
- Is CVE-2022-29249 exploitable, and should I be worried? Whether CVE-2022-29249 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-2022-29249 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-2022-29249? Upgrade
io.github.javaezlib:JavaEZto 1.7 or later.