CVE-2022-29229

Missing Cryptographic Step in cassproject

Workarounds

The issue may be mitigated by using SSO or client side certificates to log in. Please note that SSO and client side certificate authentication does not have this expectation of no-knowledge credential access, and cryptographic keys are available to the server administrator.

References

There are no references at this time.

For more information

If you have any questions or comments about this advisory:

• Open an issue in the CaSS Project Github
• Email us at the CaSS Project

CaSS Library, (npm:cassproject) has a missing cryptographic step when storing cryptographic keys that can allow a server administrator access to an account’s cryptographic keys. This affects CaSS servers using standalone username/password authentication, which uses a method that expects e2e cryptographic security of authorization credentials.

CVE-2022-29229 has a CVSS score of 6.3 (Medium). The vector is network-reachable, low 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.5.8); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The issue has been patched in 1.5.8, however, the vulnerable accounts are only resecured when the user next logs in using standalone authentication, as the data required to resecure the account is not available to the server.

1. What is CVE-2022-29229? CVE-2022-29229 is a medium-severity security vulnerability in cassproject (npm), affecting versions < 1.5.8. It is fixed in 1.5.8.
2. How severe is CVE-2022-29229? CVE-2022-29229 has a CVSS score of 6.3 (Medium). 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.
3. Which versions of cassproject are affected by CVE-2022-29229? cassproject (npm) versions < 1.5.8 is affected.
4. Is there a fix for CVE-2022-29229? Yes. CVE-2022-29229 is fixed in 1.5.8. Upgrade to this version or later.
5. Is CVE-2022-29229 exploitable, and should I be worried? Whether CVE-2022-29229 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
6. What actually determines whether CVE-2022-29229 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.
7. How do I fix CVE-2022-29229? Upgrade cassproject to 1.5.8 or later.