CVE-2022-29229 — cassproject
MEDIUMCVE-2022-29229 is a medium-severity (CVSS 6.3) CWE-325 vulnerability in cassproject. A fix is available for cassproject — see the affected versions and patch details below.
Missing Cryptographic Step in cassproject
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
cassprojectnpmDescription
Impact
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.
Patches
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.
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | cassproject | all versions | 1.5.8npm install cassproject@1.5.8 |
Affected Products
competency and skills systemcassprojectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cassproject, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cassproject to 1.5.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-29229 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2022-29229 in your dependencies?
Find it across npm, including transitive dependencies.