CVE-2006-7217 json
Apache Derby SQL Injection
published 2007-07-05 19 y ago modified 2026-06-16 4 mo ago also GHSA-v7cq-pq7v-mh5v , EUVD-2022-5308
- cvss
- 4.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Apache Derby before 10.2.1.6 does not determine schema privilege requirements during the DropSchemaNode bind phase, which allows remote authenticated users to execute arbitrary drop schema statements in SQL authorization mode.
Patch / fix
- maven org.apache.derby:derby 10.2.1.6
- derby openSUSE Tumbleweed 10.11.1.1-3.2
opensuse advisories openSUSE-SU-2024:10092-1
Exploit prediction
1.95% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:P/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.derby:derby | <10.2.1.6 |
10.2.1.6 |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
db.apache.org
/derby/releases/release-10.2.1.6.html
web, patch
-
github.com
/apache/derby/commit/28c633d82a776c90fd1cd835a0b66d1c8916d31a
web
-
novell.com
/linux/security/advisories/suse_security_summary_report.html
vendor-advisory
- issues.apache.org /jira/browse/DERBY-1858
-
secunia.com
/advisories/28636
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2006-7217
advisory
-
github.com
/apache/derby
package
-
svn.apache.org
/viewvc?view=revision&revision=449869
web
-
web.archive.org
/web/20090406213028/http://www.novell.com/linux/security/advisories/suse_security_summary_report.html
web
-
web.archive.org
/web/20200301122517/https://issues.apache.org/jira/browse/DERBY-1858
web
Sources
- CVE List CVE-2006-7217
- GitHub Advisory GHSA-v7cq-pq7v-mh5v
- NVD CVE-2006-7217
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.