# CVE-2006-1705: Missing authorization in n/a

> Local users with SELECT privileges can modify base table data by creating and manipulating crafted views, bypassing intended access controls.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m48r-mhhj-43f3

## What is CVE-2006-1705?

CVE-2006-1705 is a low-severity missing authorization vulnerability in Oracle Oracle9i, published on 11 Apr 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Oracle Database 9.2.0.0 to 10.2.0.3 allows local users with "SELECT" privileges for a base table to insert, update, or delete data by creating a crafted view then performing the operations on that view.

## Which versions are affected by CVE-2006-1705?

It affects 2 products.


Products: Oracle Oracle10g, Oracle Oracle9i.

## How do I fix CVE-2006-1705?

No fix has been published for CVE-2006-1705 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-1705 being exploited?

There is no known exploitation of CVE-2006-1705 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Oracle9i

- [CVE-2006-0272](https://insights.sbomify.com/CVE-2006-0272/): Memory corruption in n/a (critical 9.0)
- [CVE-2005-4832](https://insights.sbomify.com/CVE-2005-4832/): SQL injection in n/a (high 7.5)
- [CVE-2006-6703](https://insights.sbomify.com/CVE-2006-6703/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2006-0269](https://insights.sbomify.com/CVE-2006-0269/): SQL injection in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1705 and fix it if it is affected.

What it is: CVE-2006-1705 is a low-severity missing authorization vulnerability in Oracle Oracle9i, published on 11 Apr 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-1705 in the wild and no public exploit code.

Affected product: Oracle Oracle9i. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-1705/ (Markdown: https://insights.sbomify.com/CVE-2006-1705/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-1705
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-1705
- OSV: https://osv.dev/vulnerability/CVE-2006-1705

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-1705/
Summaries are generated and may contain mistakes; the official description above is the record.