Skip to content
Noroxi
NVD / CVE Program· CNA apache

CVE-2022-46337: Apache Derby: LDAP injection vulnerability in authenticator

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.4% (FIRST EPSS); higher than 73.2% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: derby (Debian:13) 10.14.2.0-3; org.apache.derby:derby (Maven) 10.14.2.1, 10.15.2.1, 10.16.1.2.

Low priority for now. Upgrade to derby (Debian:13) 10.14.2.0-3; org.apache.derby:derby (Maven) 10.14.2.1, 10.15.2.1, 10.16.1.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Nov 20, 2023
Updated
Jun 17, 2026
EPSS
1.4% · 73th percentile

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-46337

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
apachederby

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache Derby

    • 10.7.1.1, 10.9.1.0, 10.11.1.1, 10.12.1.1, 10.13.1.1, 10.14.2.0, 10.16.1.1affected
    • 10.1.1.0 and later · up to and including 10.1.3.1affected · semver
    • 10.2.1.6 and later · up to and including 10.2.2.0affected · semver
    • 10.3.1.4 and later · up to and including 10.3.3.0affected · semver
    • 10.4.1.3 and later · up to and including 10.4.2.0affected · semver
    • 10.5.1.1 and later · up to and including 10.5.3.0affected · semver
    • 10.6.1.0 and later · up to and including 10.6.2.1affected · semver
    • 10.8.1.2 and later · up to and including 10.8.3.0affected · semver
    • 10.10.1.1 and later · up to and including 10.10.2.0affected · semver
    • 10.15.1.3 and later · up to and including 10.15.2.0affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache derby10.1.1.0 and later · before 10.14.3.0
  • apache derby10.15.1.3 and later · before 10.15.2.1
  • apache derby10.16.1.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12derbyfrom 0—
Debian:13derbybefore 10.14.2.0-310.14.2.0-3
Mavenorg.apache.derby:derbyfrom 10.1.1.0 · up to and including 10.1.3.1—
Mavenorg.apache.derby:derbyfrom 10.10.1.1 · up to and including 10.10.2.0—
Mavenorg.apache.derby:derbyfrom 10.11.1.1 · up to and including 10.11.1.1—
Mavenorg.apache.derby:derbyfrom 10.12.1.1 · up to and including 10.12.1.1—
Mavenorg.apache.derby:derbyfrom 10.13.1.1 · up to and including 10.13.1.1—
Mavenorg.apache.derby:derbyfrom 10.14.2.0 · before 10.14.2.110.14.2.1
Mavenorg.apache.derby:derbyfrom 10.15.1.3 · before 10.15.2.110.15.2.1
Mavenorg.apache.derby:derbyfrom 10.16.1.1 · before 10.16.1.210.16.1.2
Mavenorg.apache.derby:derbyfrom 10.2.1.6 · up to and including 10.2.2.0—
Mavenorg.apache.derby:derbyfrom 10.3.1.4 · up to and including 10.3.3.0—
Mavenorg.apache.derby:derbyfrom 10.4.1.3 · up to and including 10.4.2.0—
Mavenorg.apache.derby:derbyfrom 10.5.1.1 · up to and including 10.5.3.0—
Mavenorg.apache.derby:derbyfrom 10.6.1.0 · up to and including 10.6.2.1—
Mavenorg.apache.derby:derbyfrom 10.7.1.1 · up to and including 10.7.1.1—
Mavenorg.apache.derby:derbyfrom 10.8.1.2 · up to and including 10.8.3.0—
Mavenorg.apache.derby:derbyfrom 10.9.1.0 · up to and including 10.9.1.0—

Other highest-scoring records for the same primary product.

  • CVE-2015-1832XML external entity (XXE) vulnerability in the SqlXmlUtil code in Apache Derby before 10.12.1.1, when a Java Security Manager is not in…
    40Plan
  • CVE-2010-2232In Apache Derby 10.1.2.1, 10.2.2.0, 10.3.1.4, and 10.4.1.3, Export processing may allow an attacker to overwrite an existing file.
    31Monitor
  • CVE-2018-1313In Apache Derby 10.3.1.4 to 10.14.1.0, a specially-crafted network packet can be used to request the Derby Network Server to boot a…
    22Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2006-7216Jul 5, 2007 · Apache Derby before 10.2.1.6 does not determine privilege requirements for lock table statements at compilation time, and consequently does…
    17Monitor
  • ← EarlierCVE-2006-7217Jul 5, 2007 · Apache Derby before 10.2.1.6 does not determine schema privilege requirements during the DropSchemaNode bind phase, which allows remote…
    17Monitor
  • ← EarlierCVE-2009-4269Aug 16, 2010 · The password hash generation algorithm in the BUILTIN authentication functionality for Apache Derby before 10.6.1.0 performs a…
    8Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:derby10.14.2.0-3 · Debian:13Package registry (OSV)
Maven:org.apache.derby:derby10.14.2.1Package registry (OSV)
Maven:org.apache.derby:derby10.15.2.1Package registry (OSV)
Maven:org.apache.derby:derby10.16.1.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records