CVE-2006-3718 Other in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2006-3718 and fix it if it is affected.
What it is: CVE-2006-3718 is a critical vulnerability in n/a, published on 19 Jul 2006.
Exploitation: There is no known exploitation of CVE-2006-3718 in the wild and no public exploit code.
Affected product: n/a. 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-3718/ (Markdown: https://insights.sbomify.com/CVE-2006-3718/index.md)
Unspecified vulnerabilities in Oracle Exchange for E-Business Suite allow attackers to potentially compromise the system, requiring vendor patches.
- 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-3718?
CVE-2006-3718 is a critical vulnerability in n/a, published on 19 Jul 2006.
Official description
Multiple unspecified vulnerabilities in Oracle Exchange for Oracle E-Business Suite and Applications 6.2.4 have unknown impact and attack vectors, aka Oracle Vuln# (1) APPS16 and (2) APPS17.
Which versions are affected by CVE-2006-3718?
It affects 1 product.
Products include Oracle Exchange.
How do I fix CVE-2006-3718?
No fix has been published for CVE-2006-3718 yet. Limit exposure of the affected software until one is available.
Is CVE-2006-3718 being exploited?
There is no known exploitation of CVE-2006-3718 in the wild and no public exploit code.
Sources
Also known as GHSA-r665-c4xj-hfpx.