CVE-2022-46337
CRITICALCVE-2022-46337 is a critical-severity (CVSS 9.8) CWE-74 vulnerability in org.apache.derby:derby. O3 Security confirms whether CVE-2022-46337 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache Derby: LDAP injection vulnerability in authenticator
Real-World Exposure
org.apache.derby:derby☕org.apache.derby:derby☕org.apache.derby:derby☕org.apache.derby:derby☕org.apache.derby:derby☕org.apache.derby:derby☕org.apache.derby:derby☕org.apache.derby:derby+8 moreReal-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
A cleverly devised username might bypass LDAP authentication checks. In LDAP-authenticated Derby installations, this could let an attacker fill up the disk by creating junk Derby databases. In LDAP-authenticated Derby installations, this could also allow the attacker to execute malware which was visible to and executable by the account which booted the Derby server. In LDAP-protected databases which weren't also protected by SQL GRANT/REVOKE authorization, this vulnerability could also let an attacker view and corrupt sensitive data and run sensitive database functions and procedures.
Mitigation:
Users should upgrade to Java 21 and Derby 10.17.1.0.
Alternatively, users who wish to remain on older Java versions should build their own Derby distribution from one of the release families to which the fix was backported: 10.16, 10.15, and 10.14. Those are the releases which correspond, respectively, with Java LTS versions 17, 11, and 8.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.derby:derby | ≥ 10.1.1.0 | No fix |
| ☕Maven | org.apache.derby:derby | ≥ 10.2.1.6 | No fix |
| ☕Maven | org.apache.derby:derby | ≥ 10.3.1.4 | No fix |
| ☕Maven | org.apache.derby:derby | ≥ 10.4.1.3 | No fix |
| ☕Maven | org.apache.derby:derby | ≥ 10.5.1.1 | No fix |
| ☕Maven | org.apache.derby:derby | ≥ 10.6.1.0 | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.derby:derby. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
No patched version of org.apache.derby:derby has shipped for CVE-2022-46337 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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.
How O3 protects you
O3 pinpoints whether CVE-2022-46337 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2022-46337. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-46337 in your dependencies?
O3 detects CVE-2022-46337 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.