CVE-2006-3700 Other in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2006-3700 and fix it if it is affected.
What it is: CVE-2006-3700 is a critical vulnerability in Oracle Database Server, published on 19 Jul 2006.
Exploitation: There is no known exploitation of CVE-2006-3700 in the wild and no public exploit code.
Affected product: Oracle Database Server. 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-3700/ (Markdown: https://insights.sbomify.com/CVE-2006-3700/index.md)
Unspecified vulnerabilities in Oracle Database DAV and XMLDB components with unknown impact and attack vectors.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2006-3700?
CVE-2006-3700 is a critical vulnerability in Oracle Database Server, published on 19 Jul 2006.
Official description
Multiple unspecified vulnerabilities in Oracle Database 9.2.0.6 and 10.1.0.4 have unknown impact and attack vectors, aka Oracle Vuln# (1) DB04 for Web Distributed Authoring and Versioning (DAV) and (2) DB23 for XMLDB.
Which versions are affected by CVE-2006-3700?
It affects 1 product.
Products include Oracle Database Server.
How do I fix CVE-2006-3700?
No fix has been published for CVE-2006-3700 yet. Limit exposure of the affected software until one is available.
Is CVE-2006-3700 being exploited?
There is no known exploitation of CVE-2006-3700 in the wild and no public exploit code.
Other vulnerabilities in Oracle Database Server
Sources
Also known as GHSA-vjr3-v8gr-jm24.