CVE-2022-40084 — opencrx-client
MEDIUMCVE-2022-40084 is a medium-severity (CVSS 5.3) CWE-203 vulnerability in org.opencrx:opencrx-client. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.opencrx:opencrx-client — see the affected versions and patch details below.
OpenCRX vulnerable to password enumeration via error messages in password reset
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-40084.
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
org.opencrx:opencrx-clientReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
OpenCRX before v5.2.2 was discovered to be vulnerable to password enumeration due to the difference in error messages received during a password reset which could enable an attacker to determine if a username, email or ID is valid.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.opencrx:opencrx-client | all versions | 5.2.2org.opencrx:opencrx-client:5.2.2 |
Affected Products
opencrxopencrxResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencrx:opencrx-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.opencrx:opencrx-client to 5.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-40084 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-40084 in your dependencies?
Find it across Maven, including transitive dependencies.